Latest Contributions by JustinColville

@LucasNeal the message you are seeing is just a warning message saying that your data has/support true curves, but Field Maps does not support editing true curves at this time.  As it is just a warning, you can still take this map and those layers offline and use them in Field Maps. If you would like to be able to edit the curves in Field Maps, which will densify them, then allow updates to true curves (allowTrueCurveUpdates : true) but dont "Only allow true curve updates by true curve clients" (onlyAllowTrueCurveUpdatesByTrueCurveClients : false). ... View more

@LucasNeal there are two properties of the layer, allowTrueCurveUpdates and onlyAllowTrueCurveUpdatesByTrueCurveClients, that you can see in the layer's JSON.  What are their values?  Can you send a screenshot of the error/warning that you are getting? From the service's item page, View   ... View more

@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

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

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

@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

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

@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

@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

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

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