Find occurrences of a Dimension code without hierarchy

DeepakK · 2023-05-10T15:14:13+00:00

There was an error rendering this rich post.

Hello all,

I'm stuck on something. I have a Job dimension that has Job code and Job name. (100 - Tech I)

That Job flat list is not in a hierarchy.

But I've created another list called JobL5 that has the Department as a Parent. Each dept will have several jobs listed underneath. And the same job can be in several depts.

I want to create a dashboard where I can click on the Job code and have another grid show me all the different depts that have that job.

Any thoughts?

Accepted answers

All comments

rob_marshall

@DeepakK

I assume the Display Name for the Job in the hierarchy is list formatted to the Job Flat list? If not, please do that. Same thing with the Department L4, also assuming you have a Dept Flat list.

Create a SYS Job Code L5 properties module that is only dimensionalized by Job Code L5. Create a line item called Parent with the formula being parent(item(Job Code L5)). Create another line item called Link to Department Flat with the formula being: Department L5.Display Name[lookup: Parent]

Create a module that is dimensionalized by Job Code L5 and Department Flat. Create a line item (boolean formatted) with the formula: SYS Job Code L5.Link to Department Flat = item(department Flat) and use this for your filter.

Pretty sure that will work.

Rob

DeepakK

@rob_marshall I tried this and it's not working quite right.

When you say Display Name for Job in hierarchy is List formatted, is that the list property in Job hierarchy?

I have a properties module with Item(Job L5) which I'm using instead. Will that not work?

rob_marshall

@DeepakK

I believe you said the Job L5 is a numbered list, is that correct? If so, you will/should have a Display Name property to display the name - that should be list formatted to Job Code Flat. Your next question is why am I asking for the Display Name to be list formatted instead of Text. Well, first, text is a performance hog. Second, if the name of the job code ever changes, you change it in one place (Job Code Flat) and it will automatically change it every where. If that display name is text formatted, then you will have to run a job/action to update the name. Lastly, having it as list formatted back to the flat list gives you a breadcrumb to get any metadata information stored about that job code on the SYS Job Code module without having to use a finditem()

And I think I told you incorrectly above, the filtering module should be Job Code Flat by Department flat.

Quick Links

Can you help?

Unanswered questions

Action to copy data from one version to another version only for a specific module
Ideally, I would like to setup an action that can copy data from one version to another only for a specific module. For every new version I create, I import new data into certain modules and then I manually copy data over for a specific module. I am wondering if I can just setup an action to select an origin version,…
Where can I find export file after running export process using machine task in a workflow?
I am testing export actions using workflow but its not generating any file when I am running the workflow, but the same process is generating export file when ran from the Actions→Process section. Is their any issue with the workflow functionality? Also, If I want to generate a file after completion of workflow and pull…
Automating Flat File Uploads to Anaplan Data Orchestrator (ADO) – Best Practices and Methods
Hello Anaplan Community, I am seeking guidance on the most effective ways to automatically upload flat files to Anaplan Data Orchestrator (ADO). Currently, our process involves loading flat files to an Anaplan Datahub using Anaplan APIs and custom Python scripting. With Anaplan Data Orchestrator's capabilities for data…