From 091b1870b6cd5f8ab12061f8128a6f505befde34 Mon Sep 17 00:00:00 2001 From: paulh Date: Thu, 9 Apr 2026 20:56:06 -0400 Subject: [PATCH] =?UTF-8?q?Fix=20AcctDemo=5FNamedCreds=20note=20=E2=80=94?= =?UTF-8?q?=20exists=20in=20org,=20not=20yet=20retrieved=20to=20source?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Sonnet 4.6 --- docs/SALESFORCE_SETUP.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/SALESFORCE_SETUP.md b/docs/SALESFORCE_SETUP.md index afba8d6..35e4548 100644 --- a/docs/SALESFORCE_SETUP.md +++ b/docs/SALESFORCE_SETUP.md @@ -61,10 +61,13 @@ ## Manual post-deploy steps -### Named credentials requiring org-side setup -The following are not deployable via source and must be configured in the target org: +### Named credentials not yet in source +The following exist in the target org but have not been retrieved into `force-app/`: -- **`AcctDemo_NamedCreds`** — eSignature OAuth/userinfo credential referenced by `DTC_CLM_Demo` account setting. Create a Named Credential pointing to the DocuSign account server (e.g., `https://account-d.docusign.com`) with the appropriate OAuth settings. +- **`AcctDemo_NamedCreds`** — eSignature OAuth/userinfo credential referenced by `DTC_CLM_Demo` account setting. Retrieve it with: + ```bash + sf project retrieve start --metadata "NamedCredential:AcctDemo_NamedCreds" + ``` ### DocusignJWT external credential `force-app/main/default/externalCredentials/DocusignJWT.externalCredential-meta.xml` contains demo values for `iss` (integration key) and `sub` (user GUID) targeting `account-d.docusign.com`. Replace these with your org's actual integration key and impersonation user GUID before use.