Library dependencies

If your script requires external libraries, upload the required libraries first. Then add the libraries as dependencies to the script.

After libraries are added, you can browse them in the folder structure and open the files that they contain.

Hover over an added library to view:

  • The library version currently used in the script.
  • Other available versions of the library in ION.

To add one or more libraries as dependencies:

  1. Expand the Scripts right panel.
  2. Expand the Libraries accordion.
  3. Click the ellipsis menu.
  4. Click Add Library.

    The Select Libraries dialog box lists all libraries in ION and their available versions. For each library, these details are provided:

    • Library name
    • Library description
    • GPN (Global Package Namespace)
    • GPN deployed status
    • Available library versions
    • Python runtime compatible version
    • Last updater's username
    • Last updated date

    Use the Search field to filter results by library name, description, or the user who uploaded the latest version.

    The library version identifies the uploaded version of the library. The Python runtime compatible version indicates which Python runtime version is required for that library.

  5. Select one or more libraries to add as dependencies.
  6. Select the required library version in the Version column of the Select Libraries dialog box.
  7. Review the Python runtime compatible version associated with the selected library version.

    If the selected library version is not compatible with the Python runtime version used in the environment, the script cannot be approved.

  8. Click OK to add the selected libraries to the script.

    If a selected library has missing dependencies, identify the required library name and version and import it in ION Scripting. After the dependency is imported, the error status is removed.

    Note:  Scripts that contain missing library dependencies cannot be approved. Resolve all dependency errors before approving and using the script in active data flows.

After adding a new version of a library, the library might not be immediately linked to the script within the same session. If the newly added library version does not appear as a dependency in the script, refresh the browser and reopen the script to ensure the library version is correctly linked.