topic Re: FeatureLayer ObjectIDs are ignored in ArcGIS API for Silverlight Questions

FeatureLayer ObjectIDs are ignored

egismazeika — Mon, 12 Jul 2010 07:40:22 GMT

The documentation states: "If object ids are specified, other query parameters like Where are ignored."

Here's my code:
FeatureLayer edittingLayer;
<...>
edittingLayer.ObjectIDs = new int[] { 1 };
edittingLayer.Where = "1=1";
edittingLayer.Update();

All features are returned instead of single one.

Re: FeatureLayer ObjectIDs are ignored

DominiqueBroux — Mon, 12 Jul 2010 12:46:16 GMT

ObjectIDs are working from version 10 of ArcGIS server.

Aren't you using a 9.3 map service?

Re: FeatureLayer ObjectIDs are ignored

egismazeika — Mon, 12 Jul 2010 13:36:21 GMT

That was tested on ArcGIS Server 10 beta and final

Re: FeatureLayer ObjectIDs are ignored

DominiqueBroux — Sat, 11 Dec 2021 20:02:22 GMT

I just tested with the edit tools sample : http://help.arcgis.com/en/webapi/silverlight/samples/start.htm#EditToolsExplicitSave

Adding the code below on a test button gives me a correct result (only one object is visible).

 
FeatureLayer featureLayer = MyMap.Layers["ThreatAreas"] as FeatureLayer;
featureLayer.ObjectIDs = new int[] { 8649 };
featureLayer.Where = "1=1";
featureLayer.Update();

What could be the difference with your case?

Re: FeatureLayer ObjectIDs are ignored

egismazeika — Tue, 13 Jul 2010 07:32:50 GMT

Thank you, Dominique. The sample works fine, but not my services.
I've tried on:
1. SQL Server 2008 (ArcSDE 9.3.1)
2. SQL Server 2008 Express DB created with ArcGIS 10.

Could the DBMS be the reason?

Re: FeatureLayer ObjectIDs are ignored

JoelMcBeth — Mon, 28 Mar 2011 18:34:11 GMT

I'm using ArcGIS 10 with Microsoft SQL Server 2008. I have never been able to get a FeatureLayer to use the values in ObjectIDs, it ignores them completely and only uses the Where field for queries.

I just wanted to confirm that this wasn't an isolated incident and I would be interested in getting this working.

Re: FeatureLayer ObjectIDs are ignored

JenniferNery — Mon, 28 Mar 2011 20:56:13 GMT

Thank you for reporting this. We are aware of this issue and are working to get this bug fixed in future releases of the API.