Microsoft Dynamics 365 | Integration, Dataverse...

Quick create form setting default value on save even when it is blank

(0) Share

Report

Posted on by noobCoder

Hello all,

So i just wanted to confirm if this is a default behaviour. I have a choice field with default value. A global yes/no choice.

When i open quick create form it is showing no as default and that part is fine. When i go ahead and remove the no and set it to "--select--" blank value, and save it. Then once i check the saved records it has "no" as value instead of blank

Is this a default behaviour? I checked dependencies on the field and there are none. no business rule, no workflow, no js to set the value still it is setting to no instead of blank

when i remove the default it is working fine so i am pretty sure it is because of default value that it is not setting to null

Thanks

I have the same question (0)

All responses (2)

Answers (0)

Haig Liu Microsoft Employee on at

Like (0)

Report

RE: Quick create form setting default value on save even when it is blank

Hi noobCoder,

This may be for required fields, I'm not quite sure,

when a required field is modified to yes/no, "--select--" is no longer considered a value.

Was this reply helpful? Yes No
Suggested answer

DAnny3211 11,389 on at

Like (0)

Report

RE: Quick create form setting default value on save even when it is blank

hi

this is the default behavior for choice fields in Dynamics 365 when a default value is set. If a default value is defined for the choice field and the user selects and then removes the default value before saving the record, the system will automatically set the field to the default value when the record is saved.

This behavior is intended to ensure that the field always has a valid value, even if the user accidentally clears the value. If you want to allow the field to be blank even when a default value is defined, you will need to remove the default value from the field.

You mentioned that you checked for dependencies on the field and found none, but it's possible that the default value is being set by a system configuration or customization. If you're still having trouble, you may want to reach out to your Dynamics 365 administrator or a developer who can help you investigate further.

DAniele

Was this reply helpful? Yes No