We had developed a vertical solution that will enable our third party application to display the attached file from D365F&O in their user interface. Our developer had created an API where it will return the download URL of the file attachment.
In our development machine, we are able to view the file without issues in postman. But, after we had it deployed to any of our Tier-2+ sandbox machine, we encountered this issue (See the image below).
To further explain it, it requires log-in in the Tier-2+ sandbox. Is there a difference on how we access the attachments from the Dev machine and Tier-2 Sandboxes using API? And how can we address this issue? We are using GET method to access the public URL in the Postman.
Please take note of the following steps we had done:
Reviewed the Microsoft Entra ID Applications in the D365F&O. We are using the same Client ID for both the development and sandbox machine.
Used the same Bearer Token generated in thehttps://login.microsoft.com/.../oauth2/token API to access the generated public URL of the attachment.
Reviewed the link generated by manually accessing it in a browser (Microsoft Edge).
Should you need more clarifications, please let me know.
On a Tier 2+ environment, an Azure BLOB storage linked to the Dynamics 365 application is used. On a development environment, there is a storage emulator. There is a difference in security. You don't have direct access to the BLOB storage. This is managed via APIs in the Dynamics application. You can develop a data entity providing access to specific attachments.
Was this reply helpful?YesNo
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.
Share
Report
All responses (
Answers (
301,030
