Kindly refer to the screenshot below for the same
Hi @nehatomar,
CHECKPOINT 1: It Seems you have written the formula twice.
Write it once.
CHECKPOINT 2: Check whether SYS08 Employee Details Module is created or not.
CHECKPOINT 3: Check whether Department and Country Line item (both should be list formatted line item) are created in sys08 Employee Details module.
let me know if you are still facing.
Thanks,
Hi ,
Thank you for replying
i corrected it, still facing issues
Also SYS08 can be seen in the top left corner
i @nehatomar ,
Can you share the blueprint view of EMP02, SYS08 and EMP03 module.
Hi,
Please find below the relevant screenshots
The formula blank spaces in EMP02 are because they are all showing the same error as mentioned before
I couldn't able to figure out why it is showing error, i feel formula is correct.
Make sure you have 2 dimensions in Emp03 Module (E1 Departments and E3 Role).
Try not to write everything in the formula, instead double click the formula bar and click the required line items.
So that it should automatically populate.
or else split the formula into 3 portions to check exactly where the error occurs.
1. if Employed? then 1 else 0
2. if Employed? then Salary else 0
3. 'EMP03 Employee Drivers By Role'.Bonus %[LOOKUP: 'SYS08 Employee Details'.Department, LOOKUP: 'SYS08 Employee Details'.Role]
I wanted to check if others are facing this specification difference between Grid Card in Additional Insight. When created using a Saved View, the Quick Sum bar feature does not work, but when created using the module directly, the Quick Sum bar works.
Does anyone have any documentation on the trade-offs of having 1 model for all components of planning (service revenue, product revenue, labour planning), vs multiple models 1 for each and a consolidation model to tie it all together?
A quick reminder of the Bulk Copy functionality. Bulk Copy allows you copy large volumes of data from one slice of a model to another in a single, optimised operation, instead of using formulas or imports. Use case: copy a version (RF1) into a prior year version (PY RF1) using a versions list to allow for year-on-year…