Static resources in Salesforce enable you to upload and reference various types of content, such as archives (.zip and .jar files), images, style sheets, JavaScript, and other files, specifically for use within your Salesforce organization. After onboarding a tenant, you must request the service team for the static resource file which you will use as a resource file to upload while creating a new static resource.
The static resource is used as a mapping file while syncing Quotes from Salesforce to the Conga platform.
Create a New Custom Static Resource: Ensure you create a new custom static resource in the target organization. The existing static resources from managed packages are outdated and do not work, which causes errors.
Update Mapping File with Custom Fields:If you want to sync any custom fields from the SFDC Proposal to the Conga Platform Proposal then add that field to the static resource file and also create that field on the Conga platform.
Verify Fields in Conga Platform: Ensure that the fields you add to the mapping file already exist in the Conga Platform. If not, you encounter a “metadata for field xxx not found” error.
Prerequisites
Quote field name mapping file.
Click the QuoteFieldNameMap.json file. The mapping file is automatically downloaded and saved in your system.
Do not change the file name and file type while saving this mapping file.
To Create a Static Resource in a Salesforce Org
Go to Setup > App Setup > Develop > Static Resources.
ClickNewand enter QuoteFieldNameMap in the Name field.
ClickChoose fileand upload the mapping file.
In the Cache Controldropdown, select one of the following values.
Private: Select this to restrict API access to authenticated users only.
Public: Select this to share static resource data cached on the Salesforce server with other users in your organization.
ClickSave.
The fields mentioned in the static resource file will be synced to Platform Quote during Proposal creation.
