Latest Contributions by KhaledHassen

FYI: the feature service layer Calculate API allows passing a where clause to filter which records will be affected by calculate. So without having a filter on the layer, you can pass a ad-hoc where clause to the calculate API. If you want to apply calculate to only null field, you can use something like myField IS NULL. Khaled ... View more

Great thanks. We will add the subtypes in future release of online as I described earlier. We will handle it when publishing new data, but we will offer you a way to edit existing service layer to add subtypes. I am assuming the APP continue to work without subtypes when migrating from enterprise to online. FYI: we do have many supports properties in the layer and service metadata to indicate what is supported or not (we do not really have on for subtypes - will add it). There will always be differences between feature services in general and will be good to check these supports properties. ... View more

Pl. describe what is not working for you for the enterprise and we will be sure it will make it in the next release or so in online. We are am not really aware of functionality missing in the API regarding subtypes except supporting it outside the renderer (only Pro uses it). As far as the subtypes and how to scale it, it is also an issue with enterprise also since the subtypes are returned in the layer metadata which as you described might not scale if we have many subtypes. Supporting subtypes is work in progress currently in online and we will offer a salable solution shortly. ... View more

>What I am saying that as someone who makes their livelihood using the APIs it is not unreasonable to expect that both >agol and the current ArcGIS Server would follow the same standard of service definition. Yes this is our goal and we are trying hard to make this happens. But as you might have seen, there are always new WebGIS development in online FS that is not yet in server/enterprise and vise versa. This is mainly related to the the different requirements we have for enterprise versus online and their release plan. As far as the sub types, we do support it online it as described and used. We are working on adding the support of adding subtypes during publishing and expose them even if they are no referenced by any renderer. This is the only missing spec in online FS but our understanding this functionality is used only by Pro. So this is why it was not a high priority in development for online FS. To get around this limitation you can use the feature service layer update admin API to update the layer types or templates. If this is not the issue, pl. let us know and we can help you providing a workaround for any missing specs if possible and add the missing functionality to online in future releases Thanks Khaled   ... View more

Online feature service supports types/template from service definition file (SD). This when you configure renderer based on subtypes. We do not currently preserve subtype when publishing filegdb though (we have this as enhancment-Maybe UC2019).  Pl. try to go to ArcMap or Pro and try to publish your data (from filegdb). You can use your filegdb as the source of the data. You would have to configure renderer based on subtypes in order to get them to online as types metadata. We do have a project to expose and preserve subtypes if you do not specify renderer based on subyptes. This is also an enhacment enterprise has and did not make it in online. This is also planned for UC2019. Thanks Khaled ... View more

Can you send me the error you have when updating the line geometry if you see any? You can also call update the feature using the REST API and let me know what you see. Will be good if you can share this layer and I can take a look. Khaled ... View more

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