Hey guys, I have the โF2LIVEโ app thatโs published to both the Google & Apple store. The appโs main purpose is to achieve one of the NPOโs goals to help people find people with similar fitness goals. I had a few suggestions from women especially to โverifyโ the identities of users, so I set up a โverifiedโ and โunverifiedโ system, with all FORM entries AUTOMATICALLY being โunverified.โ The mapโs first location layer is the FORM location and the second location layer is the GYM location. For the FORM location, I want to hide โunverifiedโ entries from the public, from the Table, Detail, and Map (VIEW). I can do this with the SECURITY FILTER if [โฆ Verification]=โVerifiedโ โฆ
But, Iโm getting a message from AppSheet that I need a PRO plan to use this function or my account will be banned in 3 days? I thought Publisher PRO allowed for all features? What should I do?
I really donโt want to show the โunverifiedโ entries otherwise the map will be full of fake/unverified identitiesโฆ Since the map auto-populates the entry once synced.
I couldnโt find a way for format rules to hide specific rowsโฆ For the Map, Table, and Detail views. Security Filter seems like the right answer.
You are probably using Publisher Pro plan which is a public app and you canโt use user authentication. When you canโt use authentication, you canโt use security filter either. Instead of security filters, you could try to slices. But please remember not to use any kind of sensitive data with your app.
Yes, itโs Publisher Pro. Itโs not sensitive information, itโs unnecessary information for the views. Security filter works via the code, but I guess based on AppSheet rules itโs not allowed to be used? Maybe I can find a work around by creating a duplicate table only for the FORM, and another table for the MAP, DETAIL, and TABLE view only for the entries with text โverifiedโ from the duplicate table. Itโs doable, I think, just thinking out loud, but it seems like a whole lot of extra steps when I can just filter entries from the original table.
I filter them not because of sensitive data, but because of the cleanliness of the UX.
You can filter the data with the slice. You need to use the slice as a source for your view.
Alright, Iโll begin looking through threads to see how to do this. Thank you!
Alright, splices were easy enough to use. Thank you for introducing them!
Youโre welcome
User | Count |
---|---|
43 | |
32 | |
25 | |
23 | |
14 |