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; } } }

Turn off visibility of fields in a web map

nicmah

Hi,

I'm trying to create a web map (and then a web app) which includes multiple views of a data layer. Each of these views needs to include different columns that are visible to different groups of people. Is there a way to restrict the visibility of the columns on each view, without having to create new layers, from within Portal?

Thanks

Find more posts tagged with

Accepted answers

All comments

ChristopherCounsell

The web maps and apps offer general configuration for what fields display in different pop ups and widgets etc.

If you need to control access to the data itself, i.e. ensure security, you should not do this at a map/app level as the underlying data is still accessible through the layer / service. Theoretically a capable user could find the item or service url and access the fields you are trying to hide.

So if you need to secure the data, create additional view layers.

If you just want to hide less relevant data, remove the fields from the pop up or configure the widgets in app as required. Guidance and capabilities on this varies significantly between app designers.

nicmah

Hi Christopher,

Thanks for your reply. Sorry I didn't make myself clear in my initial post, I want to have one view layer for each group of users requiring different columns. It is all based off of the one layer. I've figured out how to create a view layer, and I can see that you can filter rows on each view, but I can't figure out how to restrict which columns are available. Do you know how to remove unnecessary columns from a view layer?

Thanks

nicmah

Hi @ChristopherCounsell
I think I found it. It seems like I could only set a view definition for fields in map viewer classic, not the new map viewer, in our version of portal. I've set the visible fields for each of the views here. Thanks

ChrisH2

Looping into this comment @ChristopherCounsell as it explains our current problem nicely.

We wish to hide a number of fields from a data security point of view, and up until now have been configuring popups. We now realise savvy users could access the data in other ways, so are now looking at using view layers.

Our conundrum is that we'd like to use the username to populate a COMPANY field at the time of data capture in Field Maps, and the only way to do that is to have the COMPANY field to be present in the view so we can calculate it via a smart form. Even with careful hiding of information through a hidden field in the form and removing it from popups, we still have the problem of savvy users being able to access it in other ways. Thankfully at least the username can be accessed as a variable

Is removing the COMPANY field from the view layer, and doing the username X = Company Y calc on the parent feature service back at the server end our only option?

ChristopherCounsell

If the company field is only being populated once, you can use two views. One to edit and populate the value, and one to show the results (with or without the field).

It will only get tricky if you need to use the specific layer for editing and viewing e.g. some kind of dashboard. Or if you need to later re-edit the data via the same view (and update the company value again).

Hard to say without the full workflow but I try to keep my data editing to adds or empty value updates to allow for these scenarios.

ChristopherCounsell

To be clear, once the edit is made and the conpany value is populated I would expect the feature to be filtered out by the view.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

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