Map View Secondary Data Table Pin Links to Primary Data Table Detail View

Edit: I went ahead and reported this to support. Tested this behavior with a user that is running a stable version of the application and it is exhibiting the same behavior, suggesting that this is a bug I would imagine as the app was not previously behaving this way.

I am taking this post into consideration only because the issue is very similar but the OP did not state if their primary and secondary data tables linked to tables that shared a datasource.

I have a map view with a primary data table and a secondary. Both tables are completely different datasources. One consisting of permits and the other consisting of meters. For each of these tables I have a deck view which is part of the map view but also contained within separate views.

My meter view is the primary on the map and permits is secondary. When I click on a meter pin it displays the correct deck view at the bottom of the map and when I click on the deck view it navigates correctly to my meter detail view. When I click on a permit pin it displays the correct deck view at the bottom of the map, however when I click on the deck view it navigates to a blank meter detail view (instead of the permit detail view like it used to before).

@Steve would there be a possibility to find out what the status is on this? I know the OP from the other post said this was fixed with an Appsheet release however that does not seem to be the case for me personally. Thank you.

Hi, I can confirm that the issue still seems to be resolved for me. But I noticed as well that it seems not to work if I copy the app to another one of my appsheet accounts. Maybe resolution was rolled out for my initial account only?

Correction: I just double checked and now it is working for my other account as well. So everything is fine for me. But please not that in my case primary and secondary data tables are the same data source.

I appreciate that you tuned in on this conversation. I was thinking that maybe your map had the same datasource for both tables that are connected to your map view. This just confirms it.

Update: Received confirmation from Appsheet support that they were able to reproduce the issue and they forwarded to dev for further investigation.

Just in case someone else comes across this topic with the same issue.

1 Like