[BUG]: ___Dashboard.chapters There is an error when answering the prompts of this dashboard.

[hustontrevor]

Description

prompted Dashboards are unable to access chapters

Steps To Reproduce

Create a dashboard that requires prompt answers to create an instance. The Dashboard class has no mechanism to answer prompts and an instance is required to get the chapter list.

Code Snippet

with Connection(source_url, username, password, ssl_verify=False) as mstr_conn:
                environment = Environment(connection=mstr_conn)                
                projs = environment.list_loaded_projects()
                
                p: Project
                for p in projs:
                    mstr_conn.select_project(project_id=p.id)
                    dashboards = list_dashboards(connection=mstr_conn, project_id=p.id)
                    for dash in dashboards:
                        path = "\\".join([a['name'] for a in dash.ancestors[1:]] )
                        
                        for chapter in dash.chapters:  # !!!  fails here  !!!
                            for page in chapter.pages:
                                for viz in page.visualizations:
                                    outf.write(f"\"{p.name}\",\"{path}\",\"{dash.name}\",\"{chapter.name}\",\"{page.name}\",\"{viz.name}\",\"{viz.visualization_type}\"\n")

[NilsSchunk]

Hello,
I'm encountering the same issue with prompted documents in subscriptions.

When using the REST API to retrieve subscription properties, the response does not include the prompt instance ID. However, when attempting to modify the subscription via the REST API, the prompt instance ID is required.

Using the ALTER command doesn't work either — I receive one of the following errors:

“'prompt instance id' is required but not provided.”
“There is no Document with the given name: {ID from Document behind the subscription}”

[hustontrevor]

@NilsSchunk for updating prompted subscriptions, I've found you have to make a new content instance and provide the same prompt answers from the existing subscription. And sometimes the only path that works is to step all the way back out to the REST api.

Prompts are also tedious as you can't just copy what comes back from f"/api/subscriptions/{reportID}/prompts" and put it in the data for f"/api/documents/{reportID}/instances/{instanceID}/prompts/answers". You have to step through them all and account for potential nested prompts where you answer some, put /prompts/answers, then answer the next and put again until you get f"/api/documents/{reportID}/instances/{instanceID}/status" != 2

I also gave up on the .alter from FileSubscription and EmailSubscription as it seems to always fail with prompted subscriptions. Instead use the mstrio.api.subscriptions.update_subscription