Document Inbound
Known Issue
Review Process Fails for Reviewers When SharePoint Authentication Is Required During Document Archiving (OAuth Popup)
Description: When a Document Inbound review workflow is configured with multiple reviewers and the final reviewer completes approval, the process fails if that reviewer is not already authenticated against SharePoint and Document Central is configured to use user-based (non-certificate) SharePoint authentication. During final approval, Document Inbound attempts to both create the unposted purchase invoice and archive/upload the document via Document Central. If a SharePoint session is missing, the system tries to initiate interactive SharePoint authentication (e.g., OAuth token acquisition) from within a codeunit and an active write transaction. Because Business Central does not allow UI operations (such as authentication dialogs or RunModal calls) during write transactions, the transaction fails with the error “Form.RunModal is not allowed in write transactions,” and the approval cannot be completed.
Impact: The final approval step fails with a generic Business Central error, the transaction is terminated, the unposted purchase invoice is not created, and the document is not archived. This interrupts the approval workflow and prevents completion of the business process whenever the final reviewer is not already authenticated against SharePoint and certificate-based uploads are not enabled.
Workaround: Enable certificate-based uploads in Document Inbound Module Setup by activating the option “Use Certificate for Archive Queue Uploads.” This allows SharePoint uploads to be executed without interactive user authentication and prevents the write-transaction conflict, although this setting was originally intended for background processing rather than standard approval scenarios.
Created: June 22, 2026
Priority: Medium