@praveen How can I leverage server side partitioning and row level security within an Appsheet app environment? I’m assuming some sort of information about the logged in user will be used by Appsheet to choose what DB partitions to interact with?
I’ve been working towards using Appsheet database partitioning, one partition for each of my clients. This will keep their information separate from other clients. However, I am planning on using Oracle DB in Oracle Cloud, and was talking with @Stefan_Quartemont, and he said that we might be able to keep the partitioning server side which would make the Appsheet apps more simplistic.
Another piece of information to consider. I’ll have admin app users signing-up new users into AWS Cognito through a user table via appsheet webhook and AWS Lambda. When a user is created in the table, the key is CONCATENATE([DB_Partition_ID], “-”, UNIQUEID()), the email is also captured. These values are pushed to AWS Cognito as the USERNAME() and USEREMAIL(). So, I’ll have the users email to work with along with their user key and db partition id.
https://docs.oracle.com/cd/B19306_01/server.102/b14220/partconc.htm
LinkedIn
Twitter
