Hidden fields are visible
Hi,
When requesting information all the fields are visible.
Can anyone help me?
Thanks in advance,
In the site.xml:
<Layer Identifiable="true" IncludeInLayerList="true" IncludeInLegend="true" Name="WOZ waarde 2010" Searchable="false" ShowMapTips="false" UnconfiguredFieldsSearchable="false" UnconfiguredFieldsVisible="false" Visible="true">
<Fields>
<Field FocusField="false" Name="VHE_totaal_31122010.KOPPEL" Searchable="true" Visible="true" />
<Field FocusField="false" Name="VHE_totaal_31122010.VHE" Searchable="true" Visible="true" />
<Field DisplayName="Straat VHE" FocusField="false" Name="VHE_totaal_31122010.VHE_STRAAT" Searchable="true" Visible="true" />
</Fields>
</Layer>
This is the rest-end point of a layer:
Layer: WOZ waarde 2010 (ID: 13)
Default Visibility: False
Configured Visibility: True
Minimum Scale: 20000
Maximum Scale: 0
Extent: 143024.911, 373023.547, 168617.405, 392103.241
Display Name: WOZ waarde 2010
Feature Type: Polygon
Type: FeatureLayer
Display Field: VHE_totaal_31122010.FID_1
Primary Key Field: VHE_totaal_31122010.FID
Show Map Tips: False
Searchable: False
Identifiable: True
Feature Label: {VHE_totaal_31122010.FID_1}
Icon: N/A
Include in Layer List: True
Include in Legend: True
Feature Description:
Parent Layer: Financieel
Fields:
•VHE_totaal_31122010.FID [FID] (Type: Int32, Visible: False, FocusField: False, Searchable: False)
•VHE_totaal_31122010.Shape [Shape] (Type: String, Visible: False, FocusField: False, Searchable: False)
•VHE_totaal_31122010.FID_1 [FID_1] (Type: Int32, Visible: False, FocusField: False, Searchable: False)
•VHE_totaal_31122010.Count_ [Count_] (Type: Int32, Visible: False, FocusField: False, Searchable: False)
•VHE_totaal_31122010.OID_ [OID_] (Type: Int32, Visible: False, FocusField: False, Searchable: False)
•VHE_totaal_31122010.KOPPEL [KOPPEL] (Type: String, Visible: True, FocusField: False, Searchable: True)
•VHE_totaal_31122010.VHE [VHE] (Type: Double, Visible: True, FocusField: False, Searchable: True)
•VHE_totaal_31122010.VHE_STRAAT [Straat VHE] (Type: String, Visible: True, FocusField: False, Searchable: True)
•VHE_totaal_31122010.VHE_HUISNU [VHE_HUISNU] (Type: Int32, Visible: False, FocusField: False, Searchable: False)
•VHE_totaal_31122010.VHE_HUIS_A [VHE_HUIS_A] (Type: String, Visible: False, FocusField: False, Searchable: False)
•VHE_totaal_31122010.VHE_HUIS_B [VHE_HUIS_B] (Type: String, Visible: False, FocusField: False, Searchable: False)
•VHE_totaal_31122010.VHE_POSTCO [VHE_POSTCO] (Type: Int32, Visible: False, FocusField: False, Searchable: False)
•VHE_totaal_31122010.VHE_POST_A [VHE_POST_A] (Type: String, Visible: False, FocusField: False, Searchable: False)
•VHE_totaal_31122010.VHE_WOONPL [VHE_WOONPL] (Type: String, Visible: False, FocusField: False, Searchable: False)
•VHE_totaal_31122010.CODE_GEBRU [CODE_GEBRU] (Type: String, Visible: False, FocusField: False, Searchable: False)
•VHE_totaal_31122010.DISTRICT [DISTRICT] (Type: String, Visible: False, FocusField: False, Searchable: False)
•woz 2010 egz 20120104.OID [OID] (Type: Int32, Visible: False, FocusField: False, Searchable: False)
•woz 2010 egz 20120104.VHE [VHE] (Type: Double, Visible: False, FocusField: False, Searchable: False)
•woz 2010 egz 20120104.WOZ_2010 [WOZ_2010] (Type: Int32, Visible: False, FocusField: False, Searchable: False)
Feature Hyperlinks:
N/A
Supported Interfaces: REST
-
Hi Julian,
I'm assuming looking at info provided your using feature service. If so, you control the fields your working with via the 'output' fields under the functional tab for the feature service in question. Hopefully this is what your referencing to?
Brad
0 -
Hi Brad,
No I'm using a Dynamic Map Service. And I control the fields using the Field Tab. Hopefully you have an answer.
Julian.
0 -
My reply is based off of the Essentials 3.8 Administrator Guide.
Page 72: Visible: specifies whether or not a viewer should include the field when it displays a detailed listing of the data associated with a given feature
But above that, by the NOTE, it says,
All of the fields in your layers will be exposed through the REST API whether or not you add them to the site configuration through Manager
So, "visible" only means "visible" within a table view of the feature or something. The field is still visible via the REST API, ArcGIS Server API, and so forth. If you don't want the field public, and don't need to access the field yourself, I would try leaving it out of the feature service definition in ArcGIS Server, if that's at all possible. I hide fields in my services that neither I, nor the public, need.
0 -
Hi Roger,
So, "visible" only means "visible" within a table view of the feature or something.That is the problem. In the silverlight Viewer, within a table view the "invisible fields(visible = false) " are visible.
I think the problem is caused because this layer is joined/linked with another table. Is that possible?
And is there a solution for this problem?
Thanks in advance,
Julian
0 -
Hi (Roger),
This works:If you don't want the field public, and don't need to access the field yourself, I would try leaving it out of the feature service definition in ArcGIS Server, if that's at all possible.
Julian
0 -
One way I recommend to Geocortex users to hide fields is to create spatial views against ArcSDE. This assumes you are using ArcSDE of course, but the command line parameter is "sdetable -o create_view". The command has parameter documentation when you run it without any additional parameters. Note you must include the Shape field for it to be considered spatial. To hide fields, simply include only those fields you desire to be published against Geocortex. This then creates a new feature class, which can be consumed in ArcMap. It isn't really new data though, only a pointer to the original data source (Feature Class). The main advantage of this technique is you have full control over the data, its presentation and field names. Just be sure to update the spatial view if the source data changes in any structural way (like field names, data types or other schema changes).
0
Please sign in to leave a comment.
Comments
6 comments