My company is trying to implement a new request list experience on Guide, however we have found bug that potentially prevent the change to be promoted to production.
When we enabled this beta experience, end-users are able to filter-up custom fields to be displayed on the column.
Let's say that I have a custom field, that is not visible for end-users below:
On the end-user's view in Guide, the user would still be able to query up this field:
Then the column will be displayed on the frontend, even the value of the fields are not actually being displayed (There are actually values in the field, but those are visible as blank for the end-users):
Ideally the fields that are not visible for the end-users should not be visible when selecting to 'show' or 'hide' the column.
Could someone having a look at this bug so that we could deploy the change without affecting the customer experience on September?