Tabscanner Receipt OCR (Independent Publisher)

[tokyoben]

---

When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)

If this is your first time submitting to GitHub and you need some help, please sign up for this session.

• I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
• I attest that the connector works and I verified by deploying and testing all the operations.
• I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
• I attest that I have added response schemas to my actions, unless the response schema is dynamic.
• I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
• If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

• I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
• Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
• Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
• If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

[tokyoben]

@microsoft-github-policy-service agree company="Tabscanner"

[tokyoben]

@v-alisancic can anyone assist with this review please? Thank you!

[vmanoharas]

Hello @tokyoben,

Could you please correct the folder structure before proceeding for the review?

[tokyoben]

Hi @vmanoharas thank you for finding this, i have corrected the file structure

[tokyoben]

@vmanoharas any update on this? thank you!

[vmanoharas]

Hello @tokyoben,

Please address review comments.

[tokyoben]

Hi @vmanoharas I have made the requested changes. Thank you!

[tokyoben]

Hi @vmanoharas were these adjustments ok? let me know if there is anything else I need to update. Thank you!

[vmanoharas]

Hello @tokyoben,

Could you please resolve review comment?

[tokyoben]

Hello @tokyoben,

Could you please resolve review comment?

Hi @vmanoharas fixed and resolved comment, thanks!

[vmanoharas]

Dear Partner

I hope you are doing well.
Congratulations, your pull request is approved. We will move forward with the certification process. We are preparing your connector for production deployment and will queue up for the next deployment schedule. Once your connector onboards the next deployment schedule, it starts to deploy your connector in our production environments that typically takes 3-4 weeks.
Please let us know if you have any questions.
Thank you very much for working with us.

[tokyoben]

Dear Partner

I hope you are doing well. Congratulations, your pull request is approved. We will move forward with the certification process. We are preparing your connector for production deployment and will queue up for the next deployment schedule. Once your connector onboards the next deployment schedule, it starts to deploy your connector in our production environments that typically takes 3-4 weeks. Please let us know if you have any questions. Thank you very much for working with us.

Hi @vmanoharas I am seeing a message "Merging is blocked Merge is not an allowed merge method in this repository.This branch must not contain merge commits.", I have synced my branch so should merge now, thank you for your help on this!