Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default values are not saved #4600

Open
BlackbitNeueMedien opened this issue Jul 2, 2019 · 1 comment

Comments

3 participants
@BlackbitNeueMedien
Copy link
Contributor

commented Jul 2, 2019

I know that configured default values in field definitions are not saved to database, they are only used to preset a field's value in the GUI
But why is this the case? Also in #3853 (comment) this fact is cited - but what is the reason for this?

By not saving default values to the database a lot of problems arise, e.g. the value does not appear in exports. When you then open the object to check if the value really has not been set, it gets even more confusing because there the default value gets applied.

@brusch brusch added the Improvement label Jul 8, 2019

@weisswurstkanone weisswurstkanone added this to To do in 04/07/2019 - 16/07/2019 via automation Jul 12, 2019

weisswurstkanone added a commit that referenced this issue Jul 12, 2019

weisswurstkanone added a commit that referenced this issue Jul 15, 2019

@brusch brusch added this to To do in 15/07/2019 - 26/07/2019 via automation Jul 16, 2019

@weisswurstkanone weisswurstkanone moved this from To do to In progress in 15/07/2019 - 26/07/2019 Jul 16, 2019

@weisswurstkanone

This comment has been minimized.

Copy link
Contributor

commented Jul 16, 2019

  • only for create, not on update. otherwise there is no way to null it out anymore.
  • if inheritance is enabled and there is no parent value then take the default value.
  • if inheritance is disabled, take the default value.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.