Versions Compared

Old Version 2

changes.mady.by.user Ryan Taylor

Saved on

compared with

New Version Current

changes.mady.by.user Ryan Taylor

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The following steps allow for a user to Export & Import a Data Import Job ProfileProfiles, including all sub-profiles (Match, Action, etc.), from one tenant to another using API calls. See below for step-by-step instructions and a demo recording for using this functionality.

Preconditions:

Before completing following steps, user must be authenticated into necessary tenants using preferred API platform. For more information on how to get started using API calls with FOLIO, see this page here on using Postman API software: Getting started with Postman

Instructions:

Panel
panelIconId1f4e4
panelIcon:outbox_tray:
panelIconText📤
bgColor#F4F5F7

Export

  • Use GET call for {SOURCE TENANT API BASE URL}/data-import-profiles/profileSnapshots/{JOB PROFILE ID}?profileType=JOB_PROFILE&jobProfileId={JOB PROFILE ID}

    • Example: image-20241029-144137.pngImage Removed

      image-20241029-144137.pngImage Added

  • Send GET call

  • Response will include all necessary details of targeted Job Profile

    • Example: image-20241029-144259.pngImage Removed

      image-20241029-144259.pngImage Added

Panel
panelIconId1f4e5
panelIcon:inbox_tray:
panelIconText📥
bgColor#DEEBFF

Import 

  • Use POST call for {DESTINATION TENANT API BASE URL}/data-import-profiles/profileSnapshots

  • Copy entire response from the previous Export GET call and paste it into the Body of this POST call

    • Example:
      image-20241029-144440.pngImage Removed

      image-20241029-144440.pngImage Added

  • Send POST call

  • Once you Send this call, you should see the desired Job profiles begin to appear in the destination tenant

Demo recording:

Export and Import Data Import Job Profile via API.mp4

Additional information:

  • The functionality described above was introduced in Ramsons release

through work

  • .

  • Work to support this functionality was completed by Folijet team via the following projects:

    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyUXPROD-4348

&

    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyUXPROD-3556
      .

  • Backend information on the approach taken to implement this can be found here: