Filter Table based on & After form entry values

I am having challenges with a deck view that should filter once a form is submitted

i attempted “Linkedtofilteredview” as an Action but it does not seem to filter the deck once the form is saved.

More info

Form Finish View: Automatic

Action: Go to another view in app

Target:

LINKTOFILTEREDVIEW(“Care Givers Deck”, AND([Main Service Offering] = [_THISROW].[Service Types], [languages] = [_THISROW].[languages])),
“&quickedit=true”


Any thoughts on why that is happening?

Because you didn’t set your Action as the Form Saved Behavior?

Also,

I don’t believe Deck Views have quick-edit capability.

2 Likes

This was updated and i got the same results,

Anything else notable?

Thanks,
Magnor

Maybe provide more detail on exactly what you’re doing.

2 Likes

i am attempting to create a filtering form to work much like the search bar at the top,

however the filter form with multiple optional fields are options to narrow down the deck results that match filter form values

I asked for more detail, you gave me like a 1 out of 10 effort level there.

1 Like

lol sorry

Tabe 1 “Filter Form”: used to collect values to be used with filtering action “Update Results”

Table 2: “Care Givers deck” shows a list of results that may align with one or more filters in the filter form and is intended to be filtered after a new row is added in Table 1

Table 3: “Care Givers Dashboard” : has 2 views, 1st is the filtering card that points to the Table 1 “Filter form”. view 2 is “Care Givers deck”

Table 1’s Actions is mainly to save each unique filter as a new row in form, but at the same time once entry is submitted to open a filtered view, hence why i used this formula once form is saved

Action : Go to another view in app

Target:

LINKTOFILTEREDVIEW(“Care Givers Deck”, AND([Main Service Offering] = [_THISROW].[Service Types], [languages] = [_THISROW].[languages]))

“Service type” values within the filter form should be the same as “Main Service Offering”

The filter is intended to be used as a UI for narrowing down the list of care giver results (Table 2)

Hopefully that helps.

2 Likes

What is the point of the dashboard?
What steps are you doing in the app leading up to the failure?
Screenshots are best.

Dashboard is a front end view for users

you can see the section above is a button that opens up the “Filter Form”

The section below is the deck

Steps leading to failure

Once form is submitted the screen should return back to the dashboard with the new filtered results

I would not expect that to work. Try to use LINKTOFILTEREDIVEW just on the Deck view, not the Dashboard.

1 Like

Since you’re using a dashboard (which is a good idea):

  1. Create a table to contain the filter parameters. Each user should get their own row.

  2. Create a slice of the table in (1) with a Row filter condition that excludes all but the one row for the current user.

  3. Create a view on the slice in (2) of type detail. Add all columns that the user may modify to adjust the filter as Quick edit columns.

  4. Create a slice on the table containing the data to be filtered (the table used by the Care Givers Deck view). Set the Row filter condition to an expression that uses the columns of the slice in (2) to include only the appropriate rows.

  5. Create a view that uses the slice in (4) to display the filtered results.

  6. Add the views in (3) and (5) to your dashboard view.

With the above, there is no need for a form view, a navigation action, or the use of LINKTOFILTEREDVIEW().

2 Likes


Note: Add at least useremail of admin to Detail View show columns.

1.1 Create a Table with the filter Parameters
1.2 Table added to Data.

1.3 Shall the User Id have the UNIQUEID() in Formula. This is what you mean Each User will get their own row" …
to be continued…

This would require authentication right?

Also, is there not a way to link to view with filtered table view?

Nope, use USEREMAIL() or CONTEXT("Device"). Put the expression in Initial value`, not App formula.

1 Like

Nope. If your app doesn’t require logins, table (1) should have one row per user device, and slice (2) should include only the row for the current device. The current device can be identified with CONTEXT("Device").

2 Likes

Thanks Steve, ill give it a shot

2 Likes

So initial Value formula USEREMAIL() will fill rows of the Table1 with User Id as User Email. So if you have 3000 users that open the detail view in 3 then Table 1 will have 3000 rows (records added). Guess that is the way how it works. And the filter condition should be USEREMAIL(). :thinking: :thinking:

Yep. If you didn’t give each user their own row, there would be a chance one user could interfere with another, as two or more users could be using the same row at a time.

Yep.

Create this simple filter and doen’t work.

Interactive mode in the Dashboard is Active. Change the Track for One withot Records (Rows) and nothing happened.

image