Is it possible to increase the AI Builder collection limit above 200

[Lucian]

Hello,

Into another post Max collections in AI Model, @JoeF-MSFT mentioned:

Currently 100. If you build a model that reaches that limit, feel free to reach out by private message and we can see options to increase it.

At that time the limit was 100 and meanwhile was increased to 200, but is it (still) possible to increase it over 200?

I'm in the process of evaluating if AI Builder or Azure Form Recognizer could be used in processing invoices from almost 500 partners. Azure Form Recognizer have some advantages, but it's limited to 100 "composed models".

Unfortunately I cannot use the prebuilt model for invoice processing because of the "language limitations" and using 3 x AI Builder models will make difficult to detect which document should be sent to which model.

So is there other "better ways" to process about 500 different forms?

Kind Regards,

Lucian

[JoeF-MSFT · Accepted solution]

Hi @Lucian,

Great question - indeed the limit has been increased to 200 but unfortunately we cannot accommodate beyond that limit of 200 today. It's still a few months away, but we do have plans to increase beyond 500 by the second half of this year. 

In the meantime, three form processing models will be required and have a way to route to the appropriate model. Perhaps depending on where the invoice is coming from? For example a particular email address if invoices are received by email. 

I'm curious, what advantages you see in Azure Form Recognizer that we don't have in AI Builder today? AI Builder is built on top of Azure Form Recognizer and we aspire to offer the same capabilities within the Power Platform. Thanks for any feedback on this area!

[Lucian]

Hello @JoeF-MSFT ,

And thank you for the good news. Increasing the limit to 500 would be very useful in my case. Is there any roadmap information that I could "monitor" or at least to see the planning?

Meanwhile I could use for most of the incoming invoices the sender's email address to redirect to the proper model, except for a small percentage for which the sender is an "intermediate person" that could change over time and in this case I think I have to send the document to all the models and keep the results with higher confidence.

About Azure Form Recognizer, I can't tell too much because I did not have the chance to do some thorough tests (yet) but the main thing I liked was the fact I could set the data type for the extracted fields as string, number, date, time. And because I will process different "regional settings", the DMY, MDY and YMD settings seems to help me detect the "proper date value" when AI Builder will treat all fields as strings. 

One other think I found useful in Azure Form Recognizer was the "estimated accuracy" for each field in each trained model - here trained model seems to be the equivalent of "collection" in the AI Builder. So, when a field does not have an expected accuracy I will know I have to add more documents for the training process to have a better result.

But in rest, Azure Form Recognizer is seems harder to setup and use and I will prefer AI Builder because of the simplicity. Now with the upcoming 500 collections, probably would be my "best choice". 😉

Kind Regards,

Lucian

[JoeF-MSFT]

Hi @Lucian - I hope your week is off to a great start!

Regarding roadmap, we publish it as part of the Power Platform release notes: Dynamics 365 and Microsoft Power Platform release plans | Microsoft Docs And every time there is a relevant update to the product we will publish it in the Power Automate blog: Power Automate - Blog (microsoft.com)

Thanks for the taking the time to share the feedback on Form Recognizer.

• Data types is something that we are looking to support as well in AI Builder later this year, including dates.
• We're actually going through the testing phase for displaying estimated accuracy scores in AI Builder for form processing models, meaning that we will be releasing this soon. Here is a sneak peek. Stay tuned. 😉
  
  

If you have other feedback or questions, you know where to find us in this forum!

[Lucian]

Hello @JoeF-MSFT ,

Thank you for all the good news and links!

Kind Regards,

Lucian

[Loki1405]

Hello @JoeF-MSFT,

Just picking up on this thread and the potential of increasing the number of collections to 500 - is this still the case? I've read through the release planner and i can't see anything relating to this unfortunately.

Thanks in advance

[FBDST_Admin]

@JoeF-MSFT  Do you have more update to increase more than 200 collections on currently version  

[JoeF-MSFT]

Thank you for asking @FBDST_Admin! No new updates to share about this at the moment. 

[nicklimcs]

@JoeF-MSFT 

Hey Joe, any update on this? Looks like it is still capped at 200 collections.

Thanks.

Nick