Updates the currently-viewed MU report's layout in place (the "Save Layout" action): overwrites the report's stored layout blob with the edited layout. Only the user's own custom report can be updated this way.
Permissions: All users.
Path Parameters
- Type: stringFormat: uuididrequired
Report (dashboard) identifier being viewed
Headers
- Type: stringD
C Key The Integration Key generated for API Authentication by the PAR OPS support team as part of the integration/partnership process.
Body·
Execution id whose cached edited layout should be stored
Request payload for updating the currently-viewed MU report's layout in place (the "Save Layout" action). Only the execution id is needed — the report, its name, and its folder are unchanged; only the stored layout blob is overwritten with the edited layout.
- Type: stringFormat: uuidExecution
Id requiredThe report execution/result id (per viewer instance) whose edited layout was just pushed to the server cache by the built-in save. Used to read that viewer-specific cached XML.
Responses
Request Example for post/v2/Reports/Dashboard/{id}/MuLayout
curl /v2/Reports/Dashboard/C895A81E-0C20-42C0-B2DC-EAF43F9447BD/MuLayout \
--request POST \
--header 'Content-Type: application/json-patch+json' \
--header 'DCKey: YOUR_SECRET_TOKEN' \
--data '{
"ExecutionId": "C895A81E-0C20-42C0-B2DC-EAF43F9447BD"
}'
{
"ReportName": null,
"Applied": true,
"Created": true,
"Id": "C895A81E-0C20-42C0-B2DC-EAF43F9447BD",
"FolderName": null,
"UserType": null
}Previous
Permanently deletes the MU user's own custom dashboard report and its layout. Only the user's own
custom report can be deleted; the layout blob is kept when it is still used by another report or is
locked against the user.Next
Whether the current user may publish an MU dashboard report (used to gate designer entry so a
missing Primary Unit Group Token is surfaced before any editing work is done). Also reports whether
the source report is the user's own custom report (updatable in place).