Skip to main content
Sudhakar8990
Member
Sep 30, 2026 11:04 PM UTC
Solved

Form annotations cleared when workflow Import/Validate/Load is re-run

Hi Team,

We're seeing user-entered annotations cleared during the workflow load process, while the associated data is preserved.

Setup

  • Our import process loads data and annotations for one set of accounts/sub-accounts.
  • A separate set of accounts/sub-accounts is entered manually by users through Forms, CubeViews, or QuickViews.
  • We have confirmed that the annotations from the import and the annotations entered by users are stored under the same Origin member (O#Import). They differ only by UD1 (SSSS1 vs. SSSS2).

Sample intersections

Import-loaded annotation:
E#EEEE:S#FW:T#2027M12:C#Local:V#Annotation:A#AAAAA:F#PL_Load:I#0000:O#Import:U1#SSSS1:U2#DDD:U3#LID_001:U4#Form_Input:U5#None:U6#None:U7#None:U8#None

User-entered annotation (Forms):
E#EEEE:S#FW:T#2027M12:C#Local:V#Annotation:A#AAAAA:F#PL_Load:I#0000:O#Import:U1#SSSS2:U2#DDD:U3#LID_001:U4#Form_Input:U5#None:U6#None:U7#None:U8#None

Timeline

  1. Sep 28: Ran Import, Validate, and Load. Data and annotations exist for SSSS1.
  2. Sep 29: A user entered data and annotations through Forms for SSSS2. Data and annotations now exist for both.
  3. Sep 30: Re-ran Import, Validate, and Load. Data still exists for both, but the user-entered annotation (SSSS2) was cleared. Only the imported annotation (SSSS1) remains.

Question

Our current theory is that the load clears at the data unit level for the Import origin. Since both annotations live under O#Import, the user-entered annotation is wiped even though SSSS2 is not part of the import file. The user-entered numeric data is not affected, which suggests it is stored under a different origin.

  1. Is this expected behavior, with the load clearing all V#Annotation data under O#Import for the data unit regardless of UD1 or which intersections are in the file?
  2. Is there a way to scope the clear to only the intersections being loaded, for example through the Load Method (Replace vs. Replace Background), Data Source settings, or Workflow Profile settings?
  3. If not, what is the recommended design to keep manual annotations safe from re-imports? For example, a separate member, scenario, or a Forms-specific origin.

Has anyone run into this or found a workaround? Any guidance would be appreciated.

Thanks in advance!

Sudhakar8990Answer
Member
Oct 1, 2026 6:06 PM UTC

Update: this turned out to be expected behavior of the Workflow Data Unit, not a bug.

What's happening

  • The workflow data unit is made up of Cube, Entity, Parent, Time, Consolidation, Scenario, and Account. Every other dimension (View, Flow, Origin, IC, UD1-UD8) is not part of its definition.
  • Clear, load, and lock all operate at that level. When our import (the CAE_Load process) runs, it clears every intersection under the data unit combination, for example C#Cube:E#Entity:S#ForecastWorking:T#2027M12:C#USD:A#AAAAA:O#Import, across all other dimension combinations.
  • Our user-entered annotations sit under the same Account and O#Import as the imported ones. They differ only in UD1 (SSSS1 vs. SSSS2), and UD1 is not part of the data unit, so they get wiped when the import re-runs.

This is why the Forms-entered annotation disappeared while the Forms numeric data survived. The clear is scoped to O#Import, and the numeric data is stored under a different origin.

Suds
View in thread

1 reply

Sudhakar8990AuthorAnswer
Member
Oct 1, 2026 6:06 PM UTC

Update: this turned out to be expected behavior of the Workflow Data Unit, not a bug.

What's happening

  • The workflow data unit is made up of Cube, Entity, Parent, Time, Consolidation, Scenario, and Account. Every other dimension (View, Flow, Origin, IC, UD1-UD8) is not part of its definition.
  • Clear, load, and lock all operate at that level. When our import (the CAE_Load process) runs, it clears every intersection under the data unit combination, for example C#Cube:E#Entity:S#ForecastWorking:T#2027M12:C#USD:A#AAAAA:O#Import, across all other dimension combinations.
  • Our user-entered annotations sit under the same Account and O#Import as the imported ones. They differ only in UD1 (SSSS1 vs. SSSS2), and UD1 is not part of the data unit, so they get wiped when the import re-runs.

This is why the Forms-entered annotation disappeared while the Forms numeric data survived. The clear is scoped to O#Import, and the numeric data is stored under a different origin.

Suds
Terms & ConditionsAccessibility statement