Moving to the latest release of Sweet for ArcGIS

/

A major release of Sweet for ArcGIS is now available. This has some big improvements in functionality and appearance.

For customers accessing Sweet through ArcGIS Online, the existing Sweet (now named Sweet Classic) will continue to be supported alongside the new Sweet for ArcGIS until April 2021. For this release Apps will not be migrated automatically, and so you will need to manually migrate your Apps to the new version before this deadline.

Note: Customers using the Phase 1 Habitat Survey app will have a different migration pattern, which we’ll announce on releasing the next update to this template. Please look out for upcoming communications about this.

Here’s what you’ll need to do to migrate to the new Sweet for ArcGIS:

1. As the App owner open the Sweet Classic builder, find the App you want to migrate, and Export your App from Sweet Classic as a zip file

Sweet Export1.png


2. Then import it into the new Sweet for ArcGIS builder, using the option Create a new app > Create using a template > Import. This will create a new Web Map and a new Sweet App in your content.

Sweet Import.png

Note: Customers using ArcGIS Enterprise can export Apps using the Sweet for ArcGIS interface, or if you are not running both versions in parallel you can also use the command line operations.

To help you migrate your Apps in a way that works best for you, you will see a few options during the export/import for how to handle the data. Here are a few possible scenarios:

a. Include data in your export, and do not use existing data in your portal when importing. The new App will link to new Feature Services which contain a copy of the data from the exported App. This method is not suitable for large datasets.

b. Do not include data in your export, and do not use existing data in your portal when importing. The new App will link to new Feature Services but they will contain no data. The new App will have identical configuration to the exported App.

c. Do not include data in your export, and use existing data in your portal when importing. The new App will link into the existing Feature Services. If you use this option, you must not change the data schema of the Feature Services between the export and the import.

d. A mix of the above for different layers by using include data in your export, and use existing data for some feature services in your portal when importing. This gives flexibility, for example to copy data that’s edited but not copy large non-editable datasets such as MasterMap.

We expect all Apps to continue functioning as before in the new Sweet for ArcGIS. If you see any issues with your App after migrating, please contact Technical Support.