Announcements
curl --request GET \ --url 'https://api.businesscentral.dynamics.com/v2.0/<tenant-id>/Production/api/v1.0/companies(<company-id>)/items(<item-id>)?%24expand=itemCategory%2Cpicture%2CdefaultDimensions%2CitemVariants' \ --header 'Authorization: Bearer <auth-token>'
curl --request GET \ --url 'https://api.businesscentral.dynamics.com/v2.0/<tenant-id>/Production/api/v1.0/companies(<company-id>)/items(<item-id>)?%24expand=unitOfMeasure%2CitemCategory%2Cpicture%2CdefaultDimensions%2CitemVariants' \ --header 'Authorization: Bearer <auth-token>'
{ "error": { "code": "BadRequest", "message": "Could not find a property named 'unitOfMeasure' on type 'Microsoft.NAV.item'. CorrelationId: e5f99925-8842-4ccc-9295-13406d0e7cef." } }
unitOfMeasure
$expand
baseUnitOfMeasure
$select
The issue isn’t with your request or token — the problem is that the unitOfMeasure navigation property is not actually exposed in the standard Business Central API, even though it's listed in the official documentation.
You can confirm this by checking the $metadata endpoint, which shows the actual structure and available properties of the API.
$metadata
As a workaround, either use available fields like baseUnitOfMeasureCode, or create a custom API page in AL that includes unitOfMeasure as a navigation property if you need that relationship. Unfortunately, some navigation properties in the docs are planned or internal but not implemented in the public API.
baseUnitOfMeasureCode
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Jump in, show your community spirit, and win prizes!
Expanding mentorship, skilling, and AI innovation
These are the community rock stars!
Stay up to date on forum activity by subscribing.
OussamaSabbouh 2,454 Super User 2026 Season 1
YUN ZHU 1,806 Super User 2026 Season 1
AndrewThomas81 1,538