- Overview
- Getting started
- Building models
- Consuming models
- ML packages
- 1040 - ML package
- 1040 Schedule C - ML package
- 1040 Schedule D - ML package
- 1040 Schedule E - ML package
- 1040x - ML package
- 3949a - ML package
- 4506T - ML package
- 941x - ML package
- 9465 - ML package
- ACORD125 - ML package
- ACORD126 - ML package
- ACORD131 - ML package
- ACORD140 - ML package
- ACORD25 - ML package
- Bank Statements - ML package
- Bills Of Lading - ML package
- Certificate of Incorporation - ML package
- Certificate of Origin - ML package
- Checks - ML package
- Children Product Certificate - ML package
- CMS 1500 - ML package
- EU Declaration of Conformity - ML package
- Financial Statements - ML package
- FM1003 - ML package
- I9 - ML package
- ID Cards - ML package
- Invoices - ML package
- Invoices Australia - ML package
- Invoices China - ML package
- Invoices Hebrew - ML package
- Invoices India - ML package
- Invoices Japan - ML package
- Invoices Shipping - ML package
- Packing Lists - ML package
- Payslips - ML package
- Passports - ML package
- Purchase Orders - ML package
- Receipts - ML Package
- Receipts Japan - ML package
- Remittance Advices - ML package
- UB04 - ML package
- Utility Bills - ML package
- Vehicle Titles - ML package
- W2 - ML package
- W9 - ML package
- Public endpoints
- Supported languages
- Insights dashboards
- Data and security
- Licensing
- How to
- Troubleshooting
- About troubleshooting
- Moving Document Understanding™ modern projects between tenants or organizations
Document Understanding Modern Projects User Guide
Moving Document Understanding™ modern projects between tenants or organizations
When running an unattended process, an error occurs within the Extract Document Data activity in the Document Understanding workflow.
The following error is displayed when attempting to use a Document Understanding modern project that has been moved from one tenant to another:
Extract Document Data: The resource requested on `StartDigitization` cannot be found. CF-RAY: xxxxxxxxxxxxxxx-XXX. AppId: [GUID]Extract Document Data: The resource requested on `StartDigitization` cannot be found. CF-RAY: xxxxxxxxxxxxxxx-XXX. AppId: [GUID]The Extract Document Data activity from the UiPath.DocumentUnderstanding.Activities package references the Document Understanding project by ID and recreating the project in a different environment results in a newly generated project ID, not the one configured on the activity. Therefore, whenever a new Document Understanding modern project version is created, you need to update the automation and reference the newly created project version.
Regardless of whether the Generate Data Type property is set to true or false in the Extract Document Data activity, use the following steps to move a Document Understanding modern project/dataset between tenants:
- Export the annotated dataset from the first tenant.
- Import the dataset into a new project with the same name in the second tenant.
- Install Studio Desktop and point it to the second tenant.
- Open the project and reconfigure the Project and Extractor properties in the Extract Document Data activity.
- Publish the project to the second tenant.
- Run the project.
An alternative solution to work around the current limitation in UiPath.DocumentUnderstanding.Activities is to implement the Document Understanding Project Extractor activity from the UiPath.IntelligentOCR.Activities package v6.22.0 or above.
The Document Understanding Project Extractor and Document Understanding Project Classifier activities can use variables in the Project and Version fields so they can be configured as an Asset in Orchestrator.
Consider the following when using UiPath.IntelligentOCR.Activities:
- UiPath.IntelligentOCR.Activities v6.22.0 or above is compatible with UIAutomation.Activities versions that are v24.10.0 or later.
- Beginning with v6.19.0, installing the UiPath.IntelligentOCR.Activities package automatically installs the UiPath.DocumentUnderstanding.ML.Activities package. You do not need to install it separately.
- Do not use the UiPath.DocumentUnderstanding.Activities and UiPath.IntelligentOCR.Activities packages together in the same project.
