💡 Description:

Currently, the decimal precision of Number-type questions in Inspection Templates is affected by the "Pricing decimal precision" setting in environment behavior settings (PPAC > Environment > Settings > Behaviour).

This behavior is confusing and unintuitive for the following reasons:

• Number questions are typically used for general numeric inputs (e.g., temperature, quantities, scores), which are not related to pricing or currency.
• The "Pricing decimal precision" setting is intended for controlling decimal places in currency fields, as clearly documented.
• Customers are reluctant to change this setting, as it also affects existing Dataverse currency fields across the environment.
• This hidden dependency can lead to inconsistent behavior, especially when using different base languages (e.g., English environments default to 2, Japanese environments default to 0).

🎯 Proposed Improvement:

Please consider decoupling the precision of Number-type questions in Inspection Templates from the "Pricing decimal precision" setting.

Instead, allow these questions to:

• Have their own explicit precision setting, or
• Default to a reasonable number of decimal places (e.g., 2), independent of pricing-related configurations.

🔍 Business Impact:

This behavior is currently blocking customers from using decimal values in Number-type questions without affecting global currency formatting.

It creates avoidable confusion and increases the risk of unintended side effects when adjusting a setting that is supposed to affect only currency fields.