Document Intelligence Custom Models built with the 2024-07-31 API version cannot be composed without a classification model

Question

Document Intelligence Custom Models built with the 2024-07-31 preview API version cannot be composed without a classification model. This was possible in the past using the 2024-02-29 preview API version. The compose button is greyed out and has the message "It need [sic] a classification model to compose" when I hover over. Is this an adjustment to the composed model feature, or a bug?

Answer 1

@Musngi,Meg,PH-Manila Greetings & Welcome to Microsoft Q&A forum! Thanks for posting your query!

For the above query, yes, you are right. There is a change with 2024-07-31 preview API version where a document classifier model is required explicitly instead of the previously behavior of implicit creation. See this page for changes in behavior between the latest version and previous ones.

The model compose operation v4.0 and later adds an explicitly trained classifier instead of an implicit classifier for analysis.

Why is this change being made?

A point based summary of the new model compose operation for training an explicit classifier and its benefits. See the benefits section for details.

• Continual incremental improvement.
• Complete control over routing.
• Ignore document specific document types during the operation.
• Analyze multiple instances of the same document type.
• Support for add on features.
• Assigned custom model maximum expanded to 500.

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.