New UX Idea - Apply one more model source to all pages of the app at once

I wrote a script to do this, given two lists, one of source models, and one of target pages. PM me for more info 🙂 

Definitely needed. @kevin.cho I will contact you re: the script, if that's ok :-)

Just leaving this here - the call to update this via the API is:

PUT 
https://us1a.app.anaplan.com/a/springboard-definition-service/pagemodels/{page_id}

request body is a json payload with structure:

pageModels is an array of objects with modelId and workspaceId as keys

updated_model_payload = {}

updated_model_payload['pageModels'] = [{'modelId': '{your_model_id_to_update}', 'workspaceId': '{your_workspace_id_to_update}'}]

updated_model_payload['isAlmEnabled'] = True

isAlmEnabled allows multiple models to be set. If you only need one, then you can set this to False.

Request headers is at minimum Authorization with AnaplanAuthToken - similar to other Anaplan API requests

Yeah your body is formatted incorrectly. My example above wasn't meant to be copied directly, you need to pass a json payload instead. My code was just ripped from my existing Python script.

These curl statements might help explain it cleared

curl --location --request GET 'https://us1a.app.anaplan.com/a/springboard-definition-service/apps/{app id}' \
--header 'Authorization: AnaplanAuthToken {{token}}'

To update pages:

curl --location --request PUT 'https://us1a.app.anaplan.com/a/springboard-definition-service/pagemodels/{page id}' \
--header 'Authorization: AnaplanAuthToken {{token}}' \
--header 'Content-Type: application/json' \
--data-raw '{
    "pageModels": [
        {
            "modelId": "{model_id}",
            "workspaceId": "{workspace_id}"
        },
        {
            "modelId": "{model_id}",
            "workspaceId": "{workspace_id}"
        }
    ],
    "isAlmEnabled": true
}'

You can import these curl statements directly into Postman and then update the {parameters} as you wish.

Hi @kevin.cho - just out of curiosity - I was trying to implement an automation idea of getting all the list of page id's for a particular app and then get them updated in a cyclic fashion.

One edge case that comes to my mind is most apps will have a combination of Hub / Spoke Pages. In this case - have you explored any segregation logic that will ensure that only the intended pages we want to update are taken in the cyclic update.

Eg:-

App has 4 pages - 2 pointed to DH Dev and 2 to Spoke Dev

I update my logic with the WS & Model ID for DH Dev and DH QA and the app id

1. Logic first fetches all the pages for the app id passed - 4 pages received
2. Segregates only page id's that are currently pointed to DH Dev so our operating pool is now - 2 pages
3. Now the logic for the springboard should only take those 2 pages and get them updated to DH Dev and DH QA

PS The out of the box functionality should also allow to remove models as source from one, more or ALL pages , in bulk.

This is to prevent this issue :

causing the "Manage Models" functionality to stop working