Thank you for taking the time to read this - I knwo I’m missing something obvious regarding perhaps the nature of the database, but after hours of trying different things, I’m clearly missing something. Any help would be appreciated. Keep in mind I am creating a mobile only app).
I have a view “directory",” where a user can see all the last names of families.
My database is set up where the “Family” data type contains a field where I can link all the members of that family to that specific family as shown here:
When I try and configure the “family_members_view” to pull all the members of that specific family (from the button that the user pushed, i.e. Smith), I am having a lot of trouble figuring out how to have the “family_members_view” pull and display information from the “member”s of the “family”
I’m asking more about the technical workflow to make this happen. I’d like for the user to be able ot click the last name and then a new page show all the 5 members of the family. For exmaple, click on Smith and then it open a new page and show the “Member” types that at all assigned to the “Family” Smith.
Privacy rules shouldn’t be an issue I don’t htink:
Ok, Privacy are a serious issue actually, you have it completely public at the moment. You probably don’t want people to be able to access that data outside of that family.
But for your workflow, you will want to send the ‘Family’ to the next page and then reference that when you search for your Family members. I suggest putting it in a parameter when using the go to page functionality. I will set up an example for you so you can see how it works.
good point - when i go live I will ensure privacy is correct. Just trying to get the funcionality wokring at the moment with some examples. I am making a mobile only app. thanks!
I was able to successfully replicate what you did on my side. Thanks so much! I spent hours trying to figure this out – now I just have to follow the concept that you demonstrated. Thanks!
Took me a while to figure out why nothing was showing up on the next view, and it turns out the main issue wasn’t the structure but how the selected Family gets passed and reused. Once that part is set correctly, everything starts working as expected. Funny enough, I’ve seen similar hidden blockers in tools like Phonexa, where one missing link breaks the whole flow.