Rich Text Fields
Configure Rich Text Fields for pre-processing before Sending to Salesforce. Options:
- Patch RT Images
- Replaces all Servlet/RTA Image references with their Base64 encoded image data.
- Note: Upon record insert/update, Salesforce will re-convert the Base64 body to an RTA Image.
- Patch RT URIs
- Finds and updates Salesforce record IDs embedded in RTA fields. When a record is restored or reinserted with a new ID, this option rewrites hardcoded references to reflect the correct restored record IDs
- Supported Formats:
- /001XXXXXXXXXXXXXXX
- %2Fr%2FObject__c%2F001XXXXXXXXXXXXXXX%2Fview
- https://.lightning.force.com/lightning/r/Object__c/001XXXXXXXXXXXXXXX/view
NOTE: Only IDs that can be mapped using the Restore’s ID Map or Tracker Database will be replaced. Others remain unchanged. For more information on these functions, see Restore’s ID Map Documentation, and Tracker Database Documentation.
Advanced Use: Rich Text Config XML File
Salesforce records can hold many different formats of images in URLs. Making use of this configuration file allows for the addition of different Regex strings to allow support for new image URL formats in the field.
Setup
- Navigate to “CopyStormRestore/Config” directory
- Create an xml file and save it as “SFDCRecordIdTextReplaceUtilConfig.xml” inside of the “CopyStormRestore/config” directory.
- The xml file consists of two tags:
- The config file opening/closing tag.
- Regex Entry tags. Each Regex entry tag has two components, a unique name or “type” that is a unique identifier for the entry, as well as a Regex string used to match against URL patterns. The capture group of these Regex strings needs to be the Salesforce ID of the image resource for pre-processing to be successful.
See below for the default configuration file:
Copy to Clipboard