My team was using the google cloud vision api as the ocr engine with document understanding in an AP invoicing use case. Back in May there was an update to the Google API and we are now experiencing some issues - i.e. the invoice number needs to be read as “RI-1234” and now it reads as “RI1234” omitting the “-“ which is required. These invoices are high quality pdfs and have been trained for in AI Center.
The legacy version expires on August 20. Has anyone else experienced issues with this API and has any other ideas for a fix?
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:
Always search first. It is the best way to quickly find your answer. Check out the icon for that.
Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.
Topic that contains most common solutions with example project files can be found here.
Read our official documentation where you can find a lot of information and instructions about each of our products:
Meet us and our users on our Community Slack and ask your question there.
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!
It’s a common occurrence to have symbols such as dashes omitted in extraction, sometimes with trained it captures the dashes and sometimes it wouldn’t.
In your worse case scenario, if you see a pattern where “RI-1234” is extracted as “RI1234” frequently, you can add a post extraction validation through regex to add the “-” in “RI1234”
