@Fields, having them anonymous is indeed a bit of a pain.
Maybe you have 2 buttons on the first page - one to login using an ID and one to generate a random ID for when they first open the app and show them a message with the ID and say they need to remember it - and you store it in a list with no other info about it - then when they open the app the second time they can use the ID to log in and you can use it to check if they've submitted something.
@Anonymous, the problem is, i don't want them to use the app after their first use, or if they do, they get blocked in the first main screen...
Achieving this is already hard, and can be very buggy.
What i want, is the user only use that app once, and don't use it anymore...
@Fields I see, that sounds something quite hard to achive. And unfortunately, I can't help you with that 😐 maybe someone else knows how to do it... if it is possible...
@Anonymous I wanna make this thread up, until someone comes here with a solution! But so far, yours have been great and helped me so far, so once again thank you!
I know i am bothering with this issue, but i wanted to make a quick update about this topic, what i got in my mind is, the person will be registered no matter what, in the sharepoint column, what i can do is, if the name of the person is Automatically on the sharepoint list, the button will hide! No need to make ID's, and it's still going to be anonymous because no person knows that view...
The code that i first tried was on the button Visible:
But it was uncessfull, then i tried this:
At this point, i am trying everything.
Maybe your ID ideia can be actually usefull, if i am able to hide it somewhere!
@Fields, I think I understand what you mean - when the person fills in the form the name will be saved automatically on the 'Created By' column, thus you can use this on the Visible property of the button:
IsEmpty(Filter(Test, Author.DisplayName = User().FullName).Author)
- this will hide the button if the user has already created an item in the list, or display it if the user didn't.
You can use this directly on the button Visible property with no other variables. I have tested and it seems to be working for me.
However, it will not delegate for some reason (the blue indication appearing on the Author.DisplayName)
Hope this helps 🙂
The filter was actually called test as well, but i was doing in the wrong app...
But it works great now! Thank you once again, and i guess you have a solution on how to do this without knowing their name... Kinda!
Check out the on demand sessions that are available now!
See the latest Power Apps innovations, updates, and demos from the Microsoft Business Applications Launch Event.
ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.
Features releasing from October 2020 through March 2021