Yes. Those are permissions for Adding, Updating, and Deleting records. Those permissions do not affect whether or not certain records in a table will be loaded into the app. A very different thing.
In contrast, you could easily re-create the option you referred to in your initial post by setting a Security Filter expression, because those two things are very similar.
As the teacher said …
“and you do not want any users to be able to see existing data.”
Can’t even see this material when creating it?
Is there any specific timing?
Thank you
Yes, the users will be able to see the data they enter while entering it in the form. After the form is saved, the user will no longer be able to see the data. You (the app creator) will have access to the saved data, and can use it in other ways, such as in another app.
I have an app with a customer table and a questioner table, both have this option set to TRUE.
After filling customer customer form the app takes user to questioner form automatically. I noticed that while filling questioner form the customer name changed to customer_id. Can this be avoided and how for I still need to reference customer table while filling questioner form?
Hi. No. I am still thinking that children will “dissapear” one after the other, when I record them, before I have a chance to see parent and all that parent children at once