Dynamic value local storage to be used for filtering

AppSheet AppSheet Q&A
, ,
1

I have a workflow that runs sequentially through 4 different views. The 1st, 2nd and 4th views have a common column (Patient Name and Surname), but the 3rd view does not - it is simply an action selection table.

I am struggling to filter the 4th view by the Patient Name selected in the 2nd view.

I cannot use a temp table that stores the selected Name value as the app will be used offline.

Any suggestions? Thank you!

2

If you have an inline action with the LINKTOFILTEREDVIEW(), you can pass the value(s) from the row and if you use AND() with it, you can pass multiple values even if they are not needed for the filtering itself.

1 Like
3

My problem is that the third view does not have any column that will be filtered by the second view (the third view is simply reflecting an action table). So my need is to carry the selected value from the second view into the fourth. I don’t think I can achieve this with your suggested method. Unless I am missing something?

4

Would you please explain your case a little bit more. What are you actually doing when “going” from view #2 to view #4?

1 Like
5

And when you going from view #2 to #4, are these views from the same table or do these 4 views all have their own tables connected?

1 Like
6

I have used chatGPT to help me out with this. All the data is dummy data:

Table 1: Caretaker Table (Caretaker View)

Caretaker Name

John Doe
Jane Smith
  • Primary Key: Caretaker Name
  • Purpose: Displays a list of caretakers.
  • Navigation: Uses an action using LINKTOFILTEREDVIEW() to go to the Patient View, filtering patients based on the selected caretaker.

Table 2: Patient Table (Patient View)

Patient Name Caretaker Name

Alice Brown John Doe
Bob Green John Doe
Charlie Blue Jane Smith
  • Primary Key: Patient Name
  • Foreign Key: Caretaker Name (links to Caretaker Table)
  • Purpose: Displays patients associated with a selected caretaker.
  • Navigation: Uses an action using LINKTOVIEW() to move to the Action Table.

Table 3: Action Table (Action View)

Action Name

Check Immunizations
Record Symptoms
Update Medication
  • Primary Key: Action Name
  • Purpose: This table does not contain patient or caretaker data; it simply lists actions that can be selected.
  • Navigation: Uses SWITCH(action, “Immunizations”, LINKTOVIEW(“Immunizations”), …) to navigate to the appropriate view (e.g., Immunization View).

Table 4: Immunization Table (Immunization View)

Patient Name Immunization Type Date Given

Alice Brown Measles 2024-01-01
Bob Green Polio 2024-01-15
  • Primary Key: (Composite) Patient Name + Immunization Type
  • Foreign Key: Patient Name (links to Patient Table)
  • Purpose: Displays immunization records.
  • Challenge: Needs to be filtered based on the Patient Name selected in View 2 (Patient View), but since View 3 (Action Table) does not store Patient Name, the filtering cannot be easily passed through.
7

When going to Action table with an action, you could first write e.g. the timestamp to your starting row and then when going to View4, you could read the values from that row.

EDIT: And if your app has a lot of users, you could write user’s email + timestamp so you can recognize the correct row.

1 Like