Latest Contributions by KhaledHassen

FYI: Webhook is a work in progress in online feature service. Most likely it will be available later this year.  Khaled Hassen Online Feature Service Dev Lead ... View more

Data stored in online feature service will be defaulted to 102100 projection if it is not defined with the source and publishing parameter. If you publish SD file with a specific projection and transformation parameters, online feature service will preserve the spatial reference of the map defined within the SD file. We will not default the online feature service to 102100 in this case. Publishing any other data source (shapefile, filegdb, excel, etc.), we will default to mercator (102100 or latest=3857), unless you pass a tergetSR publishing params. Pl. note the feature service and data stored in online FS will always have the same SR. And Yes once you have your service in a specific SR, you cannot change it once publish. Khaled Hassen Online Feature Service Dev Lead ... View more

Not sure why you need to split. If it is not related to performance and just for project related changes, then will be good to consider creating views. One view per project and each view layer will have a definition query for the data related to this project. Not sure if you have issues using views instead of the split. Khaled Hassen Online Feature Service Dev Lead ... View more

Scott, The editing model on the feature service applies to all the layers within a feature service. So if you assign an editing permission on a feature service, this would apply to the feature point layer and the related table. So currently your workflow is not supported. However we do offer views. You can technically allow the client to edit a view of the related table. The changes will be reflected to the source feature service. This is what we usually advise our client who has this requirement. So you will have the original feature service with point+related table as read only. The you will create another view that contains only the related table and you would assign editing capability to the view. All changes to the editable view will shown up in the source feature service. Not sure if you will have issues with this in your workflow. We are not planning to change the feature service editing model in the near future. Khaled Hassen Online Feature Service Dev Lead ... View more

You can always export the service to filegdb. This would preserve GlobalIds, rel, and attachments. Then you can use the filegdb to publish a new service with a new name. Using Append API will allow to transfer the data from the filegdb to the new service without creating new service. It will preserve the GlobalId also but it will not create any relationships or attachments. So importing the filegdb to a new service is the best option. Khaled Hassen Online Feature Service Dev Lead ... View more

From the online side, database views are also created when joining the source and destination related table in the online view. This is currently supported when creating online feature service view and we have some examples of how you can do this in online. This is all done using REST API when you add a new join layer to an empty feature service. BTW, this is not supported in Portal/server based feature service. I would think this is a good solution moving forward if they desire to render data based on joining the source layer and a related table. Khaled Hassen Online Feature Service Lead ... View more

What you are passing in there is not esri feature collection. What I would suggest is to start using uploadId or itemId in the append API. So you can just go the feature service uploads API. Upload your filegdb and then use append passing in the uploadId for your filegdb. So the UX append does not work from filegdb or other data source? This is what the append expects as a feature collection. { "layers": [ { "layerDefinition": { "currentVersion": 10.2, "id": 0, "name": "CITIES", "displayField": "", "description": "", "copyrightText": "", "defaultVisibility": true, "editFieldsInfo": null, "relationships": [ ], "isDataVersioned": false, "supportsRollbackOnFailureParameter": true, "supportsAdvancedQueries": true, "geometryType": "esriGeometryPoint", "drawingInfo": { "renderer": { "type": "simple", "symbol": { "type": "esriSMS", "style": "esriSMSCircle", "color": [ 255, 85, 0, 255 ], "size": 7, "angle": 0, "xoffset": 0, "yoffset": 0, "outline": { "color": [ 168, 0, 0, 255 ], "width": 1 } }, "label": "", "description": "" }, "transparency": 0, "labelingInfo": null }, "allowGeometryUpdates": true, "hasAttachments": false, "htmlPopupType": "esriServerHTMLPopupTypeNone", "hasM": false, "hasZ": false, "globalIdField": "GlobalID", "typeIdField": "", "types": [ ], "templates": [ { "name": "New Feature", "description": "", "drawingTool": "esriFeatureEditToolPoint", "prototype": { "attributes": { "NAME": null, "COUNTRY": null, "Order": null, "CAPITAL": null } } } ], "supportedQueryFormats": "JSON", "hasStaticData": false, "maxRecordCount": -1, "capabilities": "Create,Delete,Query,Update,Editing", "fields": [ { "name": "FID", "type": "esriFieldTypeOID", "alias": "FID" }, { "name" : "GlobalID", "type" : "esriFieldTypeGlobalID", "alias" : "GlobalID" }, { "name": "NAME", "type": "esriFieldTypeString", "alias": "NAME", "length": 40 }, { "name": "COUNTRY", "type": "esriFieldTypeString", "alias": "COUNTRY", "length": 12 }, { "name": "Order", "type": "esriFieldTypeDouble", "alias": "Order" }, { "name": "CAPITAL", "type": "esriFieldTypeString", "alias": "CAPITAL", "length": 1 } ], "objectIdField": "FID", "minScale": 0, "maxScale": 0, "extent": { "xmin": -18397772.7190125, "ymin": -7010792.484942091, "xmax": 19718042.33097229, "ymax": 14476655.301642163, "spatialReference": { "wkid": 102100, "latestWkid": 3857 } }, "type": "Feature Layer" }, "featureSet": { "geometryType": "esriGeometryPoint", "spatialReference": { "wkid": 102100, "latestWkid": 3857 }, "features": [ { "attributes": { "FID": 533, "GlobalID": "{CE7011B8-FB6A-4ADA-B1A1-15410EB30155}", "NAME": "Shijiazhuang", "COUNTRY": "China", "Order": 1190000, "CAPITAL": "N" }, "geometry": { "x": 12752728.320089377, "y": 4590322.487161252, "spatialReference": { "wkid": 102100, "latestWkid": 3857 } } } ] } } ], "showLegend": true } ... View more

Hi Torrin, Would you be able to send me the params you have used. Also the feature service url you are trying to append to. We doc the append API here: Append (Feature Service)—ArcGIS REST API: Services Directory | ArcGIS for Developers  Thanks Khaled Hassen Online Feature Service Lead ... View more

You can always turn off visibility of any fields by using the layer updateDefinition API. You can pass one or more fields in the API below. Ex: http://serverUrl/<myOrg>/ArcGIS/rest/admin/services/<serviceName>/FeatureServer/<layerId>/updateDefinition Then you need to pass the following: {   "fields" : [   {      "name" : "myFieldName",     "visible" : false   } ] }  Thanks Khaled ... View more

Our clients normally use feature service views to organize data that can be viewed by different users. So you would end up with one or more source data and then you create a view for each user. Each view would have a filter that define with this user can see. When the source data gets updated, all views will be updated for you. Not sure if this is something that fits your project requirement but it is worth mentioning. Pl. let me know if you would like any help or info about views. Thanks Khaled Hassen Online Feature Service Development Lead ... View more

This seems to be a geo-datum transformation issue and it looks like the default transformation between these two projections does not work well. Would you be able to set the datum transformation from ArcMap between the source data projection and the map/data frame projection when authoring the sd file. We will honor the datum transformation if exists in sd file and it will be saved with the created feature service.  Khaled Hassen Online Feature Service Lead ... View more

Mike, One question I have for you is how did you create this view. I can consider turning this ON by default if I have some idea about how this is created and configured, from UX, pragmatically using the API, etc. Khaled ... View more

Mike, As I have explained isUpdatableView false means you will not be able to edit unless you use the feature service admin API to turn it ON. Pl. check the solution I have above. Not really sure if we have a UX to turn it ON. Solution is very simple. Go the admin endpoint of the feature service view and execute updateDefinition and pass {"isUpdatableView" : true} This is all what you really need to do. We can do it for you if we have admin access to your service. Khaled Hassen ... View more

One way to do this is by creating a view layer from this service. You can then set the topFilter in the view. Once this is done, then you should be able to view the results like any other filter in the layer. To set the topFilter in the view, you will need to use the layer admin API and pass the followings: https://servicesurl/ArcGIS/rest/admin/services/view-name/FeatureServer/1/updateDefinition  {     "viewLayerDefinition" : {         "topFilter" : {           "orderByFields" : "<yourfileldName> ASC",           "groupByFields" : "your _groupBy_fields",           "topCount" : 1         }     } } ... View more