When having a financial dimension that uses values from existing tables, no record for this dimension value is automatically created in the table DimensionAttributeValue, meaning that the value is not available in the OData entity FinancialDimensionValues. This means that systems that get e.g. Departments from Dynamics will not get them before they have been used.

To create the record in DimensionAttributeValue and provide availability in the OData entity FinancialDimensionValues, use the financial dimension value on a record or modify settings for the applicable dimension value.

For financial dimensions using values from e.g. customer table, project table or vendor table, basically all tables other the Operating Units (for example Department, Cost center, Business unit), it's possible to activate a parameter that will automatically populate the financial dimension on that record with its own value. Example:

The financial dimension "Customer" is getting its values from the table Customers, meaning that every time a new customer is created a new value for the financial dimension "Customer" is created. When activating the parameter "Copy values to this dimension on each new Customer created", the new customer record that is created will get the its own value for financial dimension "Customer" as a default financial dimension.

Automatically adding dimension values from Operating Units to DimensionAttributeValue prevents much manual work. Please add a parameter on the financial dimension form or on the Operating Unit value for this.