Custom Snap Pack precedence

Version precedence and Snap visibility rules for Custom Snap Packs.

Where you upload a Custom Snap Pack determines:

  • The version of Snaps a pipeline uses when the same Snap Pack exists at multiple levels: Version precedence
  • The individual Snaps a pipeline can access and use: Snap visibility

Version precedence

A Custom Snap Pack version always takes higher precedence over the configured environment-level Snap Pack. SnapLogic checks for a Custom Snap Pack version in the following locations, in order:

  1. The Project where the pipeline is located.
  2. A Project space shared folder.
  3. The environment-level global shared folder.

If no Custom Snap Pack version exists at any of these locations, the pipeline uses the environment-level Snap Pack version — a per-Snap-Pack version override, if set, or otherwise the environment's Usage setting (Stable/Latest) default version. This fallback applies to every Snap Pack, not only Custom ones.

Version precedence example

Your environment's Usage setting is Stable, and an Environment admin has set a version override for the Salesforce Snap Pack. Someone has also uploaded a Custom version of the Salesforce Snap Pack to the Project where a pipeline runs.

Which version runs? The Custom Snap Pack version in the Project — it's checked first and always takes precedence, regardless of the override or Usage setting.

If that Custom version didn't exist in the Project or its shared folders, the pipeline would fall back to the environment-level version: the override, since one is set. The Usage setting's Stable default only applies when no override is set either.

Snap visibility

You can upload Custom Snap Packs to the following folders:

  • Project folder in project space: When working on a project, you can create a specific folder dedicated to that project. This folder is located in a designated area called the project space.
  • Shared folder in project space: In the project space, you can have a folder shared among multiple users working on the project. It allows those users to access and collaborate on the files in that folder.
  • Global shared folder: This refers to a shared folder across different projects or spaces. It is accessible to users in various projects.

For each Custom Snap Pack, SnapLogic looks for it in the following locations, in order, and stops at the first match: the Project where the pipeline is located, then a Project space shared folder, then the environment-level Global shared folder. If a Snap Pack exists in the Project, a pipeline there only sees that Project's copy of it — Snaps from the same Snap Pack uploaded elsewhere aren't visible. If the Snap Pack doesn't exist in the Project, the pipeline falls back to the Project space shared folder, then the Global shared folder. Refer to the examples below for a better understanding.

Snap visibility examples

Most scenarios can be categorized in the examples mentioned below when creating pipelines and determining the visibility of the Snap Packs.

Example 1

If you have Snap Pack A and B uploaded to the following locations,

  • Global shared: Snap Pack A (Snap A-1, Snap A-2)
  • project space shared: Snap Pack B (Snap B-1, Snap B-2)
  • Project: Snap Pack B (Snap B-1, Snap B-3)

The visible Snaps in the Project folder are Snap A-1, Snap A-2, Snap B-1, and Snap B-3 (Snap B-2 isn't visible because it isn't uploaded to the Project).

The visible Snaps in the project space shared folder are Snap A-1, Snap A-2, Snap B-1, and Snap B-2.

The visible Snaps in the Global shared folder are Snap A-1 and Snap A-2

Example 2

If you have Snap Pack B uploaded to the following locations.

  • Global shared: Snap Pack B (Snap B-0, Snap B-1)
  • project space shared: Snap Pack B (Snap B-1, Snap B-2)
  • Project: Snap Pack B (Snap B-1, Snap B-3)

The visible Snaps in the Project folder are Snap B-1, and Snap B-3.

The visible Snaps in the project space shared folder are Snap B-1, and Snap B-2.

The visible Snaps in the Global shared folder are Snap B-0 and Snap B-1.

Example 3

If you have Snap Pack A and B uploaded to the following locations.

  • Global shared: Snap Pack B (Snap B-0, Snap B-1)
  • project space shared: Snap Pack B (Snap B-1, Snap B-2)
  • Project: Snap Pack A (Snap A-1, Snap A-2)

The visible Snaps in the Project folder are Snap A-1, Snap A-2, Snap B-1, and Snap B-2.

The visible Snaps in the project space shared folder are Snap B-1, and Snap B-2.

The visible Snaps in the Global Shared folder are Snap B-0 and Snap B-1