Hi
Can we introduce the option to freeze Grid table totals ?
If we have a long table, need to scroll down every time we need to check Totals.
Thanks
Kudi
I agree and also would like to freeze line items on the module at record level or column level so that we don't have to keep scrolling back to see the data we need.
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.
In as much detail as possible, describe the problem or experience related to your idea. Please provide the context of what you were trying to do and include specific examples or workarounds: With the new release of the ability for end-users to lock freeze panes - I feel it would actually be materially more helpful if page…
In as much detail as possible, describe the problem or experience related to your idea. Please provide the context of what you were trying to do and include specific examples or workarounds: For UX with large grid data, Users wanted to have filters to narrow down results, issue here was they had more than 15 filters for…
Could you please allow me to see a log of the processing status of the workspace and model? Once this is achieved, it will be possible to identify the cause of the failure to some extent by checking the logs when it occurs, and the speed of response to the failure will increase.
