Power Apps Business Rules Overcoming the Numeric Value Saving Bug in Dataverse

Power Apps Business Rules: Overcoming the Numeric Value Saving Bug in Dataverse


Power Apps Business Rules: Resolving the Numeric Value Bug in Dataverse

Welcome to our in-depth guide on fixing a prevalent bug found in the ‘Business Rules‘ editor of Dataverse. This hiccup prevents users from saving numeric values due to a language mismatch, a frequent concern for Power App users in non-English regions. Continue reading to get a comprehensive solution to this problem, and remember, contact us if you need further assistance or any other technical support.

Understanding the Bug

In instances where the Dataverse language is mismatched with the editor language, an error occurs that prevents business rules from saving. This error prompts: ‘Enter a value from -922,337,203,685,477.00 through 922.337,203,685,477.00′. The root cause is the editor’s automatic formatting of numbers above 1000 using comma separators, which causes issues for non-English locales expecting a decimal point as the separator.

An Illustration of the Issue

Let’s visualize the bug using an example: Suppose we have a quote table and aim to establish a business rule that sets an ‘importance’ field to ‘important’ if the quote value surpasses 20,000. When inputting the 20,000 value without commas, the editor automatically introduces comma separators. If Dataverse is in a non-English language expecting decimal point symbols as separators, saving the business rule results in an error.

Step-by-step Solution

To rectify this issue, align the number format of the business rule editor with Dataverse’s language. Here’s a tried-and-true method to achieve this:

  1. Access ‘Advanced settings‘ by clicking the cog icon within Power Apps.
  2. This action launches the Dynamics 365 settings area. Navigate to the cog icon once more and select ‘Options‘.
  3. In the ensuing ‘Set Personal Options‘ dialog, head over to the ‘Formats‘ tab and press the ‘Customize‘ button.
  4. At this juncture, you have the liberty to configure the ‘Digit Group‘ and ‘Negative Number Format‘ dropdowns. It’s advised to eliminate any formatting and to set the Decimal Symbol to a comma for European language settings in Dataverse.

With these modifications, the Business Rule editor will stop introducing automatic comma separators when a numeric value is entered. Consequently, saving the Business Rule should now be error-free.

In Conclusion

Correcting the numeric value bug in Dataverse’s ‘Business Rules’ editor is a straightforward process once the root cause is identified. We hope this guide proves invaluable in your Power Apps journey. Should you face any challenges or need further clarification, do not hesitate to reach out to us. Our team is ready to assist and guide you through every step of the way.

About The Author