When working in a multi dashboard environment it would be nice to copy modules, graphs, and/or text boxes to other existing dashboards.
I could have used this function a dozen times over the past week for both "instructions" and other dashboard elements. Specifically presenting lists utilized in many modules. Specifically Custom Version Lists for our Client
This is a good idea and something we will look address on the New UX roadmap.
This will be delivered with the New UX.
As part of the New UX you can build out your Boards using Cards. These Cards can be saved in a Card Template library so they can be reused in the Board or across other Boards. This will save time having to recreate similar charts or grids multiple times.
I regularly use the solution @sprender gave above. Once I have created a Card on a Page that I will want to use again, I create a Template of it. Now I can go to any other Page/Board/Report and add that Template in.
The created XLSX file contains an index of template report names that quick link to the related report tab. Since templates may be used to create multiple different reports based on passthrough parameters, I believe it makes more sense for the index to reference the Description given in the report book rather than the Name.
In multiple Anaplan implementations across FP&A, S&OP, and operational planning use cases, a recurring design challenge is the overuse of hierarchical lists with Top Levels, especially on large transactional or operational lists. In many projects, hierarchies are introduced early with the intention of providing “future…
Phenomenon: When the page is opened after launching the browser, FY25 is selected in the selector, but the year displayed in the grid is FY24. Current Workaround and Impact: The grid will display FY25 if the user first changes the selector in the page header to FY24, and then changes it back to FY25. Currently, end-users…
