Latest Contributions by KhaledHassen

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

Pl. check the feature service json from the admin API: rest/admin/services/<serviceName>/FeatureServer If the feature service has any geo-datum transformation specified at publishing time, it will be returned from the service admin json endpoint. You can also change the geo-datum transformation information using the FS admin API.  Nothing will be returned if we use the default transformation when projecting (when none is specified when publishing). The best way to get the datum transformation in online is to publish from SD file that has the datum transformation which will be used when projecting between the SRs specified in this transformation.  Thanks Khaled ... View more

Looks good to me. Khaled ... View more

I see the relationship now. I saw the typo in the error log we have.  I do see the field of type ObjectId but not seeing however the objectIdField property.  "objectIdField" : "FID" Pl. try to recreate the table and be sure to set this property to FID. Thanks Khaled ... View more

I see no relationship on your table. I see also you are adding relationship like and it has a typo: { "relationships" : [    {       "id" : 1, "name" :      "Maintenance",      "relatedTableId" : 1,      "cardinality" : "esriRelCardinalityOneToMany",      "role" : "esriRelRoleOrigin",     "keyField" : "GlobalID",     "composite" : false },    //// you have an extra "," here. Pl. remove it. ] } Thanks Khaled ... View more

Still do not see the objectId in the table. Pl. be sure to add it to the table field list when adding the table. Khaled ... View more

I see your table does not have an ObjectId. You will have a problem in your table without objectId. All UX needs the objectId. Pl. drop the table and be sure to add ObjectId field name with your table. Thanks Khaled ... View more

Can you share the service url? I can take a look. ... View more

Yes on the service (not the layer) deleteFromDefinition. You will need to pass something like: {    "layers" : [   {       "id" : <tableId>   }  ] } BTW: Editor tracking is added at the service level. When you create a feature service, you will need to specify: {     ...     "editorTracking" : {       "enableEditorTracking"  : true      .. } So editor tracking it is a system property on the service and you do not really  need to add anything on the layer for edit fields as long as you enable this on the service. Khaled ... View more

Did you try deleting the table directly? deleting the table will also dropping any relationship it has with other layers. Thanks Khaled ... View more

If you really need the count, then you might need to consider calling the feature service layer queryRelated directly and pass returnCountOnly=true. Any other option would be expensive if done in the client side. This is how the UX is getting the count. For example: https://...services/<myService>/FeatureServer/<myLayer>/queryRelatedRecords?relationshipId=0&definitionExpression=1%3D1&…  ... View more