Include or Exclude Feeder Files in Offline Packages

When creating an offline migration package in Pulse, you can control whether feeder files, views, subsets, and a Save Data operation are included.

Offline Package Options

When you select Offline Update (or Both) at the save step of package creation, three additional options become available:

• Save Data — Runs a Save Data operation on the source TM1 instance before creating the package. This ensures the files being packaged reflect the latest committed state.

• Include Views & Subsets — Includes TM1 view and subset files in the package.

• Include Feeders — Includes feeder files (.feeders) in the package. This option is unticked by default because feeder files can be very large depending on the model, significantly increasing the package size. Only enable this if feeder files need to be migrated.

Both Option

Selecting Both creates a package that contains both a Live Update (hot promote) and an Offline Update (cold promote). This gives you flexibility to apply the package either to a running instance or during a planned maintenance window.

When to Include Feeders

Feeder files are typically regenerated automatically by TM1 when a cube is loaded. However, if your environment requires pre-built feeders to be deployed, tick Include Feeders when saving the offline package. Be aware of the potential impact on package file size.