You’re offline. This is a read only version of the page.
130
Hi,
I am trying to implement adding attachments to Business Central via Oauth
Maybe I am doing something wrong, please, look at my steps.
1)POST to create an Incoming Document record entry /attachment
where _connectionDynamicsBusinessCentralOptions.Scope value is "">api.businesscentral.dynamics.com/.default"
URL is /v2.0/fc586214-b714-4bc4-8ff8-2e13a1a007cd/Sandbox/api/v2.0/companies(51fafb6c-c141-ec11-bb7e-000d3abb14eb)/salesOrders
BODY is {"externalDocumentNumber":"finally","currencyCode":"EUR","customerNumber":"10000","orderDate":"2023-08-05"}
The request is successful and data already generated in dynamics' system
2) Step 2 I retrieved Parent Id
3) Step 3
I am trying to create attachment
URL is /v2.0/fc586214-b714-4bc4-8ff8-2e13a1a007cd/Sandbox/api/v2.0/companies(51fafb6c-c141-ec11-bb7e-000d3abb14eb)/attachments
BODY is {"parentId":"5157829e-b5bd-ed11-9a88-002248d5380a","fileName":"123.txt"}
Request is successful and I get Id for attachment
4)Step 4
Everything is ready for PATCH method via /companies(CompanyId)/attachments(IncomingDocumentId)/attachmentContent
I am using the following code
In this part user and password are client id and client secret for Oauth authentication
BaseAddress is "api.businesscentral.dynamics.com/.default"
Authorization parameter is Bearer - oauth token
URl is following
And I get this
What I am doing wrong at that part ?
hi
This error message typically occurs when there is a mismatch between the number of keys specified in the URI and the number of key properties defined for the resource in Microsoft Business Central.
In this case, it seems that the error is related to the "Microsoft.NAV.attachment" resource. The error message is indicating that the number of keys specified in the URI does not match the number of key properties defined for the attachment resource.
To resolve this issue, you will need to check the URI and the key properties for the attachment resource to ensure that they match.
Here are some steps you can follow to troubleshoot this issue:
Check the URI: Make sure that the URI you are using to access the attachment resource is correct and matches the format specified in the Business Central API documentation.
Check the key properties: Check the key properties defined for the attachment resource in Business Central to ensure that they match the keys specified in the URI. You can do this by reviewing the metadata for the attachment resource in Business Central.
Update the URI or key properties: If you find a mismatch between the URI and the key properties, you will need to update either the URI or the key properties to ensure that they match.
Test the API call: After updating the URI or key properties, test the API call again to see if the issue has been resolved.
If you are still experiencing issues after following these steps, you may need to seek additional support from a Microsoft Dynamics partner or support team.
DAniele
Hello,
We currently do not have dedicated Dev support via the Dynamics 365 Business Central forums, but I wanted to provide you some additional resources to assist. If you need assistance with debugging or coding I would recommend discussing this on one of our communities.
I will open this up to the community in case they have something to add.
Thanks.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (