MattB

@jdiekman are you still experiencing this issue? if so can you let us know if the issue is the same? or has it changed?

@filcole , as @davidjenni mentioned here: > Here's a tentative workaround/mitigation: edit the pac.exe.config that is located next to where you launch the pac.exe from (if in doubt, call where...

Thanks for the PR, We will accept this one and pull it into the master branch, I will close this PR here when the master branch is updated.

@fowl2 , this pattern is extremely common and thus I'm a bit surprised your experiencing an issue. You in the second example, you do not need to pass the authentication...

@fowl2 this reflects that client is created and working, is it not? IE are you commenting about the warnings in the logs?

Got it,. We will take a look at that warning message and see if we can get rid of it under this circumstance. thanks for Reporting it!

That SDK message is very new, Please check DVSvcClient 1.0.23, I believe it should be included there. for the CrmServiceClient, Update the Microsoft.crmsdk.coreassemblies to the current release.

@Chielus This appears to be a bug with the message format in the dataverse server definition, the owning team is looking into it currently. In the mean time, Please try...

Thanks for your report, We will take a look at this.

Hi, @Ivan-Colomer What you're seeing is the GC moving though its process, the only operation in the 1.0.9 and older client that use the WebAPI ( and thus the response...