When using a pre-populated grid, if a user makes a selection of 'X' and the grid is populated based upon that selection and loads 100 items. Then the user realizes that selection 'X' was the wrong selection and needs to navigate back and select 'Y'.
As it is today the only way to get rid of the 100 wrong pre-populated grid items is to delete 1 by 1 or log out of GC and log back in.
Requesting that when the user navigates back from a pre-populated grid that the app has a pop-up to remove all grid items, or some other method that allows the user to remove the existing grid items.
6
Comments
Please sign in to leave a comment.
we also have the same problem, very interested to see if there is a fix for this bug
Hi there,
I can see how this functionality doesn't work as expected, and can be an inconvenience to accomplishing the task at hand. Thank you for letting us know about this opportunity to improve usability!
All the best,
Siobhan
Hi Go Canvas, has there been any updates on this bug, is there a fix as yet? This issue was raised over 1 year ago I would hope that there has been some movement here.
Howdy,
Thank you for checking in and commenting on this post!
This is how the pre-populated grids were originally designed to work, but I can understand how the functionality to clear multiple cells at once would be helpful, especially for wrong selections that populate several cells.
There is no estimated timeline on being able to clear multiple cells at once in a pre-populated grid, however I have resurfaced this Feature Request to our Product Managers for their consideration.
Hi,
Just checking, has this feature request been actioned on?
Hi Hung Tu,
Thanks for posting and bumping this request in the Community! At this time, I don't know of any changes to this functionality as described but perhaps using conditional tables would help. Each table would be pre-populated and a trigger on a previous page would determine which pre-populated grid the user will fill out. If they make a mistake, simply go back to the trigger field and choose an alternate trigger. That will hide the incorrect table and reveal the correct one.