SAP Analytics Cloud: Newly Created Members Delay In Story and Data Action

[vissaagen]

Hello

In SAP Analytics Cloud, I have a 2 steps process:

1. Creation of Members through Scripting.

        PlanningModel.createMembers("DimensionName",MemberArray );]

    2. Call Data Action  (through script) with the new members as parameter

          DataAction1.setParameterValue("DimensionName", MemberArray);
          DataAction1.execute();

My requirement is to execute both steps sequentially but there is an inconsistency with the create Members step. Even though the members are created (verified though debugging and also refreshing the dim table), there is a delay (sometimes consequential) between the time of member creation and availability in both stories and Data Action. Therefore, the Data Action fails because newly created members are tagged as invalid even though they are already in the dimension table. The volume of the data is not a factor here as there is no clear pattern on when there is a delay or not.

• I have tried refreshing both the table and the application before calling the data action but that does not help.
  
• I have tried reading if the member is created in the dimension table before calling the Data Action but that is also not working since the newly created member is not detected yet in the Data Action even though available in the dimension table.
• I can't use a delay mechanism here as it varies a lot

Eventually ,the story and DA will detected the new members and execute properly but the delay does not make this a viable option since the process needs immediate execution.

Is there another kind of refresh and configuration that can help with this? 😞

[david_ings]

Hello - I have used the create member followed by a data action several times and have not encountered a delay. The data action is able to pick up the new member straight away within the same script without delay timers etc.

When the data action fails I've found instead it's caused by the syntax of the dimension member you are passing across. For example passing a member without a hierarchy you can just pass the ID, but if passing a member to the data action from script that is in a hierarchy, then you have to add the full technical hierarchy information around the ID like below:

var id = InputField_ID.getValue();

var id2 = "[DIMENSION].[H1].&["+id+"]"; // restate ID so that the Data Action can recognise this

..then id2 is passed to the DA

DataAction_1.setParameterValue("DIMENSION",id2);

Just want to check this is not the issue first as I've not experienced any delays before upon master data creation.

David

[priyanka_Y]

Hi David, We tried to pass the Parameters by var id2 = "[DIMENSION].[H1].&["+id+"]"; but we are still facing the same error. Please suggest.

[david_ings]

Can you pass a screenshot of the data action monitor please, showing the parameters being passed?

[priyanka_Y]

Hi David, Thanks for your Reply. We are able to pass the Dimension Member to Data Action Script..