As an admin or an end user I would like to have ability to freeze one or a few line items from scrolling (the same way as it's available in the excel)
This is a great idea and much needed from a user standpoint.
Is this in Anaplan's roadmap?
The freeze pane option is yet to be available, however, there is a new feature to the NUX that has jest been released called synchronized scroll, that allows for similar functionality.
The synchronized scroll feature can be found in the top right corner of a grid card,
Selecting the feature will open up a panel to group the cards with similar dimensionality to be synchronized.
Name the groups accordingly, and then select the Boolean in the right corner of each card that should be in sync.
There is also an option to choose which direction the grids should be synchronized.
In this case, I chose Verticle only, because I have text fields in Grid 1, that I want to "Freeze Panes" so I can move the data left to right, without moving the Values in Grid 2, where I can make inputs, directly referencing the grid on the left.
If I put the mouse cursor in Column A Row 1, and scroll down, you can see the cursor in the column did not move and both grids scrolled vertically to the bottom. This is a very valuable feature provided by the NUX.
Need a way to periodically export all revision tags within an Anaplan model into a excel file to simplify audit and documentation process, but Anaplan currently has no native option to do this. The existing workarounds are all imperfect: the revision tags page can't be copied directly (the "Compare" pop-up only captures…
Has anyone seen this before? (1) Click a cell in an Anaplan Grid (2) Check something in Excel (3) Go back to the Anaplan page (4) Press the arrow keys After step (4), the arrow keys no longer move between cells. Instead, the Grid/page scrolls. The only way to get cell navigation back is to click a cell in the Grid again…
When you create a slicer, the displayed characteristic defaults to Caption with no way to change it. Our user community is accustomed to using Name for slicers so this has been a tough adjustment. As for now, we've been connecting an XL3 formula to the slicer output to give us the relevant information and just changing…
