Skip to main content
A
Ashu_Aswal
October 15, 2024
Solved

How to clear the VarianceExplanation comment

  • October 15, 2024
  • 1 reply
  • 0 views

Hi All,

is there any way to clear the added comments in V#VarianceExplanation/V#Footnote using rule or any other method. I tried using rule but it's not working as expected. we are storing our comments at parent entity and mostly Top members in UD dimension , please let me know if any other information required.

our intersection where we are storing the comments:

E#ParentEntity:P#?:C#USD:S#ActualComment:T#2023M9:V#Footnote:A#acc:F#EndBal:O#Top:I#Top:U1#TotOPU:U2#Top:U3#Top:U4#Top:U5#None:U6#None:U7#Top:U8#Top

Best answer by db_pdx

Two potential options:

1) The Manual Route:

  • Navigate to any Cube View where a comment is stored.
  • Right-Click the comment/the cell containing the comment ->  Data Attachments for Selected Data Unit
  • Delete comments as required using the delete button 'X'
  • Note: this works because you've indicated comments are stored in the same entity/scenario (thus the same Data Unit)

2) Automated / BR Route

  • Write a SQL Delete Statement in an extender BR
  • Make sure you have your criteria setup appropriately so that you are only deleting the comments you want to target
  • !WARNING! its possible to royally screw things up using raw SQL statements. Caveat emptor.

I'd advise option 1 purely from a safety standpoint.

1 reply

D
db_pdxAnswer
October 15, 2024

Two potential options:

1) The Manual Route:

  • Navigate to any Cube View where a comment is stored.
  • Right-Click the comment/the cell containing the comment ->  Data Attachments for Selected Data Unit
  • Delete comments as required using the delete button 'X'
  • Note: this works because you've indicated comments are stored in the same entity/scenario (thus the same Data Unit)

2) Automated / BR Route

  • Write a SQL Delete Statement in an extender BR
  • Make sure you have your criteria setup appropriately so that you are only deleting the comments you want to target
  • !WARNING! its possible to royally screw things up using raw SQL statements. Caveat emptor.

I'd advise option 1 purely from a safety standpoint.

A
Ashu_AswalAuthor
October 16, 2024

Thank you so much db_pdx . 

Terms & ConditionsAccessibility statement