Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated the PermissionSetLicenseKey to DeveloperName #3795

Merged
merged 1 commit into from
May 29, 2024

Conversation

lakshmi2506
Copy link
Contributor

The PermissionSetLicenseKey have the naming format as SalesforceCPQ.CPQStandardPerm and the actual developer name is SalesforceCPQ_CPQStandardPerm and to avoid errors .

Replaced with the developername

@lakshmi2506 lakshmi2506 requested a review from a team as a code owner May 29, 2024 11:33
@lakshmi2506 lakshmi2506 requested a review from jkasturi-sf May 29, 2024 11:33
Copy link
Contributor

@jkasturi-sf jkasturi-sf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using DeveloperName instead of PermissionSetLicenseKey

@jkasturi-sf jkasturi-sf merged commit 8ad7eb7 into main May 29, 2024
21 of 23 checks passed
@jkasturi-sf jkasturi-sf deleted the bug/W-15805907_licenses branch May 29, 2024 12:21
@jstvz jstvz added the critical-change Listed under Critical Changes in release notes label Jun 6, 2024
@jstvz jstvz added ignore-for-release Don't include in release notes and removed critical-change Listed under Critical Changes in release notes labels Jun 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ignore-for-release Don't include in release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants