Latest Contributions by NarelleChedzey

Hi Mike,  A couple of things.  Firstly you can continue to set the definition query on a layer by using the layer.SetDefinition call. It is saved and it will filter the layer records.    Test this by using the API to set an expression similar to 'OBJECTID > 5' and open the attribute table for that layer and see that not all your records are displayed.  There is a bug in the DefinitionQuery tab on the Layer properties dialog which is not correctly displaying the definition query when you use the 'SetDefinition' call.  This dialog (which changed at V2.3 to allow multiple definition queries)  now uses the DefinitionFilter properties as you suspected.   You can access the CIM definition for the layer to set theses properties.  Here is the code snippet which will assign a new filter and make it the default   - this can replace your call to SetDefinition if you require.  // must run on the MCT - use QueuedTask.Run // get the CIM layer definition var layerDef = fLayer.GetDefinition() as CIMFeatureLayer; // get the table for the layer var featureTable = layerDef.FeatureTable; // get the current set of definition filters var filters = featureTable.DefinitionFilterChoices?.ToList(); // they might be null, so create a new list if (filters == null)    filters = new List<CIMDefinitionFilter>(); // create a new filter var filter = new CIMDefinitionFilter(); filter.Name = "my filter"; filter.DefinitionExpression = newExpression; // add to the list filters.Add(filter); // assign filters back to the CIMDisplayTable featureTable.DefinitionFilterChoices = filters.ToArray(); // also set DefinitionExpression, DefinitionExpressionName // - these define the active definition filter featureTable.DefinitionExpression = filter.DefinitionExpression; featureTable.DefinitionExpressionName = filter.Name; // write back to the CIM layer definition fLayer.SetDefinition(layerDef); Thanks for pointing out the bug with the SetDefinition call and the layer properties dialog.  We will be addressing this.  We will also work on updating the images in the sample to reflect the changes made to the dialog.  And updating the sample to reflect the changes made at V2.3 to use DefinitionFilters.  Regards Narelle ... View more

Hi Serguei,  If you are retrieving a template that is not active, you need to activate that template before the inspector object is available.   Here is some sample code var map = MapView.Active?.Map; if (map == null)   return; var myTemplate = map.FindLayers("testPoints").FirstOrDefault()?.GetTemplate("testPoints"); if (myTemplate == null)   return; // activate the template myTemplate.ActivateDefaultToolAsync(); // retrieve the inspector var insp = myTemplate.Inspector; // modify fields insp["field1"] = value1; // perform the edit operation Thanks Narelle ... View more