Dynamics Community Forum Thread Details

Business rule scope of entity, field changed by Power Automate, rule not applied to records

Greetings.

We have a business rule set to the scope of entity on the Opportunity entity. The logic is to calculate estimated revenue based on a quantity unit of measure, requested quantity and a recommended price. (four check conditions with a calculation of requested quantity of the UoM * recommended price).

When a record is opened and the condition value is met, the estimated revenue field is updated/calculated as expected.

The data fields used in the business rule are populated with a PowerAutomate process. The process updates a Yes/No field, which in turn triggers a plug-in to locate a related quantity break record and return its price. The sequence of steps within the PowerAutomate are to create quantity break records for an opportunity, update a "recalculate" binary field to Yes, which in turn triggers a plug-in to determine which quantity record's price to get and update the Opportunity record.

If the PowerAutomate updates the recalculate field, the plug-in is triggered and a recommended price is updated. However, the business rule did not apply its logic to calculate the estimated revenue.

This is where it gets odd. If we run an on-demand workflow against the records to set the recalculate field to Yes, everything works as expected. The plug-in is triggered, a recommended price is updated and the business rule recalculates the estimate revenue.

All of the fields are on the form, the rule works when a record is opened by a user (similar to scope of All Forms or a specific form). Audit history shows the updates to the data fields used in the condition portion of the business rule, so we are confident the update from PowerAutomate is working.

Has anyone experienced business rules not getting processed when data is applied through a Power Automate? In a non-technical summary, it is as if the Power Automate update initiated changes do not get "seen" by the business rule, but workflow initiated changes to the same field works as expected.

Thanks for any assistance or suggestions you can offer!

Steve

Quick Links

Leaderboard