|
POST
|
Hi Mary, very astute! The new tracking capability essentially allows for applications to 'query' for changed features (including added or removed). It's not a historical log of edit transactions with the feature layer, however. No apps currently use the capability (that I am aware at least) but are expected to soon (AGOL itself likely will as well in one of the next releases). As apps leverage this feature, expect to hear more. Despite no current usage, we wanted to make the capability available as some apps may be using it before the next Online release. Hope this helps clarify- Chris
... View more
03-07-2017
09:44 AM
|
3
|
4
|
7002
|
|
POST
|
Hi Melanie - this is a bug; the public layer should not be unshared. We'll fix for the next release (currently planned for end of Feb). As Rebecca alluded, this should only be happening if the user sharing the web map has permission to update sharing on the public layer (i.e., they are owner of the layer or have admin privileges). Having the public layer owned by an administrator can help prevent inadvertent sharing changes (though if the person making the map is also an administrator, they will have permissions to update sharing regardless). Thanks, Chris
... View more
01-24-2017
08:29 AM
|
1
|
1
|
1066
|
|
POST
|
Clarification on this point: To invite a user to join a group, their profile must be visible to others. The users themselves will need to make this change in their user profile (Manage profile—ArcGIS Online Help | ArcGIS). Users can be invited without their profile being public - the username must be entered manually (as search will not discover the user if their profile is not public but you can still send an invite to a user without a public profile). Invite group members—ArcGIS Online Help | ArcGIS
... View more
01-13-2017
11:12 AM
|
1
|
0
|
1725
|
|
POST
|
Hi Deanna, can you share a screenshot of what you're seeing? I tried the workflow and it seemed to be working as expected. Thanks, Chris
... View more
12-20-2016
12:57 PM
|
0
|
2
|
651
|
|
POST
|
Hi Tom, This looks like a bug. It's specific to using the CURRENT_DATE (or _TIME, _TIMESTAMP) function. To use the current date, you'll need to use a date literal, like DATE'11/04/2016' or DATE'11/04/2016 5:00PM'. Edit: you could also create a dummy date field and calculate the field to use CURRENT_DATE and then perform the calculation on your number field using the date field storing CURRENT_DATE (the dummy field could be removed after). The bug has been logged internally and expected to be fixed in the next ArcGIS Online release (currently planned for December). Feel free to contact Tech Support if you'd like a public facing bug logged. Thanks, Chris ArcGIS Online team
... View more
11-04-2016
09:12 AM
|
1
|
0
|
1129
|
|
POST
|
Hi Mary, This appears to be a bug - the workflow you described should work as you expect. As a workaround, you can create a new feature layer from the layer that has the attributes removed. This is in the same create workflow where you initially selected the Permit Inspection template. Instead of selecting a template from the gallery, you should see another tab (in the header) for creating a new feature layer from an existing layer. Select the layer with the modified attributes. The new layer should then work as expected (the original modified layer that is not editable can be deleted - there is no link between the two). The bug has been logged internally (and you can certainly log an external facing bug with support if you like). Should be fixed in the next ArcGIS Online release. Here is the tab I'm referring to: thanks, Chris
... View more
10-21-2016
02:33 PM
|
0
|
0
|
564
|
|
POST
|
Hi Matt, What type of authentication is the WFS using? If it's token based, you should be able to specify a custom parameter which will then include a token in each request. For ex: parameter: token value: ABCDEFG Note, the same token will be used for all requests. If you save the custom parameters in the web map, anyone viewing the web map will use the same token. thanks, Chris
... View more
10-12-2016
11:16 AM
|
0
|
0
|
491
|
|
POST
|
John, you can perform a search using the id from the rest url you provided (hRUr1F8lE8Jq2uJo). This is the id for the organization hosting the services. When querying for content using the org id, search will return all (public) content owned by the organization. From the search results, you can then see specific owners. Here is the query: http://www.arcgis.com/home/search.html?q=orgid%3AhRUr1F8lE8Jq2uJo thanks, Chris
... View more
10-11-2016
08:44 AM
|
2
|
0
|
1537
|
|
POST
|
Thanks for confirming. Requests are a bit different with a layer that is shared publicly vs one that is not. When shared publicly, the requests trigger this issue in Chrome (essentially the browser does not correctly handle certain types of request responses). The Chrome team has acknowledged this as a regression and is planning to patch the current version (this issue is already fixed in future versions of Chrome, yet to be released). Should be available as a browser update fairly soon.
... View more
09-06-2016
12:26 PM
|
0
|
0
|
739
|
|
POST
|
Hi pierssen - are you using Google Chrome for your browser when you see this? Can you try a different browser (Internet Explorer, Firefox) and see if you are able to reproduce the behavior? It sounds like a bug Chrome introduced with version 52. Thanks, Chris
... View more
09-06-2016
09:18 AM
|
0
|
2
|
2586
|
|
POST
|
Adrian Welsh thanks for sending the sd file. Confirmed it's an issue with the field length. Unfortunately the only workaround really is to publish with shorter field names (32 characters or less) . This will be fixed on the Online side in the next release (currently planned for September). There also seems to be an issue with this in Pro with shortening the field names when publishing (essentially both Pro and Online should automatically truncate the longer field names but didn't in your specific case). This info was sent over to the support analyst you talked to - they're writing these issues up, etc so you'll likely be hearing from them soon. Thanks, Chris
... View more
08-03-2016
12:58 PM
|
1
|
1
|
9059
|
|
POST
|
Adrian, the issue is that some of the field names in the layer are too long. Perpetual_Easement_65_value_estimate for example. Usually field names like this are transparently truncated (with the field alias maintained). Pro 1.3 should be doing this but doesn't seem to be in your case. Possible to share the SD file generated in my content when published from Pro? Can send to me @ cwhitmore@esri.com or share privately via group in AGOL (username cwwhitmore). Thanks, Chris
... View more
08-03-2016
08:30 AM
|
1
|
4
|
6167
|
|
POST
|
Hi Nick, the behavior is a bug with some instances of Chrome. We're looking into it but it's been difficult to troubleshoot - it's only happened a handful of times. Haven't figured out yet what specifically is causing the issue on some machines. The behavior can vary even between machines with comparable specs / graphics cards, etc. We'll figure it out but in the interim, unfortunately, the workaround is to use a different browser when sharing (or use item details page, if that is appropriate for the worklow). One thing you could also try is to uninstall / reinstall Chrome (I believe settings, bookmarks, etc will persist). Haven't had the opportunity to try this when we've had a repro case, but it may work.. Thanks, Chris
... View more
07-12-2016
10:33 AM
|
2
|
1
|
4534
|
|
POST
|
Hi, For other services, the "In the last" date filter is working. Sounds like either a service / server specific issue. or maybe database specific. Your best bet is to contact Tech Support - they'll be able to troubleshoot. Thanks, Chris
... View more
06-16-2016
02:28 PM
|
0
|
1
|
1721
|
| Title | Kudos | Posted |
|---|---|---|
| 2 | 11-01-2024 03:09 PM | |
| 2 | 11-06-2024 06:58 AM | |
| 2 | 07-11-2024 09:18 AM | |
| 1 | 02-06-2024 08:21 AM | |
| 1 | 02-01-2024 11:42 AM |
| Online Status |
Offline
|
| Date Last Visited |
04-03-2025
09:40 AM
|