-
REQUEST: allow this search result field to show more text in the results
Maybe just move the ‘Object Type’ column to the far right? Or put it before the ‘Name’ column as we know the max width the ‘Object Type’ column could show. The names of the modules are getting cut off. I know we can't have an infinite amount. But there's some white space that we could use.
-
SUGGESTION: Ability close all tabs to the left/right of the selected tab
Allow the Model Builder to close all tabs to the left/right of the selected tab via right click menu. It would be part of the existing ‘Close’ options.
-
MX SUGGESTION: better tab position control
Allow the Model Builder to move a tab to the front/end of the list of open tabs via right click menu. It would be options beyond the ‘Close’ options.
-
REQUEST: Ability to add/remove dimensions from the ‘Pivot’ modal while in Model view.
Give the MB the ability to add/remove dimensions from the ‘Pivot’ modal while in Model view. It seems like such an organic place to be able to do it. Similar to initial Model setup. Could also help to avoid the awkward command click method for multi-selection in the Blueprint ‘applies to’ method.
-
REQUEST: allow the model builder to change the name of an Import action before hitting Import.
Save them from needing to find that import in the Actions list and change the name there.
-
MX REQUEST: support colored blocks in Formula Editor
Allow the builder to select if the colored text in a formula is colored text or a colored block. the colored blocks would be AWESOME! Mockup: The purple would be the same as the font color was. just an inversion. like highlighting.
-
MX REQUEST: allow the user to archive portions of a MODEL!
Often I find myself taking a standard demo model and building completely new structures for a specific customer/demo. I start from a standard demo model so I can reuse structures and concepts from it. Then, when I am done, I want to keep only the new stuff and any basic structures/data that I ended up using.It would be…
-
MX REQUEST: Model Search work with ‘Applies To’ section of a module.
Allow the Model Search feature to give results where the search term shows up in the ‘Applies To’ section of a module. I could see that this level of result could get thick. Maybe it is a flag the user can check to say they want this in the results?
-
MX Request: support this modeling sequence
* Edit the formula of a Line Item that is formatted as a Number * Enter a formula, the output of which will be Text * Submit the formula * Be presented with a modal that informs me that this formula, as entered, will not work in this Line Item * The modal gives me two options: Cancel so I can modify the formula to result…
-
MX Suggestion: add some formatting to the drill-in view.
This formatting would signal to the user what lines were actually used to derive the result. Here is a mockup: I highlighted in green the portion that was actually needed to get the result. The idea would be to make these first two lines bold or something.
-
New Model Experience: Open Model from Manage Models
Not the highest priority item in the world but it would be good that when opening models from the manage models box that it opens up into the New Model Experience as that's what i've selected as my option on the homepage. Hopefully this will be being fixed as part of the migration to New Model Experience being the default.
-
Give the MB the ability to Report with a click when they hit an error.
REQUEST: give the MB the ability to Report with a click when they hit an error like this one. It would give the error logs along with the ClientSessionID.
-
Product Summary Method
It would be useful to have the option of Product as a summary method. For example, if you have a list of % discounts that all apply to one sales order then they need to be multiplied together in order to give the total discount.
-
Add MEDIAN Function to Anaplan
As we expand our use cases within our org, we are faced with more and more times that we need to calculate a Median within a data set (ex. Revenue, Median Deal Value, Median Salary, etc.). There is a quite elaborate workaround that is posted on the community, which has been a lifesaver, but it takes up to 13 line items to…
-
NEW UX: Drilldown to be formatted & have the ability to be expanded
The current drilldown functionality in the New UX is not compatible for complex formulas. It would be a great improvement if the formulas can be formatted (like in the classic) with bolded text for functions, and indentations for IF/THEN/ELSE. It would also be ideal if the drilldown window can be expanded to cater for…
-
Time Ranges with Weeks General
As a model builder working on a supply chain use case, I need to set time ranges when using the Weeks General calendar type. Our current use case requires a daily time scale, and the need to have multiple different ranges of daily data based on historicals/forecast/current week/etc. Using another week calendar type is…
-
New function to calculate 'Inception to Date'
It appears that there is no out-of-the-box function to sum all values up to the current period to return the 'inception to date' value. A new function could be very similar to MONTHTODATE and YEARTODATE but calculate from the start of the time range up to the current period (potentially with optional offset arguments).…
-
NMX - Make it easier to enter edit mode when opening the new formula editor
Now that the New Modeling Experience (NMX) has launched the 'preview mode' functionality whilst working with a formula, users have to explicitly click the 'Edit' button to be able to edit the formula. This idea is requesting the ability to enter edit mode more quickly with the new formula editor open in preview mode (for…
-
Remove the 'Edit' formula button within the new model building environment.
In a recent amendment to the new model building environment, there is now an 'Edit' button that needs to be selected before a model builder is able to amend an existing formula. This only appears when 'expanding' the formula bar. Whilst I could perhaps understand the reason for this addition in preventing…
-
Display Line Item GUID in Blueprint
I would like to have a unique identifier for every line item in a blueprint displayed either on screen or when I do an export as this will enable me to do more straightforward comparisons between models where the line item name may have changed but not the use of the line item itself. Currently I either have to a code…