@MandeepGupta HI, I don't see any specific differences. Below is the current setup.

@MandeepGupta yes, we have run the second job by checking the HCM checkbox. The strange thing is that some other fields seem to work correctly with code , description and translated value columns. But it is not working for only specific fields.

@Bhaskar Konar We have only the standalone HCM. Thankyou , let me see what I can do. It seems like those steps solve similar issues that others have also faced but we need to figure out how this job can be run.

@Bhaskar Konar Thankyou, we have tried running the second job earlier too and it did not change anything. I am afraid I am quite new to this and have only been trying to investigate this from reporting perspective. When I reached out to IT regarding the first job, they were not aware of any Essbase applications so we could…

@MandeepGupta This is from the Workforce management "Worker Assignment real time" subject area. The name is Assignment attributes and attribute name is local job title. Value set is a table

When we try to run the Create Rules XML File for BI Extender Automation job, it asked for a parameter Essbase application. Not sure what this is. @Bhaskar Konar

Thanks Mandeep, but there is only one column. For some other fields, I can see code, description and translation columns but for these, it's just one field in that folder/subject area. Any other way to know if it is stored elsewhere or named something else entirely?