Latest Contributions by SuganyaBaskaran1

Hello Todd,  `table` is declared as a local variable in the method and therefore goes out of scope by the time the query is complete and the call back can be fired. That's probably why you don't see anything.  You can declare the table as a property on your class so it's retained. A second option is you can access the table/its properties within the query call back, so it's held on to without being released. You may not have a reason to do this in which case the first option is recommended where the table is defined at a broader scope so it can be retained Option 1:  class VC { let table = AGSServiceFeatureTable(url: URL(string: PGRLAYERURL)!) func getCountsInGeometry(creds: AGSCredential?, polygon: AGSGeometry?, bufferPoint: AGSPoint, query: String) { ... } }‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Option 2:  table.populateFromService(with: queryParams, clearCache: true, outFields: ["*"]) { (results, error) in // Access table or its properties here, so it can be retained. ... }‍‍‍‍‍‍ When you create a layer from a table, and add the layer to a map, the map holds on its layers (and the layer to its backing table), and that's why you don't see the issue in that case.  Hope that helps! Suganya ... View more

That is correct. For new features, you would first create a feature using one of the create methods on AGSGeodatabaseFeatureTable. Once created, you can add the feature to the table using the add method.  For existing features, you typically get a reference to the feature first (query, identify etc), edit and call the update method.  Hope that helps.  ... View more