Handle failure to manually create E-Document from posted doc with no …

[georgepomazkov]

Fixes message 'The e-document has been created.' being shown to user when the e-document was not in fact created.

What & why

In cases when the e-document could not be manually created from a posted document page with no explicit error, the system would still tell the user that 'The e-document has been created.'.

The fix implements a check in the underlying procedure CreateEDocumentFromPostedDocumentPage() to verify that the number of e-documents linked to this posted document has actually increased, and only in this case the procedure will exit with true. Otherwise, the action code calling this procudes from the posted document page will display message 'The e-document could not be created.'.

Linked work

Fixes #8181

How I validated this

• I read the full diff and it contains only changes I intended.
• I built the affected app(s) locally with no new analyzer warnings.
• I ran the change in Business Central and confirmed it behaves as expected.
• I added or updated tests for the new behavior, or explained below why none are needed.

What I tested and the outcome (required — be specific: scenarios, commands, screenshots for UI changes)

Manually tested the case for posted sales invoice described in the issue, the system showed the following message when the e-document was not created due to the document type not being supported by the E-Document Service and no explicit error being thrown.

Risk & compatibility

None.

[georgepomazkov]

@microsoft-github-policy-service agree