Appsheet Set a view types default configuration

Hello,

I am building an App for a personal collection. My spreadsheet has hundreds of slices and each slice needs possibly multiple views. I was wondering if there was a way to set the Editor to pick default configuration values per view type when creating a new one. 

For example, I mainly use the Deck view and I would like to be able to set the Sort by, Group by, Main Image, Primary Header, Secondary Header, Summary Column, and other settings to the same information. The only thing that changes is the slice reference to a different collection set it belongs to. Doing this manually a few hundred times is tedious, so I was wondering if there was a better way to complete this task or a way to configure the editor to set this up. 

Solved Solved
1 5 1,601
1 ACCEPTED SOLUTION

There is a view function called LINKTOFILTEREDVIEW().   Instead of having hundreds of Slices, and then hundreds of views, to display filtered data, you can instead move the Slice filter criteria into an expression and then provide a user selectable way to view the data.

For example, you can provide Filter Selection Form with your various columns to filter by and provide choices for each that user selects:

  • Column 1 Choice - A, B or C
  • Column 2 Choice - D, E, F, G
  • Column 3 Choice - H, I, J, K, L

On Save of the Filter Selection Form, attach an action that will navigate to the view applying the filter using The LINKTOFILTEREDVIEW() function something like this:

LINKTOFILTEREDVIEW("Filter View Name", 
    AND([Column 1] = [Column 1 Choice],
[Column 2] = [Column 2 Choice]
[Column 3] = [Column 3 Choice]
)
)

This would be a much easier approach to implement (though you have already done much of the hard work creating the Slices),  it will much easier to modify and maintain, and I think will be much more performant than having all those Slices and Views inside of the app.

You can find out more on this function below

LINKTOFILTEREDVIEW()

 

 

View solution in original post

5 REPLIES 5

Not that I know of.

Consider whether you could use a single slice to serve the purpose of multiple slices by embedding your current slices' distinct row filtering criteria into various conditions within a single slice's row filter criteria.

Thank you for the suggestion! I just tested this to see if I understand your concept. I used an IF(CONTEXT("View")) function and it filters the rows to match the view name. This could work by setting up one view and then copying it and changing the name. Am I understanding your reply correctly/is this a reasonable way to complete this? 

My suggestion was rather to create, say, only 1 view and and then make the slice it's based on include the desired rows instead of creating a separate slice for each distinct collection of rows.

@WillowMobileSys's point about LINKTOFILTEREDVIEW is a great technique.

If you need more guidance, it would probably be helpful if you explained what you're trying to accomplish in the first place.

There is a view function called LINKTOFILTEREDVIEW().   Instead of having hundreds of Slices, and then hundreds of views, to display filtered data, you can instead move the Slice filter criteria into an expression and then provide a user selectable way to view the data.

For example, you can provide Filter Selection Form with your various columns to filter by and provide choices for each that user selects:

  • Column 1 Choice - A, B or C
  • Column 2 Choice - D, E, F, G
  • Column 3 Choice - H, I, J, K, L

On Save of the Filter Selection Form, attach an action that will navigate to the view applying the filter using The LINKTOFILTEREDVIEW() function something like this:

LINKTOFILTEREDVIEW("Filter View Name", 
    AND([Column 1] = [Column 1 Choice],
[Column 2] = [Column 2 Choice]
[Column 3] = [Column 3 Choice]
)
)

This would be a much easier approach to implement (though you have already done much of the hard work creating the Slices),  it will much easier to modify and maintain, and I think will be much more performant than having all those Slices and Views inside of the app.

You can find out more on this function below

LINKTOFILTEREDVIEW()

 

 

@dbaum @WillowMobileSys 

Thank you both for your replies! Based on your suggestions I was able to use the LINKTOFILTEREDVIEW() to implement a menu and filter all the data how I wanted!! With only three views and 4 slices. I really appreciate the help!

Maybe you can direct me on instructions to accomplish my next step. I want to use the interactive dashboard to create a view of multiple filters depending on user selection. I am not sure if it's possible to work the way I would like though. 
Currently, I have a menu table that stores values for filtering the data and the table for the data. I have 4 slices that filter the menu table by Brand and 4 views these are the bottom Menu items. Clicking these uses an LINKTOFILTEREDVIEW() action to then sort the menu by Set then again by Rarity before finally going to a Deck view of the data. 1 view for the Gallery and 1 view for the Deck. 
In the Dashboard, I want to have a selection form that lists the Brands and then shows the Rares from each different Set in thier own Deck Views. 
Would go something like this:
Brand 1 selected -> Dashboard displays 11 Deck views of each set. 
Brand 2 selected -> Dashboard display 6 Deck views of each set. 
etc. 

If something like this is possible I would add the ability to also select which Rarity is filtered in the view based on a second selection. 
Is it possible to Add multiple of the same Deck view in a Dashboard and have each one filter differently based on a form selection? Or is there a different way to accomplish this without creating too many individual slices and views? 

Top Labels in this Space