Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I have a business rule with All Forms scope that displays an error if Mobile Phone and Primary Email are empty and requires both until at least one is filled.
One of my forms has neither of those fields on it EXCEPT in a quick view form related to a lookup field in that form. When I try to create a contact on this form the error messages display at the top of the page just below the ribbon and I'm not able to save my contact. This is despite the lookup field being empty so the quick view form is hidden.
I've tested this on other forms without those fields or quick view forms and they work. I've also tested my rule with the scope set to one form and my saving issue stops, so the only thing I can think of is the business rule thinks those two required fields are on my form because of the quick view form.
Any thoughts on why the rule is applying to a quick view form? I thought it was only main and quick create forms.
Hi Lucas, can you please give me some clarifications:
- You are trying to create a Contact, are the business rules created on the Contact forms?
- What Entity, the lookup that populates the quick view, points to?
Mauro De Biasio
Hey Mauro, thanks for the response!
- Yes, it's being created on contact forms. I've tried it on multiple different forms, too, and only the one with the Quick View form had the issue.
-The lookup field points to the Contacts table.
- Yes, the only rule related to the primary email and mobile phone field is the one that requires them if either is empty. There's also some JS that formats the phone number.
Hi Lucas, I replicated your scenario I think, I might have a different business rule, but mine should prevent saving. I tested by using only "Home Phone" as a field checked by a business rule, that makes the field itself mandatory if it's filled, and throws an error if it's empty. And I added a quick view form:
In this scenario I can save without any issues (after I fill up the home number with something). By any chance can you replicate the behavior with another entity?
Can you provide more details of the error, or maybe a screenshot of the error itself?
Mauro De Biasio
I'm not sure what happened but somehow it started working correctly... maybe something else was conflicting and causing it to not perform as expected? Anyways, thanks for your help!
Hi Lucas, that is most likely the case! Glad that you were able to solve your issue :)
Business Applications communities