IDEA
|
Pl. let us know if you see any security vulnerabilities. We will work on changing the design/fix to address these concerns or issues. There are many ways to secure a feature service or a view. Being aware of these security measures and how to use them is important to secure your data. View is one way to secure your feature service and you can create as many as needed. You can add Ownership Access Control, different capabilities, adding custom roles for users or adding views or source feature service to a group and secure your group. You can also control if you want to allow data to be extracted or not. We are working in the next release or so to allow controlling the security per layer rather than per feature service. This would allow finer control over your service layers. We are continue working on enhancing the security and any help in this initiative will be great for everyone. Thanks Khaled Online Feature Service Dev Lead
... View more
06-01-2020
03:26 PM
|
0
|
0
|
2796
|
POST
|
Hi Andy, By default, we support updating view fields when the source layer fields changed. However it it happens you have updated any fields in the view, these fields will not see the changes from the source. We have extended the support to join view also in June release of online (June 2020). Unfortunately we do not have away to reset the view back to its source if you have overridden the view fields (changing field editable, etc. in the view) and you will have to recreated the view if you need to reset them back. Pl. let me know if you have any questions. Thanks Khaled
... View more
05-26-2020
06:59 PM
|
0
|
0
|
1136
|
IDEA
|
Hi Ben, Webhooks will be released on online June release (sorry for the delay). Documentation will be ready as well with the June release. All the dev summit sessions are available. Pl. check the feature service session - ArcGIS Online: Best Practices with Hosted Feature Services - YouTube Thanks Khaled
... View more
04-29-2020
07:37 AM
|
0
|
2
|
1684
|
POST
|
Not sure why you stuck. are you using async=true? try to avoid that for quick update. At any case, I do not see you are passing groupby. you need to pass a group by field. This is how we group by records and pick the record. Do you have any issue passing groupby. Khaled
... View more
04-10-2020
11:34 AM
|
2
|
6
|
3040
|
POST
|
You are using the wrong json. I should be something like: { "viewLayerDefinition" : { "sourceServiceName" : "...", "sourceLayerId" : 0, "sourceLayerFields" : "*", "topFilter" : { ... } } } You do not need to set all these props. Can you pl try it out and let me know. This should work. Khaled
... View more
04-10-2020
10:53 AM
|
0
|
8
|
3040
|
POST
|
Yes esri internally using the topFilter to view most recent record in view as well and in similar projects related to COVID-19. Not aware of any issues. This should work. Let me know if it does not or having issues. Khaled Hassen Online Feature Service Software Dev Lead
... View more
04-10-2020
09:11 AM
|
0
|
10
|
3040
|
POST
|
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
03-18-2020
07:08 AM
|
0
|
3
|
3049
|
IDEA
|
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
03-13-2020
10:24 AM
|
0
|
1
|
1544
|
IDEA
|
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
12-11-2019
01:24 PM
|
0
|
0
|
1302
|
IDEA
|
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
12-11-2019
01:24 PM
|
0
|
0
|
1032
|
IDEA
|
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
12-11-2019
11:44 AM
|
0
|
1
|
1302
|
IDEA
|
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
12-11-2019
11:44 AM
|
0
|
1
|
1032
|
POST
|
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
11-30-2019
07:48 AM
|
0
|
0
|
1636
|
IDEA
|
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
11-21-2019
07:12 AM
|
4
|
2
|
1544
|
POST
|
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
11-20-2019
06:34 PM
|
0
|
2
|
563
|
Title | Kudos | Posted |
---|---|---|
1 | 10-31-2023 07:04 AM | |
1 | 04-13-2023 08:40 AM | |
1 | 03-11-2019 03:05 PM | |
1 | 02-22-2019 09:06 AM | |
1 | 10-04-2018 07:58 AM |
Online Status |
Offline
|
Date Last Visited |
04-17-2024
12:27 AM
|