Latest Contributions by KhaledHassen

FYI, join view support attachments. This requires the PKEY/FKEY to be based on globalId. We have released this in online 7.3 release (Sept. 2019). Pl. check it out and let us know if you still have any issues. Khaled Hassen Online Feature Service Dev. Lead ... View more

Hi Brian, Yes the plan was to release it on December. Development is done but we still working on testing/scaling the solution. Also finishing up the docs. The plan is to release it on March on the latest. Will update if we can make it before March. Sorry for the delay. Khaled  ... View more

Hi Andrew, I see you are passing the filter above in the url without any url encoding. This will not work. The topFilter in the url will look like: &topFilter=%7B"groupByFields"%3A+"Editor"%2C+"topCount"%3A+1%2C+"orderByFields"%3A+"EditDate"%7D+ Pl. note I used double quote for the group by and order by fields. Thanks Khaled ... View more

How you upload? using the UX or using Portal API. You need to be sure you are define the type of the file when uploading. ... View more

Will be good if you can send the layer url. The most common issue is that you have set a definition expression on the layer and then you have deleted the field referenced by that expression.  Khaled Hassen Online Feature Service Dev Lead ... View more

We do not really have any issues with the publishing-related size of the shapefile. We supported in the past 45G of data and millions of features. Is this only shape file publishing? did you try fileGDB? If you fail to publish again, pl. share the time of publishing and I can check it out. Khaled Hassen Online Feature Service Lead   ... View more

Yes this should be in online FS. Pl. let me know if you have any issues with it. Khaled ... View more

Online feature service supports different capabilities that would prevent querying or even export the data. If you want to prevent the user from export your data in online feature service, just do not add the "Extract" capabilities to the feature service. You can also prevent your user from even querying your data, by remove the "Query" capabilities from the feature service. Admin and service owner can adjust the feature service security from the UX and from the admin API. These security settings are enforced by the feature service logic. This security setting does not apply to the owner or the org admin. If you still see any issue after setting removing the capabilities, pl. let us know.  Khaled Hassen Online Feature Service Lead ... View more

Online feature service supports different capabilities that would prevent querying or even export the data. If you want to prevent the user from export your data in online feature service, just do not add the "Extract" capabilities to the feature service. You can also prevent your user from even querying your data, by remove the "Query" capabilities from the feature service. Admin and service owner can adjust the feature service security from the UX and from the admin API. These security settings are enforced by the feature service logic. This security setting does not apply to the owner or the org admin. If you still see any issue after setting removing the capabilities, pl. let us know.  Khaled Hassen Online Feature Service Lead ... View more

Hi Richard, You will need to turn on schema changes on the view you have. https://services1.arcgis.com/byI4kn9uGfeTFbS1/ArcGIS/rest/services/Scottish_Wildlife_Trust_reserve_boundaries___with_web…  To do this, you will need to go the admin API of the view: https://services1.arcgis.com/byI4kn9uGfeTFbS1/ArcGIS/admin/rest/services/Scottish_Wildlife_Trust_reserve_boundaries___with_website_text/FeatureServer/updateDefinition Then use the following json: {     "sourceSchemaChangesAllowed" : true } Then add the index you need. I think this should resolve your issue. If not pl. let me know. Khaled Hassen Online Feature Service Dev Lead. ... View more

Pl. check using feature service views. You can keep your source feature service private and then expose a view of the source feature service with the desired capabilities (read-only for instance). Views will see any changes in the source feature service as it happens. Khaled Hassen Online Feature Service Dev. Lead ... View more

Not sure if you have researched using views in online feature service. You can configure your source service to be private and not shared with anyone. Only the owner of the data, for instance, can read/write/export/etc. the source data. For the public consumer, you can create a view of the source data. You can hide any column and grant only public access/read capabilities. This is what we recommend to our clients. Feature service views will see any changes in the source feature service as it happens. Thanks Khaled Hassen Online Feature Service Dev. Lead ... View more

Sorry, we could not make it for online 7.2 release.  But will update you shortly if we can make it in 7.3 release scheduled in Sept. Thanks Khaled ... View more

Sorry for the confusion. We will get handled. The definition is mainly owned by the feature service and the runtime originally developed based on server. This is new in online and it looks like we have some differences in the case of the types. Runtime team does not define what the subtype json is and they have been involved in testing but it looks like this issue is not detected. The main reason I have mentioned about the collector is that we have recently fixed an issue that affected collector and was related to subtype default. I wanted to know the severity of the issue and if we need to handle it before Sept. release. If this issue is critical to you, pl. submit a request for us to the tech support (online feature service) and I will see if we can speed up the deployment.  ... View more

I am the online feature service lead but working closely with the collector app team which seems do not have this issue. At any case, I will fix this in the online feature service by Sept. Will touch base with the collector app to see if they have this issue. Khaled ... View more