Mohith Shrivastava

This is an example we have shown with an assumption that emails are also used as usernames for users in the org!! If this is not true for your org...

@dschach, I think every org is unique, and this repo aims not to build code that addresses the needs of every org. I will let the sample apps lead @pozil...

@kbuckles-sfdc Can you provide more details around here ? Please share a simple example where i can reproduce this . Also share the api version in your metadata xml file...

@kbuckles-sfdc Sorry for the delayed response on this. This looks like an issue with the Tooling api in salesforce. I will open a case on this and keep you updated.

@jprichter The core issue is in the tooling api of LWC. I will raise it internally at salesforce and see what can be done for this. The Salesforce LWC extension...

Hello, The work is logged with metadata and tooling teams and looks like it is de prioritized at this point! It is recommended to use mdapi for now!

@tielinglang It's still in the backlog! You can use the official salesforce extension to push that uses metadata API than tooling API!

Please raise in the official repo for the extension! Not here!

https://github.com/forcedotcom/salesforcedx-vscode

@pavankumar9849 Sorry for delayed response. You can use the below to update an endpoint https://developer.salesforce.com/docs/atlas.en-us.apexref.meta/apexref/apex_ConnectAPI_NamedCredentials_static_methods.htm#apex_ConnectAPI_NamedCredentials_patchCredential_4 We will have recipes for it soon. For now you can also get the NamedCredentialRecipes...