Skip to main content
April 27, 2022
Solved

Destination Data Units

  • April 27, 2022
  • 1 reply
  • 0 views

Omkareshwar_0-1651056357266.png

I am passing 2 Entities in the Data unit for Calculation as Entity is different in both the destinations 

So what i was expecting is that it will run as a for each loop with both the entities so it will pick enitity1 and then run the Calc and then enitity2 and then run the Calc 

what i was expecting was that the order will remain same every time it will run that is Enitity1 then Enitity2 

but what is happening is that it is first taking enitity1 and then entity2 but when i run it again it is taking enitity2 and then enitity1 in that for each loop 

to solve this i used 2 different DM steps but why it is running like this i want to know 

Can anyone explain why it is running like this ?

Best answer by ChristianW

I don't think the entity member filter is supposed to honor the order of the entities. I didn't test it, but it might even be, that the data management job is running the calcs in parallel using different processors.


Now I did test it and DM jobs are running the filtered entities in parallel and therefore no order is possible:

ChristianW_0-1651749300278.png

 

1 reply

April 27, 2022

Hi  Omkareshwar,

In your finance calc rule, can you add an api.logmessage("curEntity=" & api.pov.entity.name) and then re-run? I would then review the error log to see these two entries and note if both were executed on the same app server. I also suspect that the data units you are referencing are cached and maybe LRU is being used regardless of left-to-right listing of entities in your DM. Another thought: are you using more than one app or cons server for running DMs? 

 

Curious to know what's happening also!

 

April 28, 2022

Omkareshwar_0-1651138851577.png

 

 

 

Omkareshwar_1-1651138868356.png

I ran it again and saw the same behavior but after a while it was working fine 

I think it is a bug in the application

May 5, 2022

I don't think the entity member filter is supposed to honor the order of the entities. I didn't test it, but it might even be, that the data management job is running the calcs in parallel using different processors.