cancel
Showing results for 
Search instead for 
Did you mean: 

Cross Entity Business Rule

Author Name: ANDRE MARGONO

The fields that can be used to build the business rule are only available from the entity that the business rule is attached to. So there are limitations when we need to access fields/condition from related entities (child/parent entity). To achieve this, we should choose either workflow/plugin/javascript path.

Status: Under Review
Comments
D365Ideas_Admin
Regular Visitor
Status changed to: Under Review
 
D365Ideas_Admin
Regular Visitor
Hi Andre, Thank you for your feedback. This is a great suggestion and we will consider this in our roadmap. Regards, Karan
D365Ideas_Admin
Regular Visitor
Microsoft - Its been two years since this was marked as "resolved". What decision was reached during consideration to add this enhancement to the roadmap? Is there an ETA for when we can expect this feature?
D365Ideas_Admin
Regular Visitor

In addition, please provide an ability to default values from related entities. For example, default phone number on Contact from parent account on change.

D365Ideas_Admin
Regular Visitor

The status of this request shows as "Under Review". When will this be resolved? This feature is very basic and is a must-have if Dynamics 365 has to remain competitive with Saleforce.com. Please see the form rules engine provided by Resco in their mobile application. It will save tremendous amount of time for developers if those features are made available by Microsoft within Business Rules and Workflows.

Graham
Kudo Collector

I cannot believe so few people have voted for this! I am even more surprised something so fundamental has not been addressed for so long!! Especially for Model-driven apps, this is a must....!

Andreas777
New Member

Dear Microsoft, this should be basic functionality. And I agree, already implemented. 😄 Or do you suggest some other way to fulfill the need?

WilliamKim
New Member

Any update on this?

ThomasFlockCris
New Member

Are we not doing this?

ArvatoService
Frequent Visitor

I can't understand why this isn't finally being implemented. This would be an great improvement tfor the developers and the customers? Please think about how much that would reduce the development effort.

Do you still need UseCases? It's very easy 
Imagine the user opens an incident form and records one and the account is an important customer. In this case, the priority must be increased and another field must be mandatory. Sure, workflows can do that too, but the information is needed BEFORE the user saves the record. It would also be nice if you could display a form notification.

How should we explain to the customer that your "Low Code / No code" application needs JavaScript for something so simple?