When you deploy a User Access Policy to a Salesforce org, the deployment fails with a "PermissionSetLicense does not exist" error. The permission set license (PSL) named in the error is already in the target org.
Error <PolicyName> The action target <PSL name> of type PermissionSetLicense does not exist.vlocity_cmt_DocGenIndCmeUserPsl.| Example error message |
|---|
| Error Set_UserFunction_to_Blank The action target vlocity_cmt_DocGenIndCmeUserPsl of type PermissionSetLicense does not exist. |
| Error Set_UserFunction_to_CallCenterAgent The action target vlocity_cmt_DocGenIndCmeUserPsl of type PermissionSetLicense does not exist. |
| Error Set_UserFunction_to_Developer The action target vlocity_cmt_CommunicationsCloudPlusPsl of type PermissionSetLicense does not exist. |
Every permission set license has two identifiers:
For PSLs whose key includes a prefix such as a namespace, these two values differ. The key separates the prefix from the name with a period, while the DeveloperName uses an underscore:
| PermissionSetLicenseKey | DeveloperName |
|---|---|
vlocity_cmt.CommunicationsCloudPlusPsl | vlocity_cmt_CommunicationsCloudPlusPsl |
vlocity_cmt.DocGenIndCmeUserPsl | vlocity_cmt_DocGenIndCmeUserPsl |
When you retrieve a User Access Policy, its PSL action targets refer to the PSL's DeveloperName. When you deploy the policy, Salesforce looks up a PSL target by PermissionSetLicenseKey. The DeveloperName doesn't match any key, so the deployment reports that the PSL doesn't exist, even though it does.
Use this workaround: in the retrieved User Access Policy metadata, change each PSL action target from the DeveloperName to the PermissionSetLicenseKey, then redeploy.
Copy the PSL name from each error message, for example vlocity_cmt_DocGenIndCmeUserPsl.
In the target org, run this SOQL query:
SELECT PermissionSetLicenseKey, DeveloperName FROM PermissionSetLicense
Find the row where DeveloperName matches the name in the error.
Check the result:
userAccessPolicyActions entry whose type is PermissionSetLicense.target value (the DeveloperName) with the matching PermissionSetLicenseKey from Step 1. For example, change vlocity_cmt_DocGenIndCmeUserPsl to vlocity_cmt.DocGenIndCmeUserPsl.Note: If you deploy a policy with a status of Active, its status changes to Design. An admin can then activate the policy again in Setup.
target value against the query result. Copy the PermissionSetLicenseKey exactly as the query returns it, including the namespace prefix and the period.003200531

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.