-
Notifications
You must be signed in to change notification settings - Fork 244
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
W-15805907: assign_permission_set_licenses accepts the api_names in either developerName or the PermissionSetLicenseKey #3798
Conversation
… bug/W-15805907_licenses
…ssion_set_licenses takes either the developername or permissionsetlicenseKey
Hi @jkasturi-sf @jstvz @vsbharath Please review the PR Thank you |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change requested: Please update the task_docs
to mention that api_names
can contain DeveloperName
or PermissionSetLicenseKey
. Other comments optional.
Hi @jstvz Combined the queries into one, updated the task docs. Please review the PR |
To handle the compatibility issues and ensure smooth functionality for both
get_available_permission_set_licenses
andassign_permission_set_licenses
, you can make the following adjustments:Revert
get_available_permission_set_licenses
to ReturnPermissionSetLicenseKey
:Update
assign_permission_set_licenses
to Accept BothDeveloperName
andPermissionSetLicenseKey
:DeveloperName
orPermissionSetLicenseKey
, ensuring it can correctly interpret and process both formats. This adjustment will resolve issues with names likealpha.beta
where theDeveloperName
isalpha_beta
. Accepts api_name asalpha_beta
oralpha.beta
and assigns them correctly