Modern Document Understanding production deployment issue

Help Document Understanding
,
1

This product seems to have the same issue as the integration service once had. We trained a model in a Dev tenant and moved it to Prod (export/import etc.). The automation was also developed linked to this Dev tenant.

After publishing the project to production, we got the error “Extract Document Data: The resource requested on StartDigitization cannot be found.”

This happened because Studio still referenced the model in the DEV tenant. To fix that, we had to connect Studio to the PROD tenant, reselect the model in Studio, and republish.

It would be nice to be able to use an argument in the Orchestrator under ‘edit process’ → Package requirements.

5

Hello @mikebosWPP!

It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.

First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.

You can check out some of our resources directly, see below:

  1. Always search first. It is the best way to quickly find your answer. Check out the image icon for that.
    Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.

  2. Topic that contains most common solutions with example project files can be found here.

  3. Read our official documentation where you can find a lot of information and instructions about each of our products:

  4. Watch the videos on our official YouTube channel for more visual tutorials.

Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.

Thank you for helping us build our UiPath Community!

Cheers from your friendly
Forum_Staff

6

@mikebosWPP I did faced same kind of issue. So I made the ML skill as public and used the endpoint to access it.

Thanks,
Sagar

7

Hi Sagar,

Thanks, that sounds like another good workaround, although I wonder if that doesn’t raise some data security flags.

I hope this functionality gets improved so we can select the needed models directly from the process in Orchestrator.

9

Hello,

We are working on bringing both cross-tenant support to the DocumentUnderstanding.Activities pack, as well as variable support for project and version/tag selection.

This will make migration of code from dev to UAT to prod much easier, as all you will need to do is store the project + version or tag in some sort of configuration (like an asset), configure that properly in your environments, and the same automation should run correctly.

1 Like
10

Delivered our first project in modern experience in our company. I was very disappointed to know that we need to connect to robot machine ( only that has production tenant access ) and change project to point out the production model. Why is it nos visible in process requirements like asset, queue, connection for integration service… ?

11

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.