MattB

Following up on this... The next drop we are going to ship of the Dataverse ServiceClient does correct the authority acquisition and correct the construction of the request for MSAL...

@chrispiasecki please check this with he 0.6.1 client if you can and let us know if this sorted it out for you.

Yes, we have a backlog item with the API team to help provide a bit more context as to what is going on. I will ask the team to check...

Yes, this is long standing behavior of the Linq Client in our SDK. (since version 5 I believe ) the ID itself is always returned, thus if you ask for...

Tagging this an "Enhancement request"... this seems like something the team can make better in the core and we will try to get this done in the future,

Thanks, We will take a look at this.. We are in process in adding Async support to this lib currently, which may help in this situation.

@BetimBeja all the Execute commands run though our longstanding API interface which the CdsServiceClient uses. Can you tell me the instance/orgid that your connecting to so we can look at...

Sorry about the delay getting back to you here.. there was a bit of a long discussion around this. We do now understand the issue that is causing the inconsistent...

@BetimBeja as a heads up... we discovered and fixed number of issues that could have been impacting this in the ServiceClient, and a rather big issue with the way MSAL...

@BetimBeja were you successfull?