"There was no Claim specifying the Application Id" error while using postman to export data from Dynamics 365 for Operations

(0) Share

Report

Posted on by Deepa Paranthaman

Hi All,

I used a standard entity for data export (customer group). Also used this entity for recurring data job.

while using HTTP GET call against the following URL getting below error.

https://<baseurl>/api/connector/dequeue/<activity id>

URL:https://xyz-testdevaos.sandbox.ax.dynamics.com/api/connector/dequeue/9B64E276-580B-456A-B975-B07B53ABEE9D

"Message": "An error has occurred.", "ExceptionMessage": "There was no Claim specifying the Application Id.", "ExceptionType": "System.Security.SecurityException", "StackTrace": " at Microsoft.Dynamics.Platform.Integration.Services.WebApi.Connector.ConnectorExceptionHandlingAttribute.OnException(HttpActionExecutedContext actionExecutedContext)\r\n at System.Web.Http.Filters.ExceptionFilterAttribute.OnExceptionAsync(HttpActionExecutedContext actionExecutedContext, CancellationToken cancellationToken)\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at

Expecting a solution using post man tool.

Thanks

Deepa

I have the same question (0)

All responses (7)

Answers (1)

Sort by

Suggested answer

Sergei Minozhenko 23,097 on at

Like (0)

Report
Copy link

Link copied!

Hi Deepa,

Did you complete all steps mentioned in docs.microsoft.com/.../third-party-service-test ?(oData URL can be replaced with export API URL)

Was this reply helpful? Yes No
Deepa Paranthaman 95 on at

Like (0)

Report
Copy link

Link copied!

Hi Sergei

Yes, I did follow the steps mentioned in the url mentioned above.

Using recurring integration (Postman tool), am unable to export the data from D365.

Looking for a solution for it that is not available in docs.microsoft.com

Thanks

Deepa

Was this reply helpful? Yes No
Sergei Minozhenko 23,097 on at

Like (0)

Report
Copy link

Link copied!

Hi Deepa,

Could you, please, share screenshot with parameters for "Get Azure AD Token" request and actual dequeue request you used in Postman?

Was this reply helpful? Yes No
Ashok Rangineni 5 on at

Like (0)

Report
Copy link

Link copied!

Hi Deepa,

I am also facing the same issue. Are you able to find the solution?

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,172 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi Ashok,

I suggest that you start by sharing the information that Sergei asked above.

You can also try to debug Recurring Integration Scheduler sample app in Visual Studio, then you will have perfect examples that demonstrate how all the request should look like.

Was this reply helpful? Yes No
Suggested answer

CU26020744-0 2 on at

Like (0)

Report
Copy link

Link copied!

Was this reply helpful? Yes No
Verified answer

SimonPalmert 15 on at

Like (1)

Report
Copy link

Link copied!

Hi,

Had this issue myself and didn't feel that I could find a proper "solution" to this in the few community posts that exists that are pointing to the same issue.

So, here is the actual solution:

Authorization header with bearer token needs to be included in the request for collecting the file. In postman it would look like this:

This is not automatically received in postman when clicking the link from the dequeue-request. Adding it however solves the authorization issue.

Hope this helps anyone facing the same issue!

Was this reply helpful? Yes No