Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cloned connections lacking option to have their own custom headers #438

Closed
svejdo1 opened this issue Mar 20, 2024 · 2 comments · Fixed by #444
Closed

Cloned connections lacking option to have their own custom headers #438

svejdo1 opened this issue Mar 20, 2024 · 2 comments · Fixed by #444
Labels
enhancement New feature or request

Comments

@svejdo1
Copy link

svejdo1 commented Mar 20, 2024

Ref: https://github.com/microsoft/PowerPlatform-DataverseServiceClient/blob/master/src/GeneralTools/DataverseClient/Client/ServiceClient.cs (line 1420)

When we're cloning ServiceClient the CustomHeaders function is always set to match the parent.
This makes impossible to set custom headers per clonned connection.

@MattB-msft
Copy link
Member

@svejdo1, thanks for your report, Yes, this is a known issue.

On the bright side, we are about to ship a new feature to address this specific issue.
This new feature is a request builder where you can set headers per request, as well as user ID, request ID and so on.

@MattB-msft MattB-msft added the enhancement New feature or request label Mar 26, 2024
@MattB-msft
Copy link
Member

Fixed with #444

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants