Latest Contributions by KhaledHassen

Currently the attachments can only be disabled from the source and that would propagate to all views. So the short answer is not currently supported. But I will add this as a future enhancement (maybe June online release). ... View more

khassen@esri.com ... View more

Sure pl. recreate the view and share it with me. I can take a look and maybe send you the json you need to use. ... View more

We do not support deleting the relationships directly. We are supposed to delete the relationships when deleting the layer. What is the status of the view service now. Have been able to delete all tables you do not need in the view? Is it possible you have an order issue when deleting. You are supposed to delete the destination table that is not a source of a relationship first. ... View more

No. Deleting the related table should take care of deleting the relationships between that table and the view layer. Once you delete all related tables in the view, you should see no relationships in the view layer. ... View more

No. Nothing needs to be done in the source. You just need to drop the related tables from the view and this would remove the relationships from the view also. Pl. note deleting these layers from the source would delete the related tables permanently and also this would delete all the source data. Khaled ... View more

Yes you can exclude the related tables from the view and this has nothing to do with the join field. The UX clones the source and create a view with all layers. But you can drop the related table by using the deleteFromDefinition API on the feature service view. Admin API can only be used by the admin or the owner of the feature service view. http://serviceUrl/rest/admin/services/myViewName/FeatureServer/deleteFromDefinition  You can pass the following json: {"layers" : [   {      "id" : <relatedTableId1>   },   {      "id" : <relatedTableId2>   } ] } Pl. let us know if you have any issue with the above. Khaled ... View more

What I meant in my previous message is that all what you need to do is to append the token to the url returned from create replica. So if the server returns url=http://services.arcgis.com/mytenent/../myreplica.json, you need to add &token=mytoken to the json url you are downloading. The token can be the same token you used in creating the replica if it is not expired. Otherwise you will need to acquire a new token based on your user identity. Thanks Khaled ... View more

In the last release we have in online, download the json file/sqlite from create replica API will require a token. This is to prevent unauthenticated users from download the create replica output by other users. Pl. when download the output from create or sync replica append a &token={your-token} to the json file url. Pl. let us know if this does not work. Thanks Khaled ... View more

Hi, I have been able to export your data to filegdb. Would that work for you? I can send you the filegdb. In July release, you should be able to publish that filegdb back and create a new service out of it. Also you can go to ArcGIS desktop and view your data directly from the filegdb. Please send me you email and I can send you the filegdb. Thanks Khaled Khassen@esri.com ... View more

Please share it with the public and send me the url. We can find you a group if you have any issue exposing your data to the public. This is temporary. Thanks Khaled ... View more

Our target data is first week of July. I am not sure if this is the same issue we fixed. Not sure if it is OK to share your data with us if you cannot get the data exported. We can check it out and fix any other issue with your data. Thanks Khaled ... View more

Hi, We have recently fixed a similar issue related to incorrect geometry when exporting. The fix will be in our July online release. We have also another way to export your online feature service data. You can use createReplica REST API which support exporting your data to filegdb or JSON. You can find the help for creating replica to FileGDB in esri REST help: http://resources.arcgis.com/en/help/arcgis-rest-api/ Pl. note to use syncModelType = none when exporting data to filegdb since this is the only sync model we support for filegdb. If you still cannot export, pl. let us know and we can try to reproduce this issue in house and debug it to find out the export issue. Thanks Khaled ... View more

>I quess that the Attachment Id's are still FeatureService and not feature wide. So I need to get the attachment id fetched anyway? Actually the attachment Ids are layer based. So you might see the same attachment Id for two layers that have attachments. You can query a feature and get the list of attachments info which would include the attachmentId. You can use that attachment Id later to get the attachment image/bytes. >do you think that Upload can be considered as easily consumed manner? If I understood the concept of Upload correctly, I still want>to use Feature Attachments as a storage for images so those can be easily accessed from WebMaps and other clients. For example,> it is easy to attach the image for WebMap's popup with Image tag. It is a straight forward to use the feature service upload API. It is supposed to simplify the attachment upload experience in some workflows. For instance, when you need to sync a local copy of the data with online content, you can use the upload API to upload many files/images, and then sync the local content by using only the upload Ids you are getting when uploading your attachments. Please let us know if you have any issues or enhancement in consuming the API. Thanks Khaled ... View more