Latest Contributions by KhaledHassen

Pl. note the only value we support for lastEditDate is null. So you will need to be sure to have something like (i.e. "lastEditDate" : null).  Also you can specify "sourceSchemaChangesAllowed" : false/true only for views. If you are specifying "sourceSchemaChangesAllowed" : true for non view feature service, you will get an error. ... View more

In addition of changing the maxRecordCount on the feature service and layer using the admin API.  feature service supports requesting more records without changing the maxRecordCount in the layer. You can request more record by specify an additional parameter called maxRecordCountFactor. For instance you can specify .../query...&maxRecordCountFactor=3.0 If the maxRecordCount for a layer = 1000, then the server would return 3 * 1000 = 3000 record. The maxRecordCount factor is a floating number so you can request 2.5, etc. You can also request smaller value than 1 like .5. Khaled ... View more

You can update the feature service xml layer metadata using the feature service API directly if needed. You can use: ..../FeatureServer/0/metadata/update url to update but you will need to be the owner. You will get a chance to directly pass the xml file as an uploadId or as an itemId. Pl. note using the API does not update the featureService Item xml metadata. It only update the layer xml metadata. You can do this for all the layers within your feature service. To view the xml metadata, you can use .../FeatureService/0/metadata resource. ... View more

We do honor the relationship Id only when publishing Service definition file (SD) only. For fileGDB publishing the relationship Id is incrementally assigned. Is there any reason why relationship Id is important? You might need to dynamically discover the relationship Id from the layer metadata. I will add this as enhancement and see if we can preserve the relationship Id across all feature service implementations. Will post back an update. ... View more

FYI: Please note the data tab UX in the AGOL uses indirectly the feature service admin API to apply the changes. So the rules and the restriction of changing the field size/default value still applies. ... View more

Yes you can do it on online and we should honor it in online feature service fields. However, we have a bug currently in ArcGIS Online  where we only honor a default for the field of type esriFieldTypeString. This bug is scheduled to be fixed in September 2019 update,(scheduled ~ next week). The bug will still be there is you use the desktop. So I hope you can wait until next week and verify this is working for you.  ... View more

Currently you can only change the field visibility, domain and field alias. All other field properties cannot be changed once you publish the layer. We will add support to set field editable property. But we will not be able to support making a field NOT Nullable or Nullable since this operation relies on the data and affect the data store schema. You can work around this by creating a new field with the property you want, then use layer Calculate API to copy the data. ... View more

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