You’re offline. This is a read only version of the page.
5
Hi,
General Context:
We have a set of entity fields that we wanted required in our Portal, but optional in D365. So we created a business rule that effectively "un-requires" those fields when a user creates/updates records of that entity via D365. If I understand it right, the business rule fires every time a user opens up that entity form.
Problem:
Now I am trying to create a workflow that automatically creates those records under certain conditions, but the business rule doesn't seem to carry over. In other words, ALL fields are required. So I am unable to proceed with creating a new record via workflow.
Am I missing something? Any tips or advice would be greatly appreciated.
—
Additional Details (if you're curious):
I have a staging entity that is created via MS Forms + Power Automate. A record is created in D365 when forms results come in, and I want to create a workflow that uses that staging information to create a different entity record (the one that needs fields required in Portal, but optional in D365).
From what I understand, your basic requirement was to have some fields mandatory on the MS Portal but not on Dynamics 365 CRM. To achieve this, you created Business Rules that is not working in a certain scenario.
So I would suggest to create an entity form metadata in the CRM for that respective entity form where you can have that field set to be ‘Required only’ for the portal and make that field optional from the Dynamics CRM customizations.
Now, navigate to your entity form and scroll down to the Tab saying ‘Entity Form Metadata’. Click on the ‘+ button’ to create a new record and enable the ‘Field is Required’ checkbox as shown below:
Hope this helps.
Thanks!
Share
Report
All responses (
Answers (
