Applies to Product - Dynamics 365 Project Operations
What’s happening?
Customers are experiencing difficulties in configuring a new billing parameter for cost calculation in their project resources. Despite following the necessary steps, the expected pricing rules are not being applied correctly.
Reason:
This arises from the configuration of custom fields and entities as pricing dimensions. Specifically, the custom field must be created with the exact same name across multiple tables, including actuals, journal lines, invoice line details, and role prices. If the naming is not identical on all tables, the creation of the pricing dimension will fail.
Resolution:
- Navigate to Project management and accounting > Setup > Project management and accounting parameters> Project Operations on Dynamics 365 Customer Engagement tab.
- Set up your billing type mappings, default categories, default forecast model, and default integration account for expense reports.
- Ensure that the custom field is created with the exact same name on all relevant tables (actuals, journal lines, invoice line details, role prices, etc.).
- Once the custom field is added to the necessary places, it can be added as a pricing dimension to the project parameter.
- Verify that the custom field is included in the time entry quick create form.
- If filtering is required (e.g., filtering roles based on the selected business unit), customize the field on the form accordingly.
- Mark the business unit field as business required if necessary.
Note: Adding fields by using Personalize option does not always work as expected by the user. Personalize option is a user friendly way to customize the application. This tool allows user to customize forms easily but it has got some limitations. When user finds these limitations, this means they should use Visual Studio that is the way to customize something with all features. More information on Personalize can be found in this link: Personalize the user experience