Dynamics Community Forum Thread Details

Issue:
Integration Challenge with Form Recognizer, RPA, and Continia Document Viewer in Business Central Environment

Environment:
Business Central version: 14.0.4810
Login platform: Nav Desktop Client
3rd Party Module: Continia Document Capture → Document Viewer
Details:
Our current workflow involves a multistep process integrating various systems to handle invoices seamlessly. Here is a detailed breakdown of the steps being followed:

Email Attachments Processing: Through Power Automate, we extract invoice attachments from emails.
Data Extraction: The extracted attachments are then sent to Azure Form Recognizer, which has been trained to OCR the files and extract the pertinent invoice details.
Information Transfer: This extracted information is then routed back to Power Automate.
Invoice Entry into BC: Following this, the Power Automate Desktop flow, operated by an unattended bot, takes over to input the extracted details into Business Central (BC). This part of the process is functioning without issues.
Local Storage of Invoices: Our aim is to save these invoices in the same local drive location where Continia stores the 'DCxxxx' files.
Record Insertion in Table: The final step involves inserting a record into a designated table that links the saved file with the invoice, enabling it to be viewed in the Continia Document Viewer.

Technical Challenges:
We are facing hurdles in the last part of the workflow, particularly concerning the record insertion in a table to link the saved files with their respective invoices. The challenges include:

Identifying the appropriate tables/pages which contain the necessary information to link a document to the invoice for viewing in the Document Viewer.

Receiving error notifications, such as /Entity does not support insert/ and “You do not have the following permission on Page”, hindering progress and access to potentially necessary pages.

We are utilizing the ODataV4 Service to insert invoice records, while aiming to use the same service for file linkages, but encountering problems.

Objective:
Our objective remains to successfully save and link the invoice files on the local drive to BC/Continia, facilitating seamless viewing through the Continia Document Viewer, without encountering errors in the record insertion process.

Questions:
How can we preserve the functionality of Continia Document Viewer for invoice viewing with the new integration.