Time Slicing Sync takes an average of 2-3 minutes to run. Provided that it’s incompatible with Time Slicing, that can create a bottleneck and stop important slices from being up to date
STEPS TO REPRODUCE
On a large customer dataset with many calendars, schedule the below jobs:
Expected Results: Time Slicing Sync to be running within reasonable time
Actual Results: Time Slicing Sync is running for 2-3 min average, sometimes longer and keeps Time Slicing job in Waiting status and important slices are not getting updated
Clarity 16.1.x, 16.2.x, 16.3.0, 16.3.1
DE166275
DE166275, converted to user story
We are adding a general improvement to the query for all tables including fin_cost_plan_details, prteam, prassignment etc.