REST Endpoints

Supported operations: GET, POST

This endpoint enables access to the Therefore-Documents table, stored in BC. The table contains link between entries in BC and Therefore™ documents. For every document that shows up in the Drop Zone, an entry in this table must exist.

Examples:

Check if a Therefore™ document is already to BC

This can be done by sending GET request and applying a filter for “ThereforeDocumentNo”. There is no body required.

https://bcserver:7048/bc/api/therefore/connector/v1.0/tfdocuments?$filter=ThereforeDocumentNo eq 1234

Link a Therefore™ document to an object in BC

This can be done by sending a POST request to tfdocuments endpoint.

Sample Body:

Copy

{
"ThereforeDocumentNo": 1234,
"TableID": 38,
"DocumentType": 2,
"DocumentNo": "4321",
"CategoryNo": 11,
"AdditionalInfo": "Linked with REST",
"Filename": "invoice_4321.pdf"
}

This will create a link between Therefore document number 1234, stored in category 11 and a Purchase Invoice in Business Central (Table 38, type 2). The link will show up in the Drop Zone of the Connector, as invoice_4321.pdf. The AdditionalInfo is an optional comment, visible in the Therefore-Documents table.

Processing Journals

Endpoint: processingjournals

Supported operations: GET, POST

This endpoint reads or creates an entry in the BC connector’s “queue for saving”.

It can be used to schedule a delayed index data update or creation of a document.

Examples:

Check if a certain entry for delayed update of index data already exists in the queue for saving. This can be done by sending GET request and applying a filter for “Status” and for “NAVDocumentID”. There is no body required. The value for NAVDocumentID, has to come from the “LinkID” returned by “tfdocuments” REST endpoint.

https://bcserver:7048/bc/api/therefore/connector/v1.0/processingjournals?$filter= Status eq 'delayed update of indexdata' and NAVDocumentID eq 1234
Insert an entry into the “queue for saving”, to update index data when posting a purchase invoice. This can be done by sending a POST request to processingjournals endpoint. Sample Body:
Copy
```
{
"DocumentNo": ”1234”,
"NAVDocumentID": 4321,
"TableID": 122,
"CategoryID": 11,
"Status": "delayed update of indexdata"
}
```

This will create an entry into the “queue for saving”.
The “DocumentNo” 1234 is the invoice of purchase invoice in BC (not posted).
The “TableID” 122 is the posted Purchase Invoice in Business Central, so update will be done, when posting the invoice.
The “CategoryID” 11 is the Therefore™ category ID where the document is stored.
The "NAVDocumentID": 4321 is the “LinkID”, returned by “tfdocuments” REST endpoint.
The "Status" has to be set to "delayed update of indexdata".