Dimension values returned by API are less

(2) Share

Report

Posted on by CU09051527-0

Hi, we've built an integration between our product and Dynamics 365 Business Central based on the REST API v2.0.

Unfortunately, our customers started to report that the dimensions values imported to our product are less than the ones they have on Dynamics. As you can see below, the issue appears to be on Microsoft's API as the list returned by the following request (GET /dimensionValues) contains only 15 values as opposed to 50 and more values found on Dynamics.

What could be causing this issue? Are you aware of any limitation on Dynamics API or particular configurations that might reduce the number of dimension values returned by the API compared to the UI?
We already double checked the company and environment.

Thank You

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (4)

Answers (1)

Suggested answer

Gerardo Rentería Ga... 25,225 Most Valuable Professional on at

Like (1)

Report

Hi

Someone else here had a similar problem.

Dimension values returns in the rest API are less than what we have in Business Central (dynamics.com)
Reviewing the related APIs, I don't see any different filters.

ALAppExtensions/Apps/W1/APIV2/app/src/pages/APIV2Dimensions.Page.al at main · microsoft/ALAppExtensions · GitHub

ALAppExtensions/Apps/W1/APIV2/app/src/pages/APIV2DimensionValuesEntity.Page.al at main · microsoft/ALAppExtensions · GitHub
Does it only happen with this dimension or with others? In this company or in all of them?

BR

GR

Was this reply helpful? Yes No
CU09051527-0 26 on at

Like (0)

Report

Hi @gdrenteria, thanks for your reply. Unfortunately the post you shared is unanswered.

To answer your questions, the issue we're facing is experienced on different dimensions of several different customers.

Thanks

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 95,597 Super User 2025 Season 2 on at

Like (0)

Report

Hi, the last time I saw this question on the forum, he got the environment and company wrong. It looks the same this time, but you said you double checked......

The following is the standard code of this API, without adding any filtering, it just displays the value of Dimension Value table.

https://github.com/microsoft/ALAppExtensions/blob/main/Apps/W1/APIV2/app/src/pages/APIV2DimensionValuesEntity.Page.al

I suspect it's still a problem with Endpoint. Here's what I tested. I hope it can give you some tips.

https://api.businesscentral.dynamics.com/v2.0/c8558e71-6ad8-4fcd-9f29-3ca165b41bbe/Sandbox240P/api/v2.0/companies(57747d95-78d5-ee11-904e-6045bdac9fd4)/dimensions(ffb2db45-19da-ee11-904c-002248e90ed1)/dimensionValues

Thanks.

ZHU

Was this reply helpful? Yes No
Verified answer

CU09051527-0 26 on at

Like (2)

Report

Hi All,

I think we found out the issue that's causing the list of departments values retrieved from Dynamics API to contain less items than the ones that some of our customers have on Dynamics.

In order to get the list of Departments values we need to query a specific Dynamics API endpoint with the dimension ID (see Microsoft doc here):

GET https://api.businesscentral.dynamics.com/v2.0/production/api/v2.0/$metadata#companies({id})/dimensions({id})/dimensionValues

Unfortunately, this endpoint returns only a small subset of Departments values; comparing them with the list shared by the customer it appears that only 23 out of 168 are returned by Dynamics API.

After more digging, we found out that by querying the full list of dimension values, without specifying the dimension ID of the Department, we get the full list!

GET https://api.businesscentral.dynamics.com/v2.0/production/api/v2.0/$metadata#companies({id})/dimensionValues

However, all the departments that are missing from the previous call have one thing in common, the dimension_id field appears as "00000000-0000-0000-0000-000000000000".

Missing from GET ../companies({id})/dimensions({id})/dimensionValues

{ "@odata.etag": "W/\"JzIwOzE1MzQwNjUxMTc5NTE3NTExMDE0MTswMDsn\"", "id": "8d1ba80f-7ba5-ec11-80f1-000d3a870012", "code": "01C", "dimensionId": "00000000-0000-0000-0000-000000000000", "displayName": "XXXXX", "consolidationCode": "01C", "lastModifiedDateTime": "2023-08-27T20:28:55.48Z" }

Available from ../companies({id})/dimensions({id})/dimensionValues

{ "@odata.etag": "W/\"JzE5OzQ2NzAwNDA2MjgwNzA1OTI0MzgxOzAwOyc=\"", "id": "e8b99a37-3cb1-ee11-a56a-002248436b28", "code": "03D", "dimensionId": "e1c652f0-7aa5-ec11-80f1-000d3a870012", "displayName": "YYYYY", "consolidationCode": "", "lastModifiedDateTime": "2024-01-15T09:38:16.86Z" }

Therefore, it appears that the issue resides on Dynamics, without the dimensionId field populated accordingly we’re not able to retrieve the full list of values for a specific dimension via GET ../companies({id})/dimensions({id})/dimensionValues API.

Also, we can't use the GET ../companies({id})/dimensions({id})/dimensionValues API as we would not be able to identify to which dimension a value belongs to in case the dimension_id field appears as "00000000-0000-0000-0000-000000000000".

Looking around, we found out that this issue might be related to a recent Dynamics upgrade where some data migrations were not completed successfully, please see here to find out more.

Thanks

Was this reply helpful? Yes No