Latest Contributions by KhaledHassen

Hi Savannah, Updating the item above will not help you and not the right way to do this. If you need to relate two services, the only way is to create a join view. So you will end up with a view of the two services joined into one layer. I can send you more info about this if this is what you can use. But this is the only way we have currently that joined two separate feature services. You will need to create an empty feature service view and then add a view layer. I can send you the json you need to use to create the join feature service view. Thanks Khaled Hassen Online FeatureService Dev. Lead ... View more

Hi Savannah, Yes. We are working on releasing it in March or June release. Pl. check esri dev summit recording this year. I have a session about online feature service best practices. I have demoed the use of webhooks in online feature service. The dev summit recording will be available shortly from esri. Thanks Khaled ... View more

The normal flow usually is to keep the source data private and not shared with the public. Only share the view with everyone where they can see only the subset of the data. If you enable query on the view the desktop uses the query to export the data. Arcmap should check for the extract capabilities before the export but it does seem it does not. >This newly created shapefile now has no extent parameters. Is there a way to avoid and keep a layer private? Do you mean the view? if so since the view is public, you can remove "Extract" from the feature service view capabilities. A client like desktop should have checked the extract capabilities, however, any client can use the query with pagination to export the data. Khaled ... View more

The normal flow usually is to keep the source data private and not shared with the public. Only share the view with everyone where they can see only the subset of the data. If you enable query on the view the desktop uses the query to export the data. Arcmap should check for the extract capabilities before the export but it does seem it does not. >This newly created shapefile now has no extent parameters. Is there a way to avoid and keep a layer private? Do you mean the view? if so since the view is public, you can remove "Extract" from the feature service view capabilities. A client like desktop should have checked the extract capabilities, however, any client can use the query with pagination to export the data. Khaled ... View more

If you share only the view that has the spatial extent filter, desktop will export only the data within that extent. So the desktop will not be able to export the data outside the spatial filter you set on the view. If you enable query on the view, you can only see the data within the extent. Not sure how the desktop can export data ourside the spatial extent of the view since the server enfoce what data to export. Can you pl. add more details about this issue. Khaled Hassen Online Feature Service Lead ... View more

If you share only the view that has the spatial extent filter, desktop will export only the data within that extent. So the desktop will not be able to export the data outside the spatial filter you set on the view. If you enable query on the view, you can only see the data within the extent. Not sure how the desktop can export data ourside the spatial extent of the view since the server enfoce what data to export. Can you pl. add more details about this issue. Khaled Hassen Online Feature Service Lead ... View more

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