latest posts

Thanks for your answer, Martin.

I checked my configuration and for both of my files, I have page numbering set up to 'Continue from previous section'.

Hi Martin!
Update your body json content into a technical field. In the REST api call action refer the techical field in RAW mode. (right click on field)
We use this method a lot, this is the only workaround I found. It is annoying that you cannot switch off adding escape chars to a business rule result
I hope it help you.
BR
Peter

(Webcon team: please make it possible to to switch off char escaping in BR, or at least to use RAW mode for local variables in automation , as well!)

Hi everyone,

I’m facing a challenge when calling a REST API from WEBCON and I’m hoping someone has encountered something similar.

The API expects the payload in the following format:

{
"InterchangeToken": "NEWABC123",
"SupplierInvoiceCheck": {
"SupplierCode": "string",
"SupplierDocumentNumber": "string",
"SupplierDocumentDate": "2026-05-18T16:22:35.392Z",
"InvoiceEntityType": "PassiveInvoice",
"TotalTaxableAmountToCheck": 0,
"TotalInvoiceAmount": 0,
"ChangeRate": 0,
"TaxableIRPFAmount": 0,
"TotalIRPFAmount": 0,
"IsBlocked": true,
"ReversalDocumentNumber": "string",
"ReversalDocumentDate": "2026-05-18T16:22:35.392Z",
"AccountingRegistrationDate": "2026-05-18T16:22:35.392Z",
"AccountingMovementYear": 0,
"AccountingMovementNumber": 0,
"AccountingMovementID": "string",
"CreatedByUserID": "string",
"AssignmentByUserID": "string",
"BranchCode": "stri",
"CurrencyCode": "EUR",
"IRPFCode": "string",
"PaymentTermCode": "str",
"AccountingReasonCode": "string"
},
"DocumentAttachments": [
{
"DocumentContentExtension": ".PDF",
"DocumentContent": "",
"DocumentDescription": "",
"DocumentNumber": "",
"DocumentDate": "",
"DocumentType": "string"
}
]
}

Everything works fine until I need to send more than one document in DocumentAttachments.

The issue is with DocumentContent, which is expected to be a Base64 string. No matter which approach I try, WEBCON escapes forward slashes (/) into escaped slashes (\/) in the JSON payload, which causes the receiving API to reject the request.

I’ve already tried multiple approaches:

- Direct SQL query
- Business Rule
- Populating a technical field
- Storing attachment data in an item list
- Building the JSON in different ways

In all cases, the same escaping happens.

Has anyone dealt with this before or found a workaround using out-of-the-box WEBCON functionality? Ideally, I’d like to avoid using PowerShell or a custom intermediary service, although PowerShell is still an option if there’s no clean alternative.

Any ideas would be greatly appreciated.

Hi Daniel,

I don’t think this is a WEBCON issue, but rather related to how the Word templates are configured. Could you check whether the page numbering is set up correctly in the template?

Header/Footer → Page Number → Format Page Numbers → Page numbering

It should be set to:

Continue from previous section

instead of:

Start at 1

This is often the reason why page numbering resets after merging documents.

Hi everyone,

I am experiencing an issue with the "Merge attachments into a Word/PDF file" action.

When I use this action to merge multiple Word documents (.docx) into a single file, the page numbering in the resulting document is generated incorrectly.

As a result, the final document does not have a continuous page sequence (for example, the page numbering restarts from 1 at the beginning of each merged section).

I need the final, merged document to have consecutive, continuous page numbering from start to finish.

Has anyone else encountered this issue? If so, did you find a workaround or a specific configuration in Word/Webcon to fix this?

I would appreciate any help or advice on how to resolve this.

Best regards,
Daniel

Hi Martin,
Good point. I completely forgot about that :-)
Regards,
Jacek

Hei Martin,

thanks, thats it :-D

Regards, Gerd

Hello,

It is much easier if you use the "SearchIndex Source" for the report Source. This way you get the attachments in the System columns (see attached image).

Cheers,
Martin

Remember to add the condition ATT_IsDeleted = 0 to the SELECT (otherwise, you'll also see deleted attachments).

As for the link, you can try fiddling with /api/nav/db/1/attachments/xxxx/preview?hash=0 where xxxx is the ATT_ID.

Hei, thanks!!

This works fine so far! My SQL looks like this for a column type "Text"

(
SELECT STRING_AGG(A.ATT_Name, ', ')
FROM WFDataAttachmets A
WHERE A.ATT_WFDID = WFD_ID
)

It would be great to add a link to each attachment. I tried this, but i can not find the URL to the attachment in the Databse.

any idea if this is possible