Latest Contributions by KhaledHassen

Sorry if I was not clear. In order to set the view to be updatable you will need to use the feature service admin API.  This is where you can change the default. You can also specify this property when creating a new view service. As I have mentioned above, pl. use the rest/admin API as specified in the example above and then pass the json I have specified above. The admin API of the feature service follows the following url pattern. Pl. replace the url below with your view service url. https://.../myOrg/arcgis/rest/admin/services/myServiceName/FeatureServer  Thanks Khaled Hassen ... View more

Please check queryTopFeaature API on the feature service layer and it is available on online feature service. It is the same as query API but it will return you the most recent or oldest record/feature(s). The key to this API is to pass the topFilter param which can specify the orderBy and groupBy fields. topFilter: { "groupByFields" : "your-groupby_field(s)", "orderByFields" : "sometime_field ASC", "topCount" : 1 // You can return the most recent 1 or more record } Khaled Hassen Online Feature Service Dev. Lead ... View more

Please check the view "IsUpdatableView". Normally the default is false which would prevent you from editing. You can go the feature service update definition admin API and pass: https://.../myOrg/arcgis/rest/admin/services/myServiceName/FeatureServer  {"isUpdatableView" : true} Khaled Hassen Online Feature Service Lead  ... View more

Unfortunately we do not support returning attachments for join layer view. I have added an enhancement in online feature service to support returning attachment for joined layer. This will be supported for inner join only. Initial support plan will be UC this year. Also we might put a restriction like the left table needs to be the one with attachment. Will update once we have this is finalized including testing. Khaled Hassen Online feature service lead ... View more

Philip, I am assuming you are setting the property in the view service edit definition admin API and not the view layer admin editDefintion admin API. Can you pl. be sure you have no client cache (browser cache). Did you try to perform any schema changes in the source and you failed? This is supposed to work. I will check to see if we have any issue with this. Thanks Khaled ... View more

sourceSchemaChangesAllowed property can only be set on views. So for each view you have from the source, you will need to update sourceSchemaChangesAllowed. Once all views has set this property, then the source will update its status of the sourceSchemaChangesAllowed. Pl. note sourceSchemaChangesAllowed property on a source feature service that has views is computed. If any view has this property is false, then the source will be false. Khaled Hassen Online feature service Lead ... View more

Yes sorry. Appending only for features. No schema or attachments. ... View more

Append capability is not required if you use append as the owner or admin of the data. As far as the capability goes, I think you would need to use the feature service updateDefinition API and not the layer updateDefinition API. This is normally the issue I have seen before. We should have error in the API but we are tolerant to the definition that is not valid. I do not think you need to create SD file. Append accepts FileGDB and it is as good without the overhead of creating SD file with fileGDB inside. Thanks Khaled ... View more

This is not currently supported or even possible. A view does not have a storage and it is only a definition that references the original source data. Geometry measurements like area and length are stored with the original source data. You can however request/query data from the view similar to the source in any projection.The returned area/length of the geometry are returned in the native spatial reference units. In order to return the accurate area and length, you will need to query with returnGeodetic=true. This should return  accurate geodetic geometry area and length always in meters.  Thanks Khaled Hassen Online Feature Service Lead ... View more

Here is API doc help: https://esri.github.io/arcgis-python-api/apidoc/html/arcgis.features.toc.html?highlight=append#arcgis.features.FeatureLayer.append Thanks Khaled ... View more

Yes you can. So you can have layer A + attachment + related table to layer A ... View more

>Is there a possibility of creating two related >tables and synchronize one set of attachments and keeping another constant? Not for the same feature. We do support creating views that you can allow your clients to view attachments only or not seeing attachment at all. But for the same feature, we do not have a solution for it currently. Thanks Khaled ... View more

One way you can achieve this is through enabling ownership-based access control (OBAC) on this feature service. Assume you have feature F + attachment (A1). If userA owns this feature F + A1, then no-one will be able to delete or update this attachment (A1) if you enable OBAC.  So you will define ownership-based access control like below. Your users can add attachment only and cannot delete or update existing one including the one they add. "editorTrackingInfo" : { "enableEditorTracking" : true, "enableOwnershipAccessControl" : true, "allowOthersToQuery" : true, "allowOthersToUpdate" : false, "allowOthersToDelete" : false } Not sure if you need your client to modify existing attachments. If you do, then we do not really have a solution for this and you might need to enforce this in the app side but still the client will be able to go and bypass the client side modify or delete this attachment you do not want them to change. Thanks Khaled Hassen Online Feature Service Lead ... View more