Update to Base Model in Current Document Understanding Project

[macaskillh]

I recently created a new Document Understanding project for CMS1500 in Production. When I originally created the Document Type I selected CMS1500.

I then created and deployed a new project version with the CMS1500 as the base model. I uploaded and annotated enough documents so my project score is 90.

When I ran my first set of claims I get the error message: No suitable document type found in project FEP_CMS1500_ClaimForm version FEP_CMS1500_V1

The only difference I see between UAT and Production is my base model. In UAT I have Custom selected, which I actually think is correct because I did have to make changes to the fields in document manager. Is this what is causing the error or am I missing something else?

Build:

Deployed Project version:

Base Model:

I was able to update the Base Model under Build > cms1500 > Settings to Custom

But when I try to create a new Project Version I’m still only seeing CMS1500 in the drop down.

[Karan_Rautela]

Hi @macaskillh , Can you please mention which document understanding activity is giving the error- ‘No suitable document type found’.

[Anil_G (Anil Gorthi)]

@macaskillh

When you are moving from one tenant to another..the deployed version names might be different..

So use a deployment tag and instead of selecting model select tag..that way when moved between tenants tag can be used to find rhe model

Cheers

[John_Goode (John)]

@macaskillh The issue is likely that when you create a new project version, the dropdown reflects the document type name (CMS1500) rather than the base model setting. Even though you changed the base model to “Custom” under Build > cms1500 > Settings, the project version creation dialog still lists by document type name. The key thing is to make sure that after changing the base model to Custom, you create a new project version and deploy it — the dropdown showing “cms1500” is just the document type identifier, not the base model. Once you deploy this new version, the error should resolve since it will use the Custom model with your field modifications. Also confirm that the project version you’re referencing in your automation matches the newly deployed version name exactly.

[Ioana_Gligan]

what activity package are you using, and what version?

If you open the automation in Studio on the new location after you migrated the model as well, and you reconfigure your extractor (re-select the project and version) - does it work?

We have implemented a series of improvements on the activities and went out in the latest version or will come out in the next couple of week that might solve this issue…