OwnBackup aims to provide its clients with a Full & Complete backup of all the Data, Metadata, Attachments, Content Documents & Knowledgebase Articles.
In order to ensure that - OwnBackup will automatically analyze the field-level-security upon completion of every Full Backup.
If unreadable fields are detected due to changes made to profiles and/or permission, a warning will be shown on the service's dashboard that the data has been excluded with a link to a new tab ("Permissions Report") containing the report. OwnBackup also provides an actionable remediation tool.
When selecting “see report”, the option exists to export the Field Level Security Report as an XML for Profile updates.
This enables admins to update any profile with missing field/object permissions using Force.com IDE and other similar tools. See The guide below on how to deploy the XML as a permission set in Workbench.
In order to fix those gaps within Salesforce, please follow the instructions below:
Authenticated User must have the "Modify All Data" permission
A license of any installed package (that requires a license in order to access its data) must be assigned to the Authenticated User
At least Read Access to all Standard & Custom fields (can be configured from the Field Level Security page)
In case, you are using the Salesforce Knowledge Base module (KB Articles), the Authenticated User must be a Knowledge User.
*Authenticated User = The user that connects OwnBackup to the client's Salesforce org.
To immediately see the changes reflected and not wait until the next Full Backup, please run a manual "Analyze Profile Permissions" job directly from the Backup-->Options-->Analyze Profile Permissions button.
By downloading the Salesforce compatible XML you can achieve an easy method to update a permission set that can be applied to the authenticated user. Please note that Security assignments, permission sets, and profile management are the sole responsibility of the user.
View the permission report in OwnBackup in order to see the field list and download the data as a Salesforce compatible XML.
In order to create a package that Workbench can consume, we need to create a specific file/folder structure. First, create an additional file titled: package.xml which contains the package definitions:
<?xml version="1.0" encoding="UTF-8"?>
Now that the file is created, we will update the paired payload:
You should have something like this:
Via Workbench, we will be creating a new Permission Set called "IntegrationUserMissingFields" with the permission Read and Edit on all the missing fields from the edited XML.
Click on Next and then Deploy.
If the package deployed, a success message will appear under the Results.
In Salesforce, we will be assigning the permission set to the authenticated user.
Part 5: Updating the permission set file with new field data
When you need to update the IntegrationUserMissingFields permission set in Salesforce, creating a new one with the same name will overwrite it. Creating various permission sets can be messy.
See the steps below to leverage the OwnBackup Metadata backup to append the history of the already available fields for this permission set.
Sometimes you just want to talk to someone. Our customer support team is available by phone:
Monday – Friday: 3:00 AM – 5:00 PM ET
Sunday: 7:00 AM – 3:00 PM GMT