Latest Contributions by KhaledHassen

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

We have developed Append to deal with similar workflow like what you describe. We scale very well with the append API. The only other way to update the data which would definitely be more efficient to use sync and offline between online and the external system that updates the data. But this is not normally available specially if you are dealing with external data providers that use different system.   Thanks Khaled Hassen ... View more

>I have an unique identifier which is a string and which is not available when I use the append function from AGOL. >Using AGOL I worry about two things:  The key in the destination layer that you are using for upsert needs to have a unique index. This is why it does not show from the UX when appending from AGOL. The UX provides a way to add a unique index based on your unique field. >If different users are using different copies from the feature class to add features I guess it could happen that an Object >ID exists that is not the same feature as an Object ID among the new features. Thus it would be better to use our >unique identifier.  Yes you cannot use the ObjectId for this. You have to either use a globalId or your own key that are the same in all copies. Copying data preserve within ArcGIS normally preserve GlobalIds, so duplicating data still reference the same feature. >My next problem is that I have to find a solution without the python API - could I put the same in a python script running >from ArcMap 10.6?   You do not need to use Python API to do this. You can always use the feature service REST API to do this in any language. You can use fiddler to see how the home app uses the REST API to append data into online feature service. Thanks Khaled ... View more

You do not really need to do anything for the changes to be applied to the feature service after using append. If append succeeds, then new features will be appended and existing features will be updated (if you are using upsert). To update existing feature, you will need to use append matching key between the gdb feature class and the feature service layer. The online feature service layer field that is used as an append key needs to have a unique index in the online feature service layer. The online home app contains update data option where you can update the online layer from different sources. Pl. check it out there and see if the data is updated with the options you have chosen. Let us know if this does not work for you. Thanks Khaled Hassen ... View more

Yes we do support append API in online feature service. Also it is available in python API. Feature Service Append API Thanks Khaled Hassen ... View more