Salesforce

Import/Export of Integrations

Printable View
« Go Back
Information
Import/Export of Integrations
import-export-of-integrations
Article Details

Overview

To facilitate the transfer of integrations between domains, the import/export functionality can be used.

Please note:

  • The integrations being imported must be uniquely named or the import process will fail with an error reporting the integration(s) already exist (see below)
  • The relationship between integration and forms/processes can be confusing when they are exported and imported. Importing a form does not also import all attached integrations. Rather, when a form is imported, the integration ID is 'remembered' by the form, but the integration will not actually show up in the form until the integrations have been imported into Integrations Manager. 

Single Integrations

To export a single integration:

  1. Open the integration you want to export in Integrations Manager.
  2. Click on the cog: exporting integration
     
  3. Select Export. This creates a JSON of the integration.

Another option is to copy the integration, eg. Open up the one you want to copy in one browser then open up integrations in a new browser tab and create a new one - then simply copy and paste the elements you want from one to the other

To import a single integration, you will follow the same process as importing bulk integrations (described below).

Bulk Exports

It is possible to export integrations in bulk. Integrations can be filtered by category and by type to make this process easier and more intuitive.

Export All Integrations

bulk export

Select Bulk Export from the left hand menu as shown above

export all integrations

A select-all checkbox has been added to the list of integrations available for export. This allows all integrations to be selected with a single click where they would previously have to be selected individually. To complete the export, simply click 'Bulk Export' from the left-hand side.

Export Specific Category Integrations  

Integrations can also be filtered by category type and then manually selected as a group using the check box against each integration - to provide a subset for export.  Having selected by category, do not then use the 'All' checkbox at the top of the list, as this will select all integrations rather than the filtered category.

export by category

 

Bulk export of selection of integrations 

To export a number of integrations at once:
Select all integrations you want to transfer by ticking the relevant boxes:

select integrations

then to export - simple click Bulk Export from the left hand side

bulk export


 

In each of the above options a  single JSON file of all selected integrations will be created. 

To Bulk Import

To import a single or group of integrations at once:

  1. Select Bulk Import from the top left menu in Integrations Manager:bulk export menu
  2. Select the JSON file of the integrations you want to import.
  3. The integration(s) will be imported into Integrations Manager. 

    Note: Safari and older IE browsers will show the file content instead of a download dialog. Use "File" > "Save as" for these browsers

If importing to the same environment (as a way to bulk copy integrations) then you must edit the file to change the integration name - eg. Export the integration you want to duplicate, edit it in notepad++ and change the contents of the "Name" and save the json file. Then reimport, the import process will create a unique id.

It is prudent to check that the correct  integrations are attached to a process after "moving" integrations and processes.

Notes: 

  • If you try to import an integration that has the same name or same ID as an existing integration, you will see an error and the integration will not import. This will also happen if you try to import an integration that has an invalid .json file structure (if the import involves multiple integrations, the duplicate integration will fail to import but other unique integrations will import).
  • If you are importing an integration that uses a System or LIM that does not currently exist, you will see an error BUT the integration will still import. You will then need to manually change the System or LIM in order for that integration to work by clicking 'Edit' next to the relevant integration.
body {<br /> font-size: 15px;<br /> line-height: 22px;<br /> }<br /> <br /> li {<br /> padding-bottom: 10px<br /> }<br />
 

Further useful reading:

 
     
     
     

    top of page


    body {<br /> font-size: 15px;<br /> line-height: 22px;<br /> }<br /> <br /> li {<br /> padding-bottom: 10px<br /> }<br />
       
      • When you export a process, the integrations do not get exported with it. You need to import the integrations separately, with matching IDs. The IDs are stored in the process definition, but will not show that it should run. If no integrations are on the site with those IDs, 'No Integration error' will show.
       
      • Integrations that have a name starting with 'cc' (eg. 'cc Log Update') will fail to import

       
      Powered by