The Selections tool features a fields toggle checkbox. This is fine in an app I am building but in a published app where the assets panel is restricted to dimensions only, why does the selections tool allow access to the raw fields of a data model ?
Is there a design reason for this functionality ? Can it be changed ?
Allowing access exposes the inner workings of the script and also potentially the poorly named fields of all source tables.
Good point... Nothing worse than having someone see that you added 3 fields with almost identical names because you didn't think anyone would see them... 🙂
We are close to let customers to do beta testing of a complex app we are migrating from QV and we found users can see all fields from this toolbar. We restricted the searchbox to use certain fields, and we want to do the same with the seleccions tool. Honestly, we don't want to use the Hidden tag to list 100/200 fields! Even if we do, development would get tedious because the field names are not recognized when you type them, and we must remember to include possible new fields on the Hiddent tag list!
Would be much better to have something similar to the searchbox method. We list the fields we want to show there!
NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you only see 1 tab with the login page, please try clicking this link first: Authenticate me! then try the link above again. Ensure pop-up blocker is off.
