-
Ability to Repoint App to a new Model for the whole App instead of Page by Page
When creating a copy of the app I often need to change every page to a new workspace and model. Right now we have to click through one by one for all the pages. It would be great if you could repoint an entire app to use a different workspace and model.
-
Posting it for Wider Audience
These are my latest three articles that got published as Best Practice in this month. Please read if you haven't already done so, for they say Sharing is Caring 1. Anaplan Time Import Mappings Untangling Anaplan Time Mapping in Imports - Anaplan Community 2. New UX and Analogies Understanding Anaplan's UX with Analogies,…
-
No access to a list in new UX
I can not choose from a drop-down list in a module (as the items are grey) in the new UX. But if I open the source module, I can work with it fine. So it seems that the access right to the module and the list is fine. Anybody knows why? Thank you!
-
view associated to a dashboard
Hello - How do I find out which view a dashboard is associated to ? I have to disable the edit on a dashboard. I was wondering how to do this ?
-
NUX fixing the Y Axis of a graph
Hi, I have a page that has 2 graphs side by side (shown below). Users will change information on other pages in order to compare the 2 scenarios in these graphs. As the values will change in the scenarios, the Y axis scale varies. For ease of comparison it would be good to fix the Y axis to a certain value. Is there anyway…
-
New UX - Worksheet Main Grid Edit Mode Issue
When I start the edit mode in worksheet, I can see the selector setup on the top. However, once I use the "Select view", no matter change has been made or not. After I click "Next" follow with "Update" to come back to the main screen. The selector setup on the top disappear. I found it is very annoying that I need to…
-
How to retrieve Logged in User into a Module
Dear Community members, We are facing an issue while trying to retrieve the Logged in User into an Module, to figure who (User) made the changes to the line items.There is no built-in-function available in Anaplan to retrieve the Logged in User Name. My Model contains 2 ListsUser List - 1800 items Customer Flat List -…
-
Tooltip for Cells
Hi Team, Is there anyway to create Tooltips for individual cells? I know you can create them for a module but I require more detail @Hayk I saw that you requested this in the Idea Exchange & also you mentioned a workaround involving involving a formula which displays in the drill down window....any chance you could explain…
-
New UX Summary - Updated numbers not shown
New UX Summary does not show 'Updated' numbers. Example, export 3.2 Same when run in Classic it shows Updated numbers.
-
Create a hierarchy graph type
The hierarchy view for the workspace admin is very useful but unfortunatley we cannot produce a graph that replicates this functionality for the end users. As partners, we've been regularly asked by our clients to provide more graph related views of the underlying structure and data. The idea of such a graph would be that…
-
5.05-04 Ensure view filters are optimized
Only use one filter criteria...If more are needed, combine them into one line item Related to Rule: 4.02-01 Use efficient filters Best Practices article: Filter Best Practice
-
5.05-03 Split views for List and Module imports
Create two views from a source module. One for the import to the list (using name, code and parent), and a view for the attributes to the associated System module Related to Rule: 5.05-02 Only include what is needed
-
5.05-02 Only include what is needed
Only include the line items that are required for the import. Create multiple views if the module is used for different imports. The number of columns in the view does affect the speed of the import. The fewer the columns, the faster the import will be
-
5.05-01 Naming Convention
Keep it simple. Export, Build etc. There is no need to include the module name in the view name Best Practice article: Naming Convention
-
4.02-15 Limit modules with many formatted list line items
Too many list formatted line items displayed on a dashboard can adversely affect performance especially if the lists are large. Try and limit the number of displayed line items in a single module; split them into separate modules if necessary
-
4.02-14 Enable Personal Dashboards
Use Personal Dashboards to enable users to personalize the views of the data Related to Rule: 6.04-03 Master Dashboards Best Practice article: Personal Dashboards - Tips and Tricks
-
4.02-13 Store image URLs in a separate module
Keep all of the image URLs for a list in a separate System module. Be mindful of the correct dimensionality Related to Rule: 2.01-04 Use the D.I.S.C.O. Methodology for Module Design
-
4.02-12 Avoid using Delete action buttons on dashboards for end users
End users could potentially delete historical data, so keep the list element maintenance separate as part of the administration process Related to Rule: 4.02-11 Publish Process Actions instead of Import/Export Actions
-
4.02-11 Publish Process Actions instead of Import/Export Actions
Import and Export actions need to be republished if modified or replaced, whereas Process Actions are always consistent with whatever is held within the Process, making management easier Relate to Rule: 5.01-02 User Facing Actions in a process
-
4.02-10 Turn off the Module name
Use dashboard text to describe the grid, rather than display technical module names Related to Rule: 2.01-01 Naming Convention Exception: 4.02-10a Space Saving: If screen space is at a premium, heading text can take up more space than desired, but do consider the overall user experience and don't clutter up the dashboard
-
4.02-06 Deep Level hierarchies
Create a separate dashboard with selection modules to keep the main dashboards clean. This also allows for more efficiency navigation up and down the hierarchy tree
-
4.02-04 Add Page Selectors rather than module selectors
Use separate page selectors rather than module page selectors, especially if the dimensions are repeated in multiple dashboard elements Related to Rule: 4.02-05 Turn off module page selectors
-
4.02-03 Consider the screen size of the end users
Don't build based on your screen size. Consider the smallest size that users will be viewing the dashboard and build to that size. You should change the screen resolution to double check how the dashboards will look for the end users Related to Rule: 4.02-02 Avoid horizontal scrolling
-
4.02-02 Avoid horizontal scrolling
Try and avoid the screen scrolling horizontally. It is better to fix the grid and scroll within the grid Related to Rule: 4.02-03 Consider the screen size of the end users
-
4.02-01 Back to front design
At the beginning of the design process, take the user stories and the UX Principles. Start with the end in mind Best Practices article: Designing Dashboards
-
Import Action Categories and Separators
The import action management section often becomes messy because ALL import actions are saved. Would love the ability to create sections and separators, to better organize the import actions I intend to repeat. The following example was created from dummy imports, but it would be great if this feature were built in. I…
-
Confidence Bands/Prediction Intervals - Visualization Enhancements
A really valuable addition to the platform would be better ways to visualize uncertainty. In many parts of planning, particularly those that highly leverage analytics, thinking in terms of probabilities is important. If there’s a relatively simple way to add in this type of visual (confidence bands, prediction intervals,…
-
User Role Notes
It would be helpful to have a Notes function in Users Roles to be able to describe the workgroups typically using that role. Especially with new UX pages now crossing multiple models additional roles are needed to facilitate the cross-model access.
-
Warning A page with this name already exists
Using the new UX. I have a copy of a page named "Color Map - DEV" so I can make changes without breaking the production copy, named "Color Map". Now I'm ready to move the DEV copy into production. I rename the one in production to "Color Map - prior prd"...and i try to save a duplicate DEV page to production named "Color…
-
Allow 'Select Levels to Show' for the Time Dimension
As a model builder, it would be really great to be able to use the 'Select Levels to Show' on the time dimension. This would allow me to quickly show only base level data or quickly show only summary level. It could be tied to the model settings, so only the summary levels that exist in the respective time range would be…