topic Re: Workforce Migration using Jupyter Notebook in AGOL in ArcGIS Workforce Questions

Workforce Migration using Jupyter Notebook in AGOL

AndyGeo — Tue, 31 Aug 2021 22:57:41 GMT

Hello,

I am trying to migrate some large workforce projects to the new version. When running the py script, I get through about 1,500 assignments before I get a connection error. Is there a way to run the workforce project migration or assignment migration scripts in a Jupyter notebook in AGOL to avoid connection lag?

Or is there a better way to migrate large assignment datasets into the new Workforce project? My largest project has about 17,000 assignments to migrate.

Thanks,

Andy

Re: Workforce Migration using Jupyter Notebook in AGOL

Anonymous User — Tue, 31 Aug 2021 23:45:55 GMT

Hi Andy,

Do you exactly which error you are getting? Do you have any logs?

Depending on what the error is, running it in a notebook may or may not help.

Re: Workforce Migration using Jupyter Notebook in AGOL

DanPatterson — Tue, 31 Aug 2021 23:59:50 GMT

are you using recent versions? from the github site?

workforce-scripts/scripts at master · Esri/workforce-scripts (github.com)

Re: Workforce Migration using Jupyter Notebook in AGOL

AndyGeo — Wed, 01 Sep 2021 00:08:11 GMT

I am using the latest from Github. Attached is a screenshot of the py script error. If migrating large qty of assignments isn't possible, what is the best way to keep the old assignments accessible. This is for a City client that needs to keep assignments for reporting and public works planning. Would it be better to export the old assignments and load that feature layer along-side the newer Workforce project assignments layer?

Re: Workforce Migration using Jupyter Notebook in AGOL

Anonymous User — Wed, 01 Sep 2021 00:27:28 GMT

From that error message it appears that in the process of uploading a jpg attachment, the server is closing the connection for some reason.

Does this always happen for the same assignment/attachment? I'm wondering if it's very large.

There is already exception handling in place (on line 442) and should just be reporting the exception to the logs. The script should continue on and try to upload the next attachment. Are you not seeing it continue?

The way the script works is is it migrates all the assignment features then it does all the attachments. So your project should actually have all the assignments it's just the attachments (or at least an attachment) that's causing issues.