New Upload weather data from web services into TM1/Planning Analytics — Read the post →

Slice: # / ## element-name conflict

How Slice interprets the prefixes

  • # = Virtual Consolidation, e.g. #France+England.

  • ## = Virtual Expression, e.g. ##AVG(...).

The issue

Element names or aliases containing # or ## can be mistaken for Slice calculation syntax, causing normal elements to be processed incorrectly.

Workaround

If renaming elements is not possible, change the Slice prefixes to uncommon values that do not appear in element names or aliases.

  • Slice Settings → Virtual Expression Prefix: change from ## to another uncommon character or string.

  • Slice Settings → Virtual Consolidation Prefix: change from # to another uncommon character or string.

Best-practice guidance from the discussion

  • Element names and aliases should ideally avoid special characters.

  • If customers must use # in an element name or alias, they should update the Slice Settings prefixes to avoid conflicts.

Recommended action

  1. Review TM1 element names and aliases for special characters, especially # and ##.

  2. Where possible, rename elements or aliases to remove special characters.

  3. If renaming is not possible, update the Slice Virtual Expression and Virtual Consolidation prefix settings to uncommon values.

  4. Document any prefix changes so model administrators and report builders understand how on-the-fly calculations should be written in Slice.

Reference: Slice: The # / ## Element Problem i.e. Conflict with Virtual Consolidation/Virtual Expression