Hey Venitiav,
I’ve had a similar were we have connected to Workday and update data on a nightly basis. The dataset contains a list of persons and their start data, salaries, cost centers etc. This is all information that may change during the year, and as the transactional list does not have versions, a change in the person’s salary would also impact the budget figures.
I have created a solution where I create the following metrics (salary as an example):
Metric 1:
- Name: DAT_Salary_Live
- Formula: workday_data.salarysBY SUM: workday_data.person, workday_data.cost_center]
Metric 2:
- Name: DAT_Salary_Frozen
- No formula
- Values from DAT_Salary_Live are imported into this metric during budgeting so that values cannot be changed
Metric 3:
- Name: DAT_Salary_Final
- Formula: IF(‘SET_Frozen_Period’, DAT_Salary_Frozen, DAT_Salary_Live)
- I also have a settings metric where an admin user can freeze periods on a year and version level and this is used in the if-statement
- This is the final metric that is used in further calculations and ensures that in this case the budget figures remain as they were during freezing
I keep the frozen metrics at a minimum, so that there is usually max. 5 import processes that would have to be run during budgeting. Everything is published to a single dashboard for easy use.
Another thing that could work is creating a new dimensional list of “To be hired employees” and use that to manage employees internally in Pigment. You could add a comment field where you could specify that row x refers to an intern who will be turned into a permanent employee in the future.
Hope this helps :)
