Forum Discussion

Archana's avatar
Archana
New Contributor III
10 days ago

Cube View

Hi,

I'm trying to create a form with set of accounts in rows and column should be for adding the adjustments. Here, I do not required to pull any data from the cube. Instead I have to update the adjustments based on the scenario selected. This should be a separate form where the adjustments data should not update the existing forecast data.

POV:

 

 

 

 

 

 

Parameters in POV are defined to pull the accounts accordingly.

Rows: 

Columns:

Issue:

I couldn't get the form with editable fields. refer screenshot below.

FYI: Can Modify data for Column is set to 'True'

 

Application Properties
Cubes
Methodology
User Interface
  • Archana's avatar
    Archana
    New Contributor III
    10 days ago

    Hi all,

    I gave V#Annotation in the column member filter and it worked. S#|CVScenario|:Name(Forecast Adjustments):V#Annotation

     

    • TGG_Alex's avatar
      TGG_Alex
      Contributor
      10 days ago

      I would caution on use of V#Annotations:

      1. This v# member is intended to capture text commentary
      2. Security over these members do not obey regular cube security
      3. This breaks data lineage with regular v# members such as Periodic and YTD

      If it is a numeric adjustment , then you probably have another rule to move the adjustment from that member elsewhere?

      Just my two cents.

       

      • Archana's avatar
        Archana
        New Contributor III
        10 days ago

        I removed V#Annotation from column member filter. But instead in POV I added Annotation for View then only the form becomes editable otherwise it is not.

        currently I have like this. 

        Is this ok to do? my difficulty is the column fields is not accepting any numeric format, for Total Revenue even though I set Can Modify as 'False' it is editable.

  • 1392's avatar
    1392
    New Contributor II
    10 days ago

    If everything is a base member it should unless you have a slice security restriction, or the scenario being locked for 2024.

    • Archana's avatar
      Archana
      New Contributor III
      10 days ago

      scenario not locked. Same issue even if I choose any scenario in 2025.

      • 1392's avatar
        1392
        New Contributor II
        10 days ago

        how about the current security setup.

  • 1392's avatar
    1392
    New Contributor II
    10 days ago

    Hello,

    How about Flow and Origin members being defined in POV? Or the defined but missed in screenprint.

    Thank you

    • Archana's avatar
      Archana
      New Contributor III
      10 days ago

      I've updated POV like this. refer this screen print.