topic Re: Definition Expression Problem in ArcGIS API for Flex Questions

Definition Expression Problem

EvelynHernandez — Mon, 27 Oct 2014 13:34:34 GMT

Hello everybody.

Some months ago i developed a arcgis for flex app that shows features from a city , defining what city i want to show features with definition expression = "where city='alabama' " (for ex)

Some days ago, i cannot see any feature and i was trying to resolve the prob by myself, and i realized that if i put off the definition expression parameter where i define the map layers , the features are shown but not doing the filter that i want.

Is there any problem with the definition expression parameter? or is another thing that is making a prob?

Beforehand , thanks for ur answer.

Re: Definition Expression Problem

RobertScheitlin__GISP — Mon, 27 Oct 2014 13:51:36 GMT

Evelyn,

Can you provide your code where you define the definition expression?

Re: Definition Expression Problem

EvelynHernandez — Mon, 27 Oct 2014 13:55:22 GMT

<esri:FeatureLayer id="edicionLuminaria"

url="http://gisred.chilquinta.cl:5555/arcgis/rest/services/AP_Municipal/AP_MUNICIPAL/FeatureServer/0"

outFields="*" visible="true" definitionExpression="WHERE Comuna='LA CRUZ'"/>

Re: Definition Expression Problem

RobertScheitlin__GISP — Mon, 27 Oct 2014 14:03:26 GMT

Evelyn,

You should not have "WHERE" in your definitionExpression. It should just look like

<esri:FeatureLayer id="edicionLuminaria"

url="http://gisred.chilquinta.cl:5555/arcgis/rest/services/AP_Municipal/AP_MUNICIPAL/FeatureServer/0"

outFields="*" visible="true" definitionExpression="Comuna='LA CRUZ'"/>

Re: Definition Expression Problem

EvelynHernandez — Mon, 27 Oct 2014 18:09:10 GMT

Thank you for ur answer, that was correct. But my question is : why before the definition expression let me do that and it showed the correct result and now i have to change it? is it for any update?

Thanks again

Re: Definition Expression Problem

RobertScheitlin__GISP — Mon, 27 Oct 2014 18:17:50 GMT

Evelyn,

I am not aware of any change. I would not have thought that it ever would have worked with the keyword Where in the string.