Skip to content
This repository has been archived by the owner on Jan 16, 2024. It is now read-only.

Initial Values cannot be set #82

Closed
ByteCraftServices opened this issue Jun 26, 2019 · 6 comments
Closed

Initial Values cannot be set #82

ByteCraftServices opened this issue Jun 26, 2019 · 6 comments
Labels
as designed As designed released Issue is resolved in a current release
Milestone
1.3.0.5

Comments

@ByteCraftServices
Copy link

I'm using the Property Inital Value on the Entity's property to set the default value.
It is a column from type = "short". But if I enter the value '0' it tells me that "0 isn't a valid value for short".

Afterwards I've got the same issue when i was using an Enum.
Same error with saying that my entered value is not valid for the chosen Enum type.
But the enum was set up correct. The value I've entered as initial value is specified on my enum.
@msawczyn msawczyn added need info Need more information to track this down and removed need info Need more information to track this down labels Jun 26, 2019
@msawczyn
Copy link
Owner

Hmm. Ok. Let me look into that. Should be a quick fix.

@msawczyn msawczyn added the investigating Looking into this label Jun 26, 2019
@msawczyn
Copy link
Owner

msawczyn commented Jul 5, 2019

I can't seem to reproduce this. Can you make available an .efmodel file that shows the problem?

@msawczyn msawczyn added no repro Can't reproduce. Need sample code that exhibits the issue. and removed investigating Looking into this labels Jul 5, 2019
@msawczyn
Copy link
Owner

Closing due to inactivity. Please reopen if/when this continues to be a problem.

@ByteCraftServices
Copy link
Author

Sorry for my late response.
I've attached a TestModel in which you should be able to reproduce bug.
In CustomEntity I've attached the prperty "Active" (see Screenshot)
image

TestModel.zip

@msawczyn
Copy link
Owner

Got it. The picture and sample model really helped. "No" won't work - it's not the enumeration. Try "NoYes.No".

Not to say that we shouldn't make that simpler for the user. And it's an easy change. Thanks!

@msawczyn msawczyn reopened this Jul 14, 2019
@msawczyn msawczyn added as designed As designed clarification Feature needs clarity to make it more user friendly pending release Issue is resolved in the current codebase, will be published with the next release and removed no repro Can't reproduce. Need sample code that exhibits the issue. labels Jul 14, 2019
@msawczyn
Copy link
Owner

Enhanced in 1.3.0.5

@msawczyn msawczyn added this to the 1.3.0.5 milestone Sep 18, 2019
@msawczyn msawczyn added released Issue is resolved in a current release and removed pending release Issue is resolved in the current codebase, will be published with the next release labels Sep 30, 2019
@msawczyn msawczyn removed the clarification Feature needs clarity to make it more user friendly label Oct 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
as designed As designed released Issue is resolved in a current release
Projects
None yet
Milestone
1.3.0.5
Development

No branches or pull requests
2 participants
@msawczyn @ByteCraftServices