-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Hidden extrafields of type boolean are set to 0 on update #29353
Comments
I see the same on Tuxgasy development Dolibarr container image. Dolibarr Version: 20.0.0-alpha json from API on the extrafield for propal lines
the proposal Json before ticking that Complementary Attribute
ticking that extrafield
only getting the propal lines with it ticked
extrafield json after setting visibility to 0
json of the propal lines are still with a value
json of propal line after editing and saving.
The value is now back to null even though we never actually changed the value, only the definition and the visibility. |
Looking in the database the rowid number changes every time the propal line is edited, and during this process the glu000 value gets reset to |
@glu000 I think the code here is why that value disappears when you hide and unhide it. |
@eldy is there some technical reason for why the extrafield is first deleted from the database and then created again? Why not just use |
Historical reason. |
Hidden extrafields are NULL on update. Can only happen with extrafields in positions of commercial elements (facture, propal, commande, etc)
Bug
Hidden extrafields of type boolean are set to 0 on update. Can only happen with extrafields in positions of commercial elements (facture, propal, commande, etc)
Dolibarr Version
18, 19, develop
Environment PHP
na
Environment Database
na
Steps to reproduce the behavior and expected behavior
Attached files
No response
The text was updated successfully, but these errors were encountered: