Invoice file not read in AI - "Input parameters are invalid for your model"

[pkhurana]

Hi all, hoping someone might be able to help me.

I have a flow using the Extract Information from Invoices action to pull the PO number and Invoice number from a PDF and put it in excel online.

I have tested the invoice within the available AI build Invoice Processing test sample, and it reads the file just fine. However, when I attempt the invoice within the custom flow which uses PDF from incoming as attachment it comes up with the error “Input parameters are invalid for your model.”

[JoeF-MSFT]

Hi @pkhurana ! Thank you for sharing your use case and the screenshots.

I see that you're using an expression in the AI Builder action. It should not be needed. You can build the flow like this:

Also, if your emails come with signatures, you might have to filter them out like this: https://learn.microsoft.com/en-us/ai-builder/form-processing-model-in-flow#filter-email-signature-fr...

I hope this helps, happy automation!

[pkhurana]

Hello Joe,

Thanks for your response. I tried this but still does not works. It seems the attachment pdf is coming as inline.

Regards,

Puneet Khurana

[JoeF-MSFT]

Thanks for the update Puneet! In the AI Builder action, what's the error message you're getting? Did you remove the base64toBinary function?

A couple of things we can try:

• Take the PDF. Navigate to the AI Builder Explore page (https://aka.ms/tryaibuilder). Select Invoice Processing and upload the PDF from the email. Is the data extracted correctly?
  
  
• If you then select Use prebuilt model --> Use in a flow and try that flow template, does it work for you?
  
  

[pkhurana · Accepted solution]

Hello Joe,
Thanks for your response.
1. I have removed the base64toBinary function
2. Using the available sample in AI Builder Explore page, this is working perfectly fine. This asks for a file when we run the flow manually and my requirement is to pick pdf from incoming mail on shared mailbox.
3. I am able to fix it (refer snapshot) but for the future new users, is it possible to have this information in documentation, may be clarity will help others.