Critical impact of the release on your Integration Apps
A few of the updates in the Salesforce Spring 2020 release might critically impact your Integration App. You’ll need to provide the “direct read access” from your Custom Settings.
What’s changed?
Before the update
Salesforce allowed you to use the “read unprotected” Custom Setting on Salesforce APIs.
After the update
Salesforce does not allow you to use “read custom settings” without the Customize Application permission. If you’ve not provided the “direct read access” Customize Application permission for Custom Settings you’ll expect these changes in your Salesforce app behavior:
- You’ll not be able to read unprotected custom settings.
- A few of your Salesforce APIs will error out as they will not be able to read unprotected custom settings.
Salesforce Editions & Integration Apps affected
We've listed the Salesforce Versions, Editions and Integration Apps that are affected by the Salesforce Spring 2020 release for you.
Salesforce Versions
- Salesforce Lightning Experience
- Classic versions
Salesforce Editions
- Professional
- Note: You can create, edit, and delete custom metadata types for records from installed packages in Professional Edition orgs.
- Enterprise,
- Performance
- Unlimited, Developer
- Database.com editions
Integration Applications
- Salesforce-NetSuite v2 version
- Salesforce-NetSuite v1 version
- Open Air
Note: There is no known impact on the Salesforce-NetSuite IO version of the Integration App as this version does not have a dependency on Salesforce Custom Settings or Custom Metadata.
Scheduled changes
To know the time period for effective changes, refer to the Spring 2020 release schedule here
Who’s affected
You’re affected: if you’ve authorized Salesforce connection(s) for any of the Integration Application(s) mentioned in the list above; for roles other than the System Administrator role.
You'll see errors like:
You’ll not be affected: if you’ve authorized your Salesforce connection(s) for Integration App(s) mentioned in the list above for the System Administrator role. Your role settings will allow the Salesforce app to read Custom Settings.
Action required
Please follow the method applicable to your current Salesforce Profile Settings to ensure you conform with the Spring 2020 release updates:
Custom Profile
You’ll need to provide “View All Custom Settings” permission to the Custom Profile you use to authenticate your Salesforce Connection. If you’re a Salesforce admin with “Customize Application permission,” you can grant “read access” for Custom Settings by following these steps:
- From your Salesforce home page, click Setup.
- Search for Profiles from the Quick-Find/Search bar.
- Click the profile that you want to edit.
- Click Edit.
- Enable View All Custom Settings.
- Click Save.
Standard Profiles
For a Standard Profile, you’ll have to provide access to Custom Settings via Permission Sets. Follow these steps to provide access to Custom Settings on your Salesforce App:
- From your Salesforce home, page click Setup.
- From the Quick-Find/Search bar, search for “Permission Sets.”
If you’ve created a Permission Set already
- Click Edit.
- Click “Custom Setting Definitions.”
- Add custom settings with the prefix “netsuite_conn” to the permission set.
- Click save
To create a new Permission Set
- Click New.
- Enter the Label name and API name.
- Click Save.
- Click “Add Custom Setting Definitions” to the permission set.
- Add custom settings with the prefix “netsuite_conn” to the permission set.
- Click on Manage Assignment and assign it to the user used in the Integration App’s salesforce connection.
- Click Save.
If neither of the methods mentioned above seems to work, you'll have to Disable Updates via Schema Settings.
Disable update via Schema Settings
- Note: Salesforce recommends that you keep your org-wide setting enabled.
If you’re a Salesforce Admin, you can disable this update by turning it off via Schema Settings. Follow these steps to disable the update:
- From your Salesforce home page click Setup.
- From the Quick-Find/Search bar, search for Schema Settings.
- Disable “Restrict access to Custom Settings”.
- Click Save.
Comments
0 comments
Please sign in to leave a comment.