In-Line Table View Now Stuck As Map View

[Ryan_Wagner]

Hi,

I have an inline view that was previously working great as a table and now, for some reason, changed to a map view. In this image you can see a different inline table working as it should, but the bottom REF should also be a table…Anyone else experience this?

I didn’t change anything in the settings, so I am perplexed…

[Marc_Dillon · Accepted solution]

There is no app-creator option for which view shows as the inline view. There is a feature request for exactly that though.

Specify which inline view to use in a detailed view Feature Requests

It is too difficult to guess/change which inline view will be used while using a related field in a defailed view. Should have a way to just point on the desired inline view rather that trying to guess which one it will choose (or the need to create a specific slice and create a ref to it, just to force it to use the inline view of that slice)

Also, the first reply, by Fabian, to the above thread has a lot of linked info about what you’re seeing.

Basically, the system chooses which view to use as the inline view. It chooses from all ref-prominence views, and greater priority is given to a map view over a table view.

So a quick fix is to just move your map view to menu prominence.

A better solution is to create a slice for new views, so that they don’t override the inline view.

Read the linked info for more details.

[WillowMobileSys]

What @Marc said above.

However, you are probably wondering why you are seeing a Map but the View you THINK is showing is a Table. More than likely you are not seeing the view you think you are.

To determine what view you ARE seeing, do this:

Below the Map, tap the View button (see image) to expand the map to fullscreen

Note the view name (see image). If it is a name other than “default”, you can tap on the View name to go to that view. If it is a system generated view, you will need to have the “show system views” option on (which it looks like you do above)

[Ryan_Wagner]

Thanks @Marc_Dillon and @WillowMobileSystems.

That is all good to know! I was able to fix it by creating a slice. Back on track!

Thanks again.