Timeline for Named Credentials - Merge Fields not Resolving
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 29, 2018 at 15:17 | comment | added | Charles T | The values are not merged in until the "last mile" when the request is about to exit Salesforce. However if you need to prove to yourself (for debugging's sake) that it merges, you could use a service like PostBin or RequestBin to create a fake endpoint and it will show you the entire request that you sent to it. | |
| Aug 30, 2018 at 11:08 | comment | added | Azeez | @kleytman-aular So, when you say "you will see the merge field '{!$Credential.UserName}' .... and not the actual value, the value is only replaced when the request is finally sent", do you mean to say that there is no way to see the actual merge fields values in the debug logs? | |
| May 30, 2017 at 18:26 | comment | added | Mauricio Oliveira | Is there any merge field to obtain the user's token? | |
| Apr 26, 2017 at 20:23 | review | Late answers | |||
| Apr 26, 2017 at 20:44 | |||||
| Apr 26, 2017 at 20:07 | review | First posts | |||
| Apr 26, 2017 at 20:30 | |||||
| Apr 26, 2017 at 20:07 | history | answered | Kleytman Aular | CC BY-SA 3.0 |