Commit after TM1py-data-import
Posted: Mon Sep 23, 2024 12:57 pm
Dear community,
we are expanding our application/server by the use of TM1py. Guess, that for those of you, who work with it for years already, our current issue is familiar and you can help us:
We have two processes:
- Processes1 imports data via tm1py to a cube
- Process2 transforms the data
Both work fine, when I run them one after another. The problem arises, when I wrap the process executions into one process: Process2 does not see the imported data.
It doesn't matter, if I do the ExecuteProcess-commands both in Prolog or Epilog, or the first in Prolog and the second in Epilog.
Process2 sees the data, when I add a CubeSaveData between the execution of Process1 and Process2. So, it looks to me, that the imported data is not committed before the end of the wrap-up-process.
How can I update the data without CubeSaveData, so that TM1 sees it right after finishing the python script? Does TM1py provide a solution for that?
Thanks in advance!
we are expanding our application/server by the use of TM1py. Guess, that for those of you, who work with it for years already, our current issue is familiar and you can help us:
We have two processes:
- Processes1 imports data via tm1py to a cube
- Process2 transforms the data
Both work fine, when I run them one after another. The problem arises, when I wrap the process executions into one process: Process2 does not see the imported data.
It doesn't matter, if I do the ExecuteProcess-commands both in Prolog or Epilog, or the first in Prolog and the second in Epilog.
Process2 sees the data, when I add a CubeSaveData between the execution of Process1 and Process2. So, it looks to me, that the imported data is not committed before the end of the wrap-up-process.
How can I update the data without CubeSaveData, so that TM1 sees it right after finishing the python script? Does TM1py provide a solution for that?
Thanks in advance!