FAQ Pulse
Provide us with clarification around the Pulse migration mechanism?
Migrating TM1 objects is complex and you should always be careful when doing a migration, therefore, it is recommended to go through the Migration section of the Pulse User Manual to get familar with the Pulse Migration feature before using it.
Elaborate on the cube data migration storage details? Migrating cube data
If Pulse can migrate all object types, but we’re not able to use Offline Cold Promote with the IBM cloud, how will it migrate our cubes and their data?
Pulse supports live migration of cube data. Views is the only TM1 object which you can’t migrate using Live data yet, this is planned for v7.3.0.
Do I need to reprocess feeders after a Pulse migration?
When Pulse migrate rules, it ask TM1 to save the rule. Pulse is not going to reprocess feeders and the rule is saved. It is up to the TM1 developer to decide if a reprocess feeders is necessary.
What is the Pulse folder structure for Git integration?
Pulse stores the change tracking information per environment and instance so the structure is Pulse for TM1\vcs\git\environment\instance
Does the Pulse Service Control work on the IBM Cloud?
Refer to this comparison table to see the different between using Pulse with TM1 on premise vs IBM Cloud: Comparison table (on-premise vs IBM Cloud)
For Pulse migrations, does Pulse move the entire file as it exists in the TM1 server’s Data folder, or does it first compare the source and target and then apply only the differences (deltas) to the destination instance?
During a live migration, Pulse applies the changes to the destination instance via REST API.
What role does the repository copy play?
The repository copy plays the role of a central, controlled source of truth for code, separating where changes are developed from what is officially stored and released. It records who changed what, when, and why and maintains a complete version history
Is the best practice to run a Documentation update on both the source and target instance right before any migration?
It is not necessary to execute a documentation update before doing a migration. Pulse checks for changes every 30 seconds by default, if you make a change to dev then you should wait for the change traking to catch the changes before you create a migration package.
If change tracking is not working in your environment, please raise a support ticket and we’ll help you to fix it.
We don’t show any .cubd files in our repository, even for small attribute cubes. Does this mean that Pulse can only effectively migrate rules and processes (and I guess chores, but we don’t migrate those)?
.cubd files are generated by Pulse when a cube data live migration is executed, Pulse should delete this file once the migration is done so they should not remain in the TM1 data folder.
“If Source Level is not enabled for a dimension, migrating a dimension via Pulse’ Live migration package creates an empty dimension with all attributes”. Does this mean that if someone chooses to migrate a dimension without the Source Level enabled, it will effectively wipe out all of the data within the related cubes?
If a dimension is migrated without Source Level enabled and the dimension already exists in the target instance, Pulse will not proceed with the migration, as no change will be detected. As a result, no cube data will be overwritten or removed. The only changes Pulse tracks for a dimension when Source Level is not enabled are attribute definitions (i.e., attributes being added or removed), not attribute values.
What is Pulse cluster Health and why it is important?
Pulse cluster health shows the status of the underlying Opensearch cluster that Pulse uses to store detailed monitoring data. Keeping the cluster in Green state is important to ensure Pulse can reliably store and retrieve monitoring data, drive Explorer dashboards, and support troubleshooting over time.
Can we use Pulse validation rules to create new rules?
Yes. Pulse includes a flexible Validation Rules engine that lets you define your own rules in addition to the built‑in ones. You manage them in the Pulse web client under Administration → Validation Rules. For full details and screenshots, see the Validation Rules article:
Validation Rules
What does "Recreate" migration package mean in Pulse?
After creating the package if we update the package using the Recreate option, it will include the latest versions of objects.
Most of the time we will create a migration package and execute it straightaway. However, if we want to execute an old package with the TM1 objects as they are today, we have to click the "Recreate" button. This feature has been introduced in v5.6.