Dynamics CRM 365 seems to ignore default values for entity fields in quick create forms

0
votes

For the contact entity I have set the default values for some build in fields to specific values. For example I set the default value for the field "Contact -> donotemail" to the value "Do not Allow".

In the "normal" web browser forms it seems to be working as expected. But if I create a new contact using a quick create form and select the save and then "view created record" button the view switches to the new created contact. If I then scroll down to the "donotemail" - field the field does not have the default value I selected in the field settings.

I googled the problem, the nearest community post I could find is https://community.dynamics.com/crm/b/mohamedmostafacrmblog/archive/2016/06/02/set-field-default-value-in-microsoft-dynamics-crm-online-and-on-premise-using-business-rules-without-javascript-or-custom-components-plugins-or-workflows

Unfortunately the post is from 2016 and it describes how to workaround the problem using custom business rules. But due to this is build in funtionality there is no business rule I could edit and creating some new to achive the goal of setting a default value seems odd.

Did someone encounter this problem too and could find a solution?

1
dynamics-crmmicrosoft-dynamicsdynamics-365dynamics-crm-365
Did you try to add that field in quick create form, but set visibility as false & test it? - Arun Vinoth
Hi Arun, thx for your comment. I tried that in a Testsystem and it worked as expected. The fields were set to the default values I configured. I then went back to my production system without adding the fields on the quick form and it worked there as well.. Of course there is no connection between the two systems. But its working now.. is it possible that the system needs time to propagate the changes? I was sure I hit "publish customizations" multiple times during my first tests, where it did not work.. I'm a litte bit confused now - D M
You mean Publish All? - Arun Vinoth
exactly. "Publish all Customizations". For example when you clicked "All components" in the "Customize the system" dialog - D M
One possible reason I could think of: you might have not refreshed the main window after publish all, maybe cached QC form didn’t work as expected bcoz customize the system will open a separate popup to edit & publish all. Still technically server side should not be cached with old customizations. But publish all should reflect immediately & no delays expected. Am confused too. Anyway issue is resolved & assume a glitch or product misbehaved :) - Arun Vinoth

1 Answers

1
votes

One possible reason I could think of: you might have not refreshed the main window after publish all, maybe cached QC form didn’t work as expected bcoz “customize the system” will open a separate popup to edit & publish all.

Still technically server side should not be cached with old customizations. But QC might have rendered from cached Metadata in browser.

But publish all should reflect immediately & no delays expected. Make sure to refresh the main window next time :)