Latest Contributions by KhaledHassen

Yes pl. work with Tech support so they can provide me with a repro case and I will take a look and work toward fixing this issue. Until then pl. create view with only the layer you need to avoid having to delete the layers after creating the view. ... View more

You should be able to do this now. Just drop the layer or related layer you do not want in the view. This should not affect the source feature service or layers. ... View more

Here are some numbers for online FS: >maximum number of fields in a hosted feature service You can define up to 30K fields per table. But you might have issues in the platform if you define very large number of fields specially when integrating server/offline/online since this involves different geodatabases that have different limits. But the number is sufficiently large and will support 30K limit. -max/min value of Integer (webmap won't allow you to enter anything beyond +/- 999,999,999,999,999 but this may be a UI limit)  Online/server have the limits of the data type value short (esriFieldTypeShort = 2 bytes) versus integer (esriFieldTypeinteger = 4 bytes) versus long (8 bytes = bigint).  As you know the formula is: max = 2^(n-1) here n=32 for 4 bytes integer. for instance min/max for esriFieldTypeInteger = [-2,147,483,648, 2,147,483,647] >-max/min value of Float (webmap won't allow you to enter anything beyond +/- 999,999,999,999,999)  The range is the float (4 bytes, 7 digits precision = esriFieldTypeFloat): [- 3.40E + 38, 3.40E + 38] >-max/min value of double (esriFieldTypeDouble)  The range is the double (8 byte, 15 digits precision): Very large value: [- 1.79E+308, 1.79E+308] >-max/min value of Date (webmap seems to allow 1/1/0100 to 12/31/9999) Actually this is the limit: 0001-01-01 through 9999-12-31 >-max length of String (I think this is 2GB or approx 1 billion characters) To index a string column in online, the string column needs to be less than 4000 chars. But if you define the column size = -1 or more than 4000, the max is used (2^30-1 number of chars) but you will not be able to add an index on that string column. >maximum number of attachments (assuming sufficient credits)  No limits >maximum attachment size (assuming sufficient credits)  Also no limits but we have a 10M limit in the size of the attachment you are adding as a single part attachment from the API. Adding multi part attachment has no limit. So you can add technically add video/etc as a multipart attachment in online. Pl. Let us know if you have this case and we can show best practice of reading such attachments. Pl. note we do support resizing attachment images in online for large size attachment images from the API (w=100 up to w = 2400 and preserving the aspect ratio of the original attachment). Hope that helps. Khaled ... View more

We are planning online 6.2 release in the next couple of weeks in June. ... View more

We have made the initial install for this in the API. But it might not make it from the UX. So in the next release you will be able to use feature service layer updateDefinition API with {"hasAttachments" : false} to disable attachments on the view. You can later enable it on the view only if it attachments is enabled in the source. ... View more

Most likely, Will update you shortly. It is still in development. ... View more

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

[email protected] ... 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