MattB

the issue fix was in the framework itself, so it should have been picked up.. thanks for the validation of what we were seeing here. We will continue to poke...

Ok, Update on this.. We think we have finally got this locked down, the .net 6 codebase made it a bit easier to spot. The next update for the Dataverse...

@kwu022 , we have identified a bug in this behavior that would cause this pattern fault if the previous connection was disposed. We are going to move to a newer...

I know I'm way behind on responding to this one, Sorry about that. The LINQ provider is in somewhat of a limbo state right now. I had fowarded this over...

To clarify a few things... The Dataverse WebAPI is implemented on the Organization API. The Organization API is what is directly exposed in this client. In the webAPI when Prefer:...

Should we implement the Update behavior, we will have a discussion internally as to building it out as an IOrganziationService\*3, or an extension to OrganizationService\* The create is less interesting...

The next drop will include the implementation for CreateAndReturnAsync with the existing contract, (there is not a sync version of it right now). that will be part of the last...

sorry for the delay in responding here. We are aware of this and are discussing this with the Azure team, as their replacement lib extends the dependencies beyond the features...

Are you seeing this inconsistently for the same entity/attribute in the same environment? if so, that would be something we would want to have a support ticket opened with a...

Providing a bit of an update here. We are going to keep using the Rest nuget for a time yet. While the team is recommending Azure.Core as replacement, it is...