nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Process button works with different model

DarrenYtsma25

I have a page where we control data between the different models when they need to be run as needed. As such the page itself is connected to multiple models. Data Hub, and FP&A.

I've noticed somethings strange and i'm wondering why this is happening. Usually when I change the model at the top of the page, all the process and action buttons grey out since they are in a different model so they can't run now. Which I expect.

For one singular button, I can run in the different models, and depending on what model i'm connected to it runs a different action? Just to be safe we are going to split the page now, but i'm just curious how this happens. I've tried running in dev and it does indeed run the other action

…………..

Community manager note: This post and/or comments below reference a workaround for getting API details from your browser window. Anaplan will be retiring the https://us1a.app.anaplan.com/2/0 legacy API on July 31, 2026, to enhance platform security and performance. API requests sent to this URL after July 31st will receive 503 errors. Please switch to using the recommended Integrations API.

Accepted answers

alexpavel

@DarrenYtsma25 : any object in an Anaplan model : line-items, actions, processes, modules, saved views, etc… have an internal ID and they are unique within a model, but it can happen that the exact internal ID coincide with an object created in another model.

Below are some links how to identify the internal object IDs in a model: launch in a browser one of links below:

https://us1a.app.anaplan.com/2/0/models/[MODEL_ID]/processes

https://us1a.app.anaplan.com/2/0/models/[MODEL_ID]/exports

https://us1a.app.anaplan.com/2/0/models/[MODEL_ID]/imports

..etc..

In your particular case, I presume there is an action ID that coincides with another action ID from another model.

To try to make them "unique" between the models, choose a process from a model and delete and re-create the process with the same name. It will associate a new internal object ID, hoping it will not coincide with others :).

Hope it helps,

Alex

All comments

pyrypeura

Hi, By my understanding the UX links to process IDs that are unique within a model but not across models. Due to this it might be that a process button might point out to different processes in different models.