After reading about the forms processing for invoice automation I was curious if this can be used for multiple layouts. For example, most demonstrations focus on the same invoice however different copies all with the same layout. Most organizations receive 100-1000s of different invoice layouts from different vendors, etc. Is this out of scope for the current functionality? Can you not have a model with many different invoice layouts from different vendors?
Solved! Go to Solution.
Hey @Dudditz
I have tried building the exact same functionality but it looks like it is currently not supported in a single model. This is out of scope based on the current functionality and you will have to build a different model for each form layout that needs to be passed through the specific form recognizer model.
Hope this Helps!
If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!
Thank you for your feedback. This is what I expected and really limits the usage to more simple requirements.
Hey @Dudditz
I have tried building the exact same functionality but it looks like it is currently not supported in a single model. This is out of scope based on the current functionality and you will have to build a different model for each form layout that needs to be passed through the specific form recognizer model.
Hope this Helps!
If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!
Thank you for your feedback. This is what I expected and really limits the usage to more simple requirements.
This has been my experience as well. I.e. That currently we are limited to one layout per model.
For that reason, I'm not really able to make use of AI Builder Form Processing, as in our case we have/need many layouts per model.
This functionality would be vastly more useful if it could handle multiple layouts.
Anyway, the potential is promising. Looking forward to future developments.
- Kyle
Join digitally, March 2โ4, 2021 to explore new tech that's ready to implement. Experience the keynote in mixed reality through AltspaceVR!
Power Platform release plan for the 2021 release wave 1 describes all new features releasing from April through September 2021.
User | Count |
---|---|
34 | |
16 | |
15 | |
12 | |
9 |
User | Count |
---|---|
36 | |
26 | |
17 | |
7 | |
7 |