D365 OData 401 on SaveChanges()

(0) Share

Report

Posted on by richierich79

300

I am able to retrieve both out of the box and standard data entities from my dev instance if D365FO

I now want to submit Sales journals and have setup the following code but I get a 401 returned.

context.AddToOpenSalesPriceJournalLines(new OpenSalesPriceJournalLine()
{

//populate journal entry

});

var response = context.SaveChanges();

Any idea what could be causing the 401?

I can successfully retrieve a collection of journals, just not submit them

I have the same question (0)

All responses (8)

Answers (1)

Martin Dráb 237,880 Most Valuable Professional on at

Like (0)

Report

I would start by reviewing details of the Exception object and events logs.

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

Like (0)

Report

Hi richerich79,

As 401 means Unauthorized and you said that you can read data with the same credentials, I can suspect that you don't have enough rights to insert data. Which account is linked to application in D365? Does it have enough access rights to the entity?

But it's good to explore the exception for useful information.

Was this reply helpful? Yes No
richierich79 300 on at

Like (0)

Report

Thanks for your replies, authentication and permission issues always give me a headache :-(

@Martin Unfortunately the exception object give me no more information than a 401 Authentication Failed, and I have not been able to find anything useful in the event viewer.

The only thing I can find in the event viewer is a security audit (I don't know if it's even relevant)

@Sergei I agree that seems the most likely issue. I have one user setup in dynamics as a system admin.

The azure application has the following roles

In visual studio I have created security privileges for my custom data entities, and I have added in SalesOpenSalesPriceJournalLineEntity to the group of entities

I'm a bit stuck for where to go from here :-(

Was this reply helpful? Yes No
Martin Dráb 237,880 Most Valuable Professional on at

Like (0)

Report

If you use the client secret for authentication, did you register your app in F&O (System Administration > Setup > Azure Active Directory Applications)?

Was this reply helpful? Yes No
richierich79 300 on at

Like (0)

Report

Hi Martin

Yes I have, and the client Id in FO matches the client id of the app in Azure

I would of thought if this wasn't setup then I would be able to access FO externally at all. Currently I can retrieve data, but can't create new journals

The inner exception is of type System.InvalidOperationException. Could it be that the 401 is a red herring and Im sending the journals in an incorrect mannor?

Was this reply helpful? Yes No
LDuncan on at

Like (0)

Report

It is possible the 401 is not actually representative of the issue. The best way to get the inner exception is with a Fiddler trace. This article contains a link to Fiddler, I don't expect it is a token issue if you can read data successfully so the rest of the article may not be helpful.

https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/troubleshoot-service-authentication

Also the Event Log I think is a good spot to check and you noted checking there but I would look into the AX-OData* logs as opposed to the Windows Security Events. You can find all of the AX logs in the Windows Event Viewer under Applications and Services Logs > Microsoft > Dynamics

Was this reply helpful? Yes No
richierich79 300 on at

Like (0)

Report

Thanks for all of your comments guys. Unfortunately I'm still getting the same error.

Fiddler doesn't give much more than the exception object.

I doubt it's authentication because I can retrieve records.

My instincts tell me it's permissions of the user\application, or it's down to the data entity permissions. Unfortunately I've not been able to find anything

Any ideas would be greatly welcome.

Was this reply helpful? Yes No
Verified answer

richierich79 300 on at

Like (0)

Report

So I was being an idiot.

The calls that were working were using a different config file. It was my own config that was causing the issue.

The backslash issue...

This works

ActiveDirectoryResource = "https://#######.cloudax.dynamics.com";

This doesn't!

ActiveDirectoryResource = "https://#######.cloudax.dynamics.com/";

Was this reply helpful? Yes No