Why are FinDock permission set group changes reset?
UPDATE 2025-01-29 - We pushed a Core update to all orgs that handles some of the manual workaround steps outlined below. For details, see Status.
With the January '25 release to production, some orgs are seeing permission errors related to FinDock permission set groups. This is unfortunately related to the Salesforce issue that forced us to cancel our November '24 release.
We sincerely apologize for this. Based on the information we had gotten from Salesforce and our own testing, we believed the issue had been fully resolved.
How do I know if my org is impacted by the permission set group issue?
If you are not using FinDock permission set groups, you are not impacted from the FinDock perspective. Classic permission sets work as normal after the January '25 release.
If you are using FinDock permission set groups, you need to check if you are impacted. Not all orgs are experiencing this issue. We have not been able to determine the pattern of this permission set group reset behavior, so all orgs must be checked.
What exactly is the permission set group issue?
When an ISV package is installed or updated, any customization to the permission set groups included in that package may be reset. Customizations include permission sets from other packages. For example, the integration-related permission sets from FinDock payment extensions may be removed when Core is updated.
Any customizations you make to FinDock permissions sets groups, such as adding a muting permission set to a group, may also be removed when FinDock releases an update.
How do I restore permission set groups?
There is no automatic restore process. You need to manually check for missing permission sets or other customizations and add them back to the FinDock permission set groups.
Please check strongly recommend the FinDock Integration User permission set group first! This is a crucial permission set group for most payment processing scenarios.
To restore the FinDock Integration User permission set group:
- From the Salesforce Setup, go to Custom Code > Custom Settings.
- Find the custom setting
PaymentHub Settings
for namespacecpm
and click Manage. - Click Edit, mark the checkbox for Execute Initial Permission Set Adding, and then click Save.
- Launch the FinDock app and go to the classic Setup tab (not the new FinDock Setup tab). This triggers initial permission set adding.
- From the Salesforce Setup, go to Users > Permission Set Groups.
- Open the FinDock Integration user group and click Recalculate.
- Click Permission Sets in Group and do a spot check to ensure your payment extension and source connector permission sets are in the group. For example, if you are using Stripe, you should see the FinDock Stripe Integration permission set in the group.
- If you had your own customizations to the FinDock Integration User permission set group, re-make these changes as needed.
The above procedure should have correctly restored all FinDock permission set groups according to the installed and activated FinDock packages in the org. Please also check the FinDock Admin, Payment Operator and Service Agent permission set groups for package-specific sets, as well as re-make any missing customizations of your own as needed.