Alright… This is about showing the current location on the map.
I’ve been trying to solve this for a few days now in a replicated prototype of my live version.
I have a data table that feeds into a slice.
This slice is the data set for the map view.
There is currently one location column, “location,” that shows all of the pins on the map that match the condition of the slice.
So, normally, about 20 different pins show on the map.
Additionally, a “View Map (Location)” button that shows up on the map, on the bottom right.
When this button is clicked, a bouncing red pin shows that, when moved, feeds into a form, that will eventually populate more pins.
When this button is clicked inline, it shows the current pin’s zoomed location on the map.
This “View Map (Location)” button on the map only shows if the data set is editable and if the main source of the map view is “Location.”
This button is necessary.
Now, the staff has suggested creating a virtual column with the “Here()” formula and use this instead of the “Location” column for the map view.
There are several issues.
If the “Location” column is replaced with “Here()” virtual column, the “View Map (Location)” system-generated action disappears. This action cannot be replicated. Even if I create the exact copy, it does not appear on the map the same way as it did before.
If the “Here()” virtual column is toggled to show, the current pins are repopulated as plain green pins in a close cluster. The pins are not in their designated locations and it looks very wrong.
If the “Here()” virtual column is toggled to not-show, the weird green pins don’t show, but none of the other pins from “Location” show either.
If “Here()” is the main column and “Location” is the secondary column, the “View Map (Location)” action is still not shown, the map is zoomed out just like it was when it was only “Location” as the main column, and the purpose of “Here()” virtual column is pointless.
Same if “Location” is the main column and “Here()” virtual column is secondary, just the “View Map (Location)” action is viewable, but the start view of the map is STILL not the user’s current location.
If there is no “Here()” virtual column, the initial value of “Here()” for the “Location” column doesn’t affect anything. The map still begins showing all the pins on the map instead of the user’s current location.
If the app formula for the “Location” column is edited in ANY way, the “View Map (Location)” action disappears.
I’ve tried many, many things.
Here is my suggested solution…
Please stop giving advice to add a virtual column with the “Here()” formula, it only works if there are no other pins on the map.
Currently, the “Add” and “View Map (Location)” actions, system-generated, seem to be the only ones that are allowed to show on the bottom right of the map view. We should have the option to add our own actions to this place as well.
The action I suggest is some sort of LINKTOVIEW or CONCATENATE button that people can click (inline, prominent, overlay, and map bottom right) that will take a person to their current location.
When completing a form, in the location input, there’s a bouncing red pin and in the upper-right of the small map box, there’s a small map pin… This map pin, when clicked, takes a person directly to their current location… Why can’t this type of button be recreated anywhere else in the app?
The DEFAULT view of a map view should NOT be the view of all the pins. This means that if pins exist in Africa and Japan, the CURRENT default view shows both Japan and Africa at once. This is very annoying for people who only care about dropping a pin in their current location (20~50km) map range.
It’s either a new required & necessary feature or somehow use the current formulas to link directly to a person’s current view. I know a feature might take a few days or so to roll out, but in the meantime, would really appreciate the correct formula to link
Actions should be allowed to be shown in the navigation bar or menu as well.
So we can have the option of replacing the map view in the navigation bar and replacing it with an action that leads to a map view starting at the user’s current location.
This is such a complicated issue, but I really hope to receive a solution soon.