Articles in this section

Review changes within a pull or revert

When you want to pull or revert an integration, you need to review any changes between your current integration and the remote version. Various features, including references, difference (diff) screens, and conflicts, help you analyze how your changes affect your integration.

Review changes

Conflicts

Conflicts arise when identical resources are modified between the current and remote integration. You’ll run into a conflict if:

  • The current and remote integration names don’t match:

    • Amazon – NetSuite integration

    • NetSuite – Amazon integrations

    • The same hook has edits on the same line

  • The resource names don’t match:

    • Get Amazon sales vs Get sales from Amazon

  • The same hook has edits on the same line.

Conflicts can be introduced when multiple users are working on the same integrations. To resolve them, edit either one of the integrations to match the other, then merge and pull.

Name_change_conflict.png

Refresh refresh.svg

You can use Refresh to review any changes to your integration in real time. The refresh button works best if you’re using two integrator.io webpages; one for editing and making changes to an integration and the other for reviewing merge data in real-time. This way, you can update an integration and see its effects on your merge.

Expand all Expand.svg

Expand all expands your resources so you can review all your changes at once.

References reference_button.svg

This list displays all the flows containing a reference in your account. For example, an export (Export all Salesforce leads) could be used in multiple integrations, like Salesforce – NetSuite and Salesforce – Acumatica.

Important

Any modified references (such as imports and exports) are changed for all integrations and flows. If you modify a reference you must check this to ensure that it isn’t modifying anything in a different integration.

Manage resources

Your resources appear on the Review changes screen. From there, you can review any changes to your integrations and resolve conflicts.

Important

In your JSON data, imports (including lookups) and exports are called pageProcessors and pageGenerators (PP and PG), respectively.

Caution

Modifying a resource in one integration will modify it throughout all your integrations. Check your references before making changes that might affect other integrations.

Update an existing resource

This change includes an update to an export. The method was changed to GET and the relative URI was changed to include {{lastExportDateTime}}.

Change_to_export.png

Add a new resource and delete an existing resource

This change includes a new export and a deleted export.

New_import.png
removed_export.png

New, modified, and deleted resources

This change includes new, modified, and deleted resources. Notice that the Action is available for each change (removed, update, new).

multiple_changes.png

Delete a resource shared with multiple flows and integrations

In this situation, you’re deleting an export shared between multiple flows. Exports are not linked to a single integration since they can simultaneously be used in multiple integrations. If an export is removed from a flow, it won’t be deleted from your account. Instead, references to it in the flow are removed. Always check your references to ensure you’re not deleting or editing a resource used in multiple flows or integrations.

used_by_other_integrations.png
Used_by_in_this_integration.png

Manage scripts

Scripts are commonly used in multiple integrations at once. If a script is removed from a flow, it won’t be deleted from your account. Instead, references to it in the flow are removed.

Caution

Modifying a script in one integration will modify it throughout all the integrations you use. Check your references before making changes that might affect other integrations.

Remove an existing script from a flow

In this example, you’ve removed an existing script from a current integration and then you're pulling the changes. The script isn’t deleted from your entire account, but it is deleted from the flow.

  1. Navigate to the hook you want to delete from your flow.

  2. Select your script and click None.

    remove_hook_click_none.png
  3. Save the hook.

  4. Create a pull request from the remote integration to your current integration.

  5. Verify that the script has been deleted.

    Hook_delete.png

Modify and delete multiple scripts

In this situation, you’ve modified, and then deleted, an existing script and modified a second script in a different flow. It’s important to remember that this script is not going to be permanently deleted from your account. Instead, you’ve deleted it from your flow and modified it in another.

The first script you modified and then deleted is highlighted in red to show that it was removed from your flow.

Hook_delete.png

The deleted changes in your second script are highlighted in red, and the updates are highlighted in green.

Update_script.png
Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.