The August 2020 release of ArcGIS Workforce allows you to create projects that are enabled for offline use. Projects created prior to this release are now categorized as Classic projects and listed in the Classic section of the Projects page.
While you can continue to manage your Classic projects using the Workforce web app, clicking Create Project will only create projects enabled for offline use in ArcGIS Workforce. To create Classic projects for use in Workforce for ArcGIS, you must use ArcGIS API for Python.
Follow along with this blog post to install ArcGIS API for Python and create a Classic project.
Note: Classic projects will only work in the Classic version of the mobile app, listed as Workforce for ArcGIS. They will not appear in ArcGIS Workforce. The icons for the different store listings are shown below.
For information on migrating Classic projects to projects that will appear in ArcGIS Workforce, see Migrate Classic projects.
Install ArcGIS API for Python
To automate and script Workforce projects, and to create a Classic project, you must use ArcGIS API for Python 1.8.3 or later. To learn how to install ArcGIS API for Python, see Install and set up ArcGIS API for Python.
Once you’ve installed ArcGIS API for Python, you are ready to create a Classic project.
Create a Classic project
Complete the following steps in either a Python script or Python console.
First, import the ArcGIS library:
import arcgis
Next, log in to your ArcGIS Online account using your login credentials:
gis = arcgis.gis.GIS("https://arcgis.com", "<username>", "<password>")
Finally, run the following command to create a Classic project, also known as a version 1 project. Be sure to give your project a meaningful title and summary:
version1_project = arcgis.apps.workforce.create_project("<project-title>", "<project-summary>", major_version=1)
After running this command, the Classic project is created and appears in the Workforce web app. You can configure the Classic project in the web app or with the Workforce module in ArcGIS API For Python.
For more information on working with Classic projects, see Create your first project (Classic) or Automate and Script Workforce (Classic).
In a geo database, dataset folder objects are prefixed with old database name .dbo. feature class names. What is the process of making these objects operate correctly after the database name is changed?
Hey Paul, can you provide some more info/details about your question? Where are you still seeing the database name stored?
I am opening the database in ArcGIS Pro 3.1.2 and all the datasets still have the old database name and none of the feature classes in the dataset folders are available. The geo databases on both the new testing server and the production server is still 10.8.1.
So, to get this to work properly must I upgrade my geodatabase version to be 11.x on the production server?
That is correct, this only exists with enterprise geodatabases in SQL Server that have been created or upgraded using ArcGIS Pro 3.0 or ArcGIS Server 11. Remember that ArcGIS clients older than Pro 2.3 / ArcGIS 10.7 will not be able to connect to the geodatabase once upgraded.
Oh wait I misread part of your statement… you are saying that accessing the existing geodatabase with 3.1.2 is having trouble listing the featureclasses in the catalog pane? If so then please open a support ticket so we can investigate that issue.
Esri Case #03373162
I need to understand why I can’t do the geo database upgrade on the destination server. I do not want to touch my production environment. I want to migrate apps and services over to the freshly upgraded geo databases on the new SQL 2022 server.
I am reviewing the support case and will be in contact with the Esri representative that is working with you there.
Hi Chet – is this new ability to change database name specific to SQL Server only or would the same apply to Postgres as well, so the system tables there wouldn’t store the database names either?
Was this question answered?
Currently this ability is only supported for enterprise geodatabases that are stored in SQL Server.