Ref to slice marked as search field, doesn't appear to respect slice clause

Hi there,

I’m building a video game collecting app, it’s all looking good except the below.

I have two tables each with a slice:

Platforms (PlatformsSlice)

GamePlatforms (GamePlatformsSlice)

There is a ref between GamePlatforms.platforms (number) to PlatformsSlice.id (number - key). This is a many-to-many reference. e.g. a Nintendo Switch can have many games and a game can be on many platforms; Switch, SNES, Gameboy etc

PlatformsSlice will only will only display rows if there is an associated row from GamePlatforms - this is working fine and excludes rows from GamePlatforms if there is not an associated platform for it.

My problem is:

GamePlatforms does have rows in it that do not match to rows in Platforms - this is intended. As some games are released on platforms that am I not interested in displaying.

My issue is when I set GamePlatforms.platforms as a search field, in my app UI, I see a multi select that includes the ID’s of platforms that the slice should not include.

When I look at the slice data those platforms in the search multi select are not displayed.

My theory is:

It appears that when a ref is pointing to a slice and marked as search, the search field actually looks at the slice’s parent table instead.

Some screenshots.

ref: GamePlatforms.platforms → PlatformsSliced.id

Search dropdown for GamePlatforms.platforms

PlatformsSliced - preview data - note [id] does not have 6,8,9,11,12,49 or 169 from the search dropdown

And the data

Platforms:

GamePlatforms

Any tips would be great!

Thank you :slightly_smiling_face:

Quite possible. The built-in filter feature was not well implemented and has several quirks.

Cool cool, thank you, love a “quirk”.

Side question: is AppSheet still in active development?

Heh. Yes, but without any obvious roadmap.