|
POST
|
@SamiHammer Again sorry for the confusion that this has caused. It was not our intention to prevent existing layers that were working to stop working. For the statement "SQLite keywords as fields have never been supported when taking a map offline, the maps will fail when trying to take them offline in mobile or fail packaging in Online. This was not a new restriction, but we made changes in this release to error at authoring time so that we can more easily tell there is an issue with a layer and offline usage.", there is a list of words that have always caused offline to fail. The issue last week was caused by us using a keywords list that was larger than it needed to be. We are retesting all of the keywords to refine the list, which will be around 60 words, that cause a map to fail to go offline if it is used as a field name in a feature layer.
... View more
07-01-2024
12:25 PM
|
1
|
1
|
2552
|
|
POST
|
Hello, can you please share more details of what you are seeing? What is the error message? Can you share the schema of the effected layer(s)? Are you able to take the map offline in Field Maps Mobile? If not what error message(s) are you seeing there (and if possible please share a troubleshooting log from mobile)? Can you please share what changed and any updates to this issue? On Friday evening, based on comments in this post and a couple other posts, we reduced the set of keywords used when showing this new message as we test the complete of SQLite keywords (https://sqlite.org/lang_keywords.html). Currently we are only showing this message for the following 10 keywords which will cause an error when taking a map offline: select commit set then foreign group index unique intersect join As we test the SQLite keywords we plan to expand this list.
... View more
07-01-2024
08:28 AM
|
1
|
3
|
2593
|
|
POST
|
Hello @RichardKauffman Sorry that you are having problem. Would you be able to share the schema of the layers you are having problems with? Object ID is not an SQLite keyword. A list of SQLite keywords is available here - https://sqlite.org/lang_keywords.html.
... View more
06-28-2024
10:31 AM
|
0
|
0
|
916
|
|
POST
|
@TrevorDenson Sorry for the confusion this is causing. Thank-you for the details. A list of SQLite keywords is available here - https://sqlite.org/lang_keywords.html. If possible would you be able to send me the schema of the layer that is giving you the error message? "I would doubt my use of Field Aliases/labels would cause this issue" You are correct, this is for field names. Colin's comment was from June 2023 and was in regards to a change to the Forms tab in Field Maps Designer and a fix was made shortly after Colin's comment around the end of June last year. His comment was not about the new messaging you are seeing in the Offline tab. The change that we added in this release was to add the new error messaging in the Offline tab. Prior to this release you would not have seen that error message, but SQLite keywords as fields have never been supported when taking a map offline. The maps will fail when trying to take them offline in mobile or fail when packaging map areas in Online/Field Maps Designer. This restriction with SQLite keywords is not new at this release, we have just made this more visible to help avoid packaging/offline download errors that would have been occurring. "My staff is unable to download offline areas all of a sudden" This change was just in Field Maps Designer and did not change anything in Field Maps mobile. If your staff are taking maps offline from the mobile device, this change would not come into play. There might be another issue happening as well. What errors are your staff seeing on the mobile devices? Would you be able to send a troubleshooting log from Field Maps mobile? I would encourage you to reach out to support and submit an issue as well.
... View more
06-28-2024
09:10 AM
|
0
|
3
|
2689
|
|
POST
|
Hello @MikaylaLeishman It sounds like your feature layer is configured to "Allow update of true curve" and "Only allow true curve updates by true curve clients". Field Maps does not support editing true curves, which is why you are seeing the message. Both of this properties, "Allow update of true curve" and "Only allow true curve updates by true curve clients", can be configured when you publish your layer (Step 8 in the Configure Layers section of Configure a web feature layer) or modified after you publish (Editor permissions for feature services). Changing these properties will allow you to take the map offline
... View more
06-27-2024
03:06 PM
|
1
|
2
|
3680
|
|
POST
|
@TrevorDenson sorry to hear that you are having problems. Can you tell me a little more about your workflow? What are the error message? Where are you seeing these error message, Field Maps Designer or Field Maps Mobile? When the users are trying to take the maps offline what errors are they seeing? Would you be able to send troubleshooting logs from mobile? If you would like please submit an issue with support as well SQLite keywords as fields have never been supported when taking a map offline, the maps will fail when trying to take them offline in mobile or fail packaging in Online. This was not a new restriction, but we made changes in this release to error at authoring time so that we can more easily tell there is an issue with a layer and offline usage.
... View more
06-27-2024
02:00 PM
|
0
|
0
|
2752
|
|
POST
|
@FRODF you should not need to remove all of the indexes. It is the indexes created by Experience Builder that have a hyphen ('-') in the name that is causing the issue. Taking a map offline should work with the other indexes present.
... View more
05-20-2024
09:49 AM
|
0
|
0
|
3958
|
|
POST
|
Hello Levi, This can be configured in Field Maps Designer in the App Settings under Feature actions. Our documentation covers it in this section - Enable copying attributes and shape to a new feature
... View more
05-09-2024
10:32 AM
|
1
|
1
|
752
|
|
POST
|
Sorry for the inconvenience this is causing you. The Experience Builder team is planning to fix this in the next release, which is scheduled for mid June. @Jianxia
... View more
05-01-2024
10:46 AM
|
1
|
0
|
4197
|
|
POST
|
From the settings page, you should be able to delete those indexes from the layer and recreate them with a different name, without any hyphens
... View more
04-03-2024
12:30 PM
|
1
|
0
|
4811
|
|
POST
|
Hello, We have a recently reported issue with Experience Builder and offline maps, that the teams are working on fixing, that you might be running into. The issue is: "Configuring the Search widget with a layer source from a map in ArcGIS Experience Builder creates field indexes with '-' in the name that will cause SQLite replicas to fail for the feature layer." To check if this is the problem, you can look at the layers settings page in Online and in the Manage Indexes section view the Field Indexes. If you see an index name with a hyphen ('-'), this might be the issue you are seeing.
... View more
04-03-2024
10:07 AM
|
6
|
5
|
4827
|
|
POST
|
Hello Colin, Are you using ArcGIS Online or ArcGIS Enterprise? If you are using ArcGIS Enterprise have you followed the steps here: Use an Esri basemap offline?
... View more
03-04-2024
08:31 AM
|
0
|
0
|
607
|
|
POST
|
Hello @JohnHu, "Reload Map" should always be available for the current map. It does not show up for other maps that are not in the "Current" section. Also, if the current map has offline areas or is an MMPK the option is not shown. If your users still do not see "Reload Map" can you post a screenshot and details of the device and map?
... View more
02-09-2024
01:09 PM
|
0
|
1
|
3152
|
|
POST
|
Yes, this is correct. Users of type Creator would need to have the location sharing user type extension assigned to them. This is done per user, not by user type or role. The Mobile Worker users type is an exception as location sharing is part of this by default (but does not apply to you if all field staff are Creators). As you mention, you can leave the user types and role as is and just assign the location sharing user type extension to only the users you want to be able to share location, dont assign it to the others in the public works union.
... View more
02-08-2024
02:42 PM
|
0
|
0
|
5203
|
|
POST
|
Hello, Answers to your questions below. Also a couple of additional help docs to look at if you have not seen them: https://doc.arcgis.com/en/arcgis-online/administer/configure-location-tracking.htm https://doc.arcgis.com/en/arcgis-online/administer/create-track-views.htm 1. “our administrator has to turn on tracking as a feature for our organization” Correct, an admin needs to turn on location sharing for your organization and this does not turn on location sharing for any user. It just allows farther configuration to occur. 2. Configuration of what organization users can view track data is configured in TrackViewer where track views are created (https://doc.arcgis.com/en/arcgis-online/administer/create-track-views.htm). Only users with a role that has the view tracks privilege can view other user’s tracks. 3. “Then he has to assign licenses to the users who want to use tracking.” If the users are of type mobile worker they will be able to use location sharing, otherwise the user type extension will need to be assigned to each user that you want to be able to share their location. 4. “He has to go into the field maps designer and turn on location sharing in each individual app that needs tracking.” Configuration of an individual map to require location sharing be turned on (like you show in your screen shot) is an optional step. 5. “In field maps designer can he select a checkbox to allow users to see each others tracks for the same field app. If he doesn't check this box then they will only see their own tracks.” Configuring which users can view other’s tracks is done in TrackViewer with track views (https://doc.arcgis.com/en/arcgis-online/administer/create-track-views.htm). By default, in Field Maps a user can only view their own tracks. You would need to author a map, make sure they had the correct role/privilege and have a track view to be able to have them view other user’s tracks. 6. “Users who do not have the location sharing extension assigned to them will not be able to see the field app anymore if location sharing is turned on?” Users who do not have the location sharing extension will be able to use Field Maps without any issues, they just wont be able to share their location. 7. “The toggle for location sharing is turned off by default in field maps and is not tracking the worker until the click the toggle. The worker has to select the toggle to turn on tracking, and select a tracking duration of 4,8,12 hours or until switched off. Even if they close the app on their device it will continue to track the worker until they click the toggle to turn off tracking on this screen or on the gps screen, or when the time expires.” Correct, users need to turn on location sharing in the app and it will continue to share their location when the app is in the background 8. “Is the tracking data stored separately for each field map app, or is all of the tracking data stored in one place that is accessible to all users who have the track viewer enabled?” Tracks data is stored in one service per organization. Who has access to view this data is configured in TrackViewer with track views and by assigning roles that has the view tracks privilege can view other user’s tracks. I hope this helps with our questions.
... View more
02-08-2024
12:50 PM
|
3
|
2
|
5212
|
| Title | Kudos | Posted |
|---|---|---|
| 2 | 04-01-2025 11:40 AM | |
| 1 | 01-11-2024 04:08 PM | |
| 1 | 06-27-2024 03:06 PM | |
| 5 | 07-09-2024 01:13 PM | |
| 3 | 07-03-2024 03:58 PM |
| Online Status |
Offline
|
| Date Last Visited |
a month ago
|