The following limitations apply to Lifecycle Management in IBM® Planning Analytics Workspace.

  • You must have at least View permission for an asset to see it in Lifecycle Management. You are not shown assets that you don't have permission to view even if they exist in your source environment.
  • You can migrate assets that exist in the Shared folder or in your Personal folder. You cannot migrate assets that exist in other users' Personal folders.
  • You cannot import a snapshot from a newer version of Planning Analytics Workspace into an older version of Planning Analytics Workspace. For example, you can't import a snapshot that was created in Planning Analytics Workspace version 2.0.55 into version 2.0.54.
  • Websheets are not supported as an asset type. You cannot create a snapshot that includes a websheet. Websheets must be manually moved to the target environment and must be placed in the same application folder structure.
  • If you are migrating a book that contains multiple missing databases, when you remove the book from the snapshot all of the relevant warnings for that book are not removed.
  • Migration of a view puts an incorrect Modified by user in the collection even though the Modified by time is updated.
  • If you create a circular mapping of databases, all databases are mapped to a single database. For example, mapping 24Retail to 2003cert and 2003cert to 24Retail maps all databases to 24Retail.
  • When you migrate out and then migrate in to the same environment, both actions appear in the Snapshot actions chart. However, only the migrate out action appears in the log.
  • When you migrate a previously saved snapshot, you are able to select a folder name in the target environment. When you migrate a new snapshot, you must use the snapshot name as the folder name.
  • When you validate a snapshot, the validation can see only actively running TM1 databases. You can migrate a snapshot that contains validation errors if you know that the target database will be running soon.