Timeline for FYI, apparently Salesforce Integration User License doesn't work with Named/External Credentials?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 11 at 14:14 | answer | added | BenSimonds | timeline score: 3 | |
| Jun 22, 2023 at 14:58 | vote | accept | smohyee | ||
| Jun 22, 2023 at 14:58 | answer | added | smohyee | timeline score: 1 | |
| Jun 19, 2023 at 17:04 | comment | added | Phil W | Sure. Why not post a self-answer and get some reps!? | |
| Jun 19, 2023 at 16:18 | comment | added | smohyee | Yeah that seems to be the case. Figured I'd make the post so other people could see it too. | |
| Jun 2, 2023 at 19:24 | comment | added | Phil W | A transaction running as the integration user, initiated through an inbound request, could, in principle, initiate a callout itself - that is true. But clearly it is an API only account which means for inbound calls. I guess the usage pattern you are trying is not supported. | |
| Jun 2, 2023 at 19:11 | comment | added | smohyee | But why would that license be only for inbound integration? For example, our integration user is making callouts to Salesforce which in turn trigger callouts to an external org, which ties it back to the user. | |
| Jun 1, 2023 at 18:06 | comment | added | Phil W | The integration user license is designed for inbound integration use, as far as I am aware, while named credentials are for outbound use. | |
| Jun 1, 2023 at 17:31 | history | asked | smohyee | CC BY-SA 4.0 |