nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

hide fields in table - ArcGIS Online

Anonymous User

Is there a way to permanently hide fields in a hosted feature layer table without creating a hosted feature layer view?

I'd rather not have two layers of the same information showing different fields.

This is in New Map Viewer not Map Viewer Classic.

Thanks to all.

Finde mehr Beiträge mit dem Tag

Accepted answers

All comments

konsta_kuorikoski

Coming back to this after Map Viewer has received some well needed updates and is actually usable over Classic. The issues with table control are still present. The thing thats frustrating is that I can do this in SDE. Re-arrange, set default visibility etc. The popups are fine for the most part, and will satiffy most of the users we have. But as there are fields added, they will be bottom of the list and right-most in table. In between them and rest of useful data are, among other things, logging fields I need for administration but not when checking on data daily.

This is another thing which could be added under Visualization tab. Or in Data tab but with Save-button.

MistySkye

In map viewer you can reorder fields for each layer using the "forms" option on the right panel. You can make fields not visible, required, add arcade code to populate etc.

From the map settings itself (also on the left panel toward the bottom), you can make layers not editable within the map as well.

hope that helps.

JamieMaxwell

I have a feature layer from a different org in a map. I'm trying to make one field visible in the table that isn't currently. I can't make a hosted feature layer view since the feature layer isn't owned by my org. Do I have to export the hosted feature layer and republish it as a new feature service in my org just to turn on one field in the table?

MaximeDemers

@Robert_LeClair thanks for the reply. I am not using Survey123, its an application made with javascript API. Anyway, even if I can hide it in Survey123, the field stay queryable from the rest endpoint.

The goal is to protect user's personal data.

Robert LeClair

In Survey123 using an XLSform I think you can do this - Survey123 Tricks of the Trade: hidden, relevant and body::esri:visible

MaximeDemers

Hi,

Im facing a problem similar to this post that seems that could not be resolved right now even with Hosted Views.

I have an editable Hosted FeatureLayer where people can anonymously add features it in. We are asking about the email of people but we dont want the email field to be publicly queryable.

In other word the email field must be editable publicly without signin but must be hidden. If I use a Hosted View and remove the email field from it, it cannot be edited.

Is there a solution for such case?

Robert LeClair

Hi @konsta_kuorikoski - we're getting there then! Hosted Layer Views are pretty interesting certainly. I don't know about the permanently reordering of fields in the Map Viewer but one workflow that could work, a bit clunky, but could work is in ArcGIS Pro, use the Export Features GP tool to export to a new feature class AND permanently reorder the fields in the feature as referenced here. Then share as a web layer to your Portal. Then use the Hosted Layer Views in the Map Viewer. Clunky yes, but it would work.

konsta_kuorikoski

Hi Robert,

thanks for the reply. Hosted Layer Views are new thing to me (and for the rest of the department), and sure looks promissing. However, it seems to only fix half of the issues. It does help with hiding those fields that aren't needed by the general editors for the layer. But arranging order of the fields in Map Viewer still doesn't save. Not even within same instance. I tested this by changing order of two columns, closing Attribute Table and saving the map. Opening Attribute Table again, the order is switched back to default. Changing order for Pop-up configuration doesn't work in Map Viewer either, seems like that is only effective for Classic.

If the order of the fields could be changed to different default directly from layer Data settings page, that probably would be best. Similar to how visualization default is done from layer Visualization options, not from Map view. Though it seems like bug that Map Viewer Attribute table forgets user set order when table is closed and reopened.

Robert LeClair

Hi @konsta_kuorikoski - I wonder if creating a hosted feature layer view would accomplish what you're looking to do?

konsta_kuorikoski

Sorry for bringing this discussion back up. I stumbled here while looking answers to same question.

We are building AGOL based solution where multiple people with slim GIS experience would be using Map Viewer to track projects and customer queries about those projects. The data contains fields that aren't important for those mainly using the data, but are or would be beneficial for me as admin for the layers. For example fields containing edit logs. Besides those, the main users have certain needs for field order in attribute table.

Right now, neither hiding nor changing order will be saved when Map Viewer is used. Making it pretty bad UX. In Classic, both of these work. But using attribute table as extra source of information besides popups isn't as good experience. So we have combination of two bad solutions to simple problem. I really hope you could get this functionality to us.

ZackK

If the table is closed, looks like the field is back in when table is opened again. I was referring to hiding fields on a hosted layer in map viewer that could be saved. With this setting users would not see those fields in map viewer table, until map editor changes it back. So basically, using the same hosted layer, but hiding field A in one web map, and then hiding field B in another. Currently, it seems that our option is to use a multitude of view layers for various web maps. This works, and should remain an option, but allowing hiding fields of the hosted layer would make the process bit quicker. +1 vote from me asking if there is an update on this setting using a hosted layer. Thanks in advance.

Robert LeClair

So in the Tables, I clicked the Options button (i.e. gear) and in the Field Visiblity UI, turned off an attribute field. Now it does not appear in the table. Secondly, I went to the Pop-Ups UI (right side of the Map Viewer) and clicked the "x" to the right of the same attribute field and it does not appear in my pop-up anymore. It seems to be sticking for me when I use the popup anywhere in the Map Viewer. The hidden field does show up for symbolization tho'...

LayerItOn

Hello, is there an update on this? I try to hide fields in layers in the new map viewer table, in the visualization tab of a feature layer, and tried editing the pop-ups, but they do not stick even after saving. Thank you in advance!

ZackK

Thank you very much for such a quick reply. 🙂👍

No need to apologize, I appreciate possible timeline and explanation. Have a great day!

JeremyBartley1

Same team worked on it then as in now. 🙂

The implicit behavior of applying the popup field visibility to the table leads it to only be implemented in apps that understand that behavior. This becomes even more difficult for our external developers to understand what the "correct" behavior should be.

We will eventually give you the ability to control it at the layer level and by default that will apply to the popup and the table. Plus we will give you the ability to set the visibility of fields for just the popup or just the table. This would allow you to have a different visibility for your popup versus the table.

Unfortunately this won't happen for the next release in Nov but is something we would like to get to in the first half of 2023.

Thanks for the feedback and sorry for the confusion!

ZackK

Is the field visibility supported now? I can't seem to find it. If not, is there a possible timeline when this feature might be implemented and supported? I'd hate to setup views, then not need them in a month:)

It may have "disentangled" that relationship, but that action leads to a bit of confusion for admins and users. If we set up a field to not be visible in a pop-up, odds are that the general intent was not to have it visible in the table either. Why enable basic bypass of limited data we want viewers to see, by allowing to view the full table? Could it be possible that whichever developer(s) setup that "entanglement" may have had that in mind in the first place, giving us a straightforward solution without needing layer views? Creating layer views for something that was solvable with a checkbox, just adds to the number of assets that staff has to track and make sense of in AGOL.

JeremyBartley1

In classic Map Viewer the table honored the popup field visibility which led to confusion (why does popup field list visibility control table field visibility and vice versa). We disentangled this relationship in the new Map Viewer. In a future release we will support a table field visibility in webmaps.

You can control field visibility through views like you mention.

Anonymous User

it's odd that there seems to be no way in New Map Viewer to permanently hide fields that remains after the map is closed then reopened.

i'm not sure how to use the API Python solution so find myself simply disappointed with ESRI on this one.

Anonymous User

it seems there's no simple way as there was with Map Viewer Classic

Robert LeClair

In this Esri Community post, there's a response by KhaledHassen that says you can turn off field visibility using the layer updateDefinition API with an example. I'm not a developer but it seems this may work.

In addition, this link and Example twelve may be the way to do it.

Nimm an der Unterhaltung teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.