Latest Contributions by KhaledHassen

StartAt time does control the scheduler when we start sending you changes. The changes are counted from the time you enable change tracking in your feature service and not from the startAt time. Once you receive the first change, all changes will be send based on the first change we sent earlier. ... View more

Please let me know if your services that see a delay in webhooks notification. We have been scaling the webhooks infrastructures to handle the load. But will be good if you can share a url of a service that sees a delay in webhooks notification. We would expect notification to be between 1-5 mins. ... View more

All, pl note online feature service now allows changing the field type if the change will not cause data loss or issue. For instance you can upgrade small int to int and float to double, etc. Thanks Khaled   ... View more

This is related to the data store accuracy we use which is around 11 or 12 mm.  I would try something a little bit higher. ... View more

Unfortunately we do not currently support vertical line in online feature service. The validation of geometry requires difference in x, y. This is a date store limitation. We will be working on supporting vertical line in future releases of online. The workaround is to create at least one point that has difference in x or y. Thanks Khaled Hassen Online Feature Service Dev. Lead   ... View more

Liam, I have watched the video. From what I see, you are applying updateDefinition to the feature service and not the layer. You need to go to the layer and set the topfilter on the layer using the layer updateDefinition. You cannot update topfilter in feature service updateDefinition API. ... View more

Hi Liam, Can you pl. try only the topfilter. { "viewLayerDefinition" : { "topFilter" : { "orderByFields" : "Fix_Time DESC", "groupByFields" : "Email", "topCount" : 1 } } }  Thanks  Khaled  ... View more

Hi Liam, I think you should be able to create a view with the topfilter for this service. Can you pl. provide us with the steps to create the view in our side based on this data. We can try to repro it. I think the step that should work as follows: - Create an empty view - Call add to definition and link the view to the source - Use update definition to change the topfilter. Thanks   Khaled ... View more

That looks right to me. I have recently fixed an issue related to topfilter. The fix will be available next week as part of online feature service update. So please try it again with the update. If it is the same bug I have fixed, then if you retry apply the topfilter. It will finally work. So please try it again another time and see if this is fixed. If not, please wait until next week for the fix.  ... View more

I would try to disable change tracking, sync and enable them back. You do not need to enable change tracking if all what you need to create offline and sync. You will see change tracking in the UX under (Keep track of changes to the data (add, update, delete features). Unfortunately you will have to delete all existing replicas on this service before disable sync. It is possible sync was enabled and there has been some schema changes after. Thanks Khaled     ... View more

You need to use admin service updateDefinition. Ex:  https://.../ArcGIS/rest/admin/services/<myservicename>/FeatureServer/updateDefinition and then pass the json above. Pl. note the sources of the view needs to have sync enabled. Thanks Khaled   ... View more

Pl. provide me with some info and I can double check. What API you are calling, applyEdits, etc,? I see the layer has the relationship set correctly.  ... View more

Yes you need to publish SD file to bypass the default SR which is web Mercator if you are using Pro or even arcgis.com UX. The UX does not expose the targetSR param we support at publishing. So you can use the portal Publish API directly without the UX and you should be able to override the default behavior and specify any target spatial reference as a publishing param. Publishing param in portal can contain: {    "name" : "<yourname>",     "targetSR" : { "wkid" : <>"} } You can check how the UX is publishing from arcgis.com UX (fiddler, etc.). It does call the portal publishing from your data source. Thanks Khaled ... View more

Not really understand the issue. We do support publishing data into any coordinate systems. However once the data is published, you can change the coordinate system since this would requires reprojecting the existing data. Also area and length reported in the layer query is based on the data spatial reference. BTW, these are not geodetic. You can use returnGeodetics in the query API to get more accurate measurements.  Thanks Khaled ... View more