Slice with one result

[coldcoffee]

Hello

I'm creating a map that uses two tables.

i start in a detail view of row A from Table 1

i have an action which takes me to a map view showing on the map all Table 2 rows whose latlong is within 10km of row A's  latlong

i'd like the Map View to also display Row A from Table1 

so far i can only get it to show me all the rows from Table1

I tried to create a slice of Table 1 - with the only row in the slice being current row A from above

not working!

[AleksiAlkio]

One way is to create a "Sequence of actions" where the first action writes a timestamp to your record in table A and the 2nd opens the map view with your filter. Then create a slice showing only the latest record based on the timestamp and use that slice as a secondary source to your map view.

[coldcoffee]

That sounds good and simple to test out, since
I already have a series of actions in place - i write the distance I want the other records to be from the record in question, and then do the filtered view action.

So there’s no way to just filter the slice based on the uniqueID ?

[AleksiAlkio]

Somehow you need to say for the slice what the correct row is.

[coldcoffee]

Someone asked what my condition is for LINKTOFILTEREDVIEW

I’m not at my computer but from memory it’s like this

Action 1 : inputs the [CustomDistance] and writes it to the current record

Action 2 : takes me to the map

LINKTOFILTEREDVIEW(“Custom Map”, DISTANCE([Map], theother[Map]) < [CustomDistance])

At this point I am having to close the map and go back to the detailed view each time I want to view results at a different CustomDistance

I would prefer landing on an interactive dashboard, one view being the control to adjust the distance

Could my LINKTOFILTEREDVIEW parameter just be the uniqueID of the current row, and then have the second map slice be where I apply the distance filter?

I don’t really care if the action lands the interactive dashboard with a preset instead of customized distance variable. As long as I can control the distance once I’m there, without having to go back to the detailed view

[AleksiAlkio]

If you use the INPUT() with your action when writing the desired distance, you could write a timestamp at the same time.. and then use that with your slice.