Guys, before saving to the Firebase database, I check if the item has already been saved. Before, when there was just the Subgroups Tag, it was easy. As I now use the Firebase Authentication UserId together with the Subgroups Tag, I don’t know how to identify duplicity.
Follow the blocks and their explanations:
Registration block.
First I check if he selected the group (A, B, C, D and E).
Then I check if the subgroup is already in the list. If so, I inform you that the chosen subgroup is already registered and I ask that another one be created.
If there is no Tag in Firebase, it is the Firebase Authentication UserId and the chosen subgroup.
I validated whether the information was within the list. If so, it would pass information to the user that the item had already been recorded and that he or she could choose another one.
Ayan, I did as you asked and even so, when I select the same subgroup it records it, that is, it does not include the information that that subgroup already exists, that is, the variable is taking the userid number.
I’m sending the project assistant. In this case I left (Designer) - Bank Properties (firebase) and Cloudinary for images blank, in case you want to test.
I created a rule for User and GroupName. When changing the Project Bucket as you asked for GroupName, I receive the Access Denied message for both GroupName and Users
Before this modification it worked normally. Allergy_Community_B.aia (195.9 KB)
Guys, any news? Can someone help me?
If it doesn’t work, I’ll try something else and end this call with no solution and I think there may be a Community user with the same problem.