DocXtender is a free Insight Works app designed to simplify document attachment and SharePoint integration in Business Central. Most DocXtender issues can be resolved by reviewing the configuration, Business Central permissions, browser settings, or the underlying Business Central attachment functionality.
For setup and usage information, see the following resources:
- DocXtender Knowledge Base: https://kb.dmsiworks.com/knowledge-base/docxtender-overview/
- DocXtender Overview and Video: https://dmsiworks.com/apps/docxtender
- DocXtender Community Forum: https://kb.dmsiworks.com/forum/docxtender-and-navxtender/
The forum is monitored regularly by the Insight Works team and is the best place to post questions that are not covered by the documentation below.
DocXtender drag-and-drop area is not visible
If the standard Documents FactBox is visible but the DocXtender drag-and-drop area is missing:
- Verify that the user has the DOCX-USER (DocXtender User) permission set assigned.
- Verify that the user also has the required base Business Central permissions for document attachments.
- Compare the affected user’s permission sets with a user where the DocXtender drop area is visible.
- After changing permissions, have the user sign out of Business Central and sign back in.
- If the entire Documents Factbox or document count summary is missing, troubleshoot the user’s base Business Central permissions first rather than DocXtender, this will likely be missing a base Business Central permission set.
For the required permission sets, see DocXtender Permissions
Start with Business Central Attachments
Before troubleshooting DocXtender itself, confirm that the underlying Business Central attachment functionality is working correctly.
1. Test attachments without DocXtender
On the affected Business Central page, try adding the same file manually using the standard Business Central functionality.
Use the Attach File action, or the + action in the Links FactBox, and test both:
- Browsing to the file
- Dragging and dropping the file
If the standard Business Central attachment functionality does not work, the issue is likely with the page, record, permissions, or Business Central configuration rather than DocXtender.
Also confirm that the record has already been created. Business Central generally cannot attach a document to a record that does not yet exist.
2. Confirm the user’s permissions
The Business Central user should have the following permission sets:
- IWORKS COMMON
- DOCX-USER, or a higher DocXtender permission set
3. Drag files from Windows File Explorer
For the most reliable results, drag files directly from Windows File Explorer.
Dragging files directly from another application is not supported and may behave differently depending on the application.
For example, dragging an email or attachment directly from Outlook Classic may have worked in some environments, but this behavior is not supported by New Outlook or Outlook in a browser. For now, the recommended workaround is to save the email attachment to your computer first, then drag and drop the saved file from Windows File Explorer into DocXtender. Or, alternatively consider the Business Central add-in for Outlook (https://learn.microsoft.com/en-us/dynamics365/business-central/work-outlook-addin).
If you would like Microsoft to support this feature in “New Outlook” make sure to vote for it here:
- Not able to Drag and drop attachment from New Outlook to web page, IDC (https://feedbackportal.microsoft.com/feedback/idea/4a7776f3-77bd-ed11-83ff-002248273995)
- Microsoft’s explanation of New Outlook drag-and-drop limitations ( https://learn.microsoft.com/en-us/answers/questions/5832520/not-able-to-drag-and-drop-attachment-from-new-outl)
4. Check Allow HttpClient Requests
In Business Central, open Extension Management and confirm that Allow HttpClient Requests is enabled for both:
- DocXtender
- IWorks Common
For each extension:
- Select the ellipsis (…).
- Select Configure.
- Verify that Allow HttpClient Requests is enabled.
It is worth checking this setting again after a Business Central environment update.
5. Try Silent Drop Behavior
On the DocXtender Setup page, try setting:
Drop Behavior = Silent
Then test the drag-and-drop process again.
6. Check for available app updates
Use the Business Central Admin Center to confirm that the environment is running the latest available versions of:
- DocXtender
- IWorks Common
Updating both apps can resolve issues that have already been addressed in newer releases.
Check the Business Central Page
DocXtender relies on standard Business Central FactBoxes and page behavior. If a particular page does not work while other pages do, review the page configuration.
7. Check for conflicts with other extensions
Use Page Inspection to determine whether another installed extension is modifying the same:
Document Attachment List FactBox
Multiple extensions modifying the same FactBox can sometimes result in unexpected page behavior.
8. Confirm the required FactBoxes are available
To use DocXtender, the Business Central page must have a Doc. Attachment List FactBox associated with a valid single record.
Depending on the DocXtender configuration, the page may also need the standard Documents and Links FactBoxes to be visible.
If necessary, use Personalize in Business Central to add the appropriate FactBoxes.
DocXtender uses these standard Business Central components but does not control when Business Central displays or hides them.
For example, if Business Central automatically hides a FactBox when there are no attachments, that behavior is controlled by the underlying Business Central page.
9. Refresh or reopen the record
After adding a document, refresh the page.
If the document or link still does not appear:
- Leave the record.
- Reopen it.
- Check the Documents or Links FactBox again.
DocXtender attempts to refresh the page after processing a document, but the standard Business Central Documents and Links FactBoxes ultimately control how and when the information is displayed.
Custom Pages and Primary Keys
10. Consider Business Central attachment limitations
Custom pages and tables require some additional consideration.
Standard Business Central document attachments use table 1173 Document Attachment, while record links use table 2000000068 Record Link.
These standard mechanisms have limitations when working with records that:
- Have multiple primary-key fields
- Use primary-key fields longer than 20 characters
- Do not have a single record that can be uniquely associated with the attachment
If an extension implements its own Documents FactBox by associating attachments with a separate unique integer field rather than the record’s normal primary key, DocXtender does not currently support that custom attachment implementation.
If DocXtender works on standard Business Central pages but not on a particular custom page, review how that extension has implemented its attachment FactBox.
Troubleshooting SharePoint Storage
If DocXtender works with regular Business Central attachments but has problems when SharePoint storage is enabled, continue with the checks below.
11. Check browser and workstation security
Confirm that the browser or workstation is not blocking:
- Pop-ups
- Redirects
- URLs
- SharePoint
- Authentication windows
Also review browser extensions and workstation security software, including:
- Browser add-ons
- Firewalls
- Antivirus
- Anti-malware software
- Pop-up blockers
- Application approval or security tools
If security software is suspected, testing from another workstation or a clean test VM can help determine whether the issue is specific to the original workstation.
12. Confirm the user can access SharePoint
When using the standard interactive SharePoint integration, the user should be able to open the configured SharePoint site in the same browser as Business Central without being prompted again for:
- Username or password
- Multi-factor authentication
- Application approval
DocXtender relies on the user’s existing browser session with SharePoint. The SharePoint credentials themselves are not stored in Business Central.
This is similar to signing into SharePoint and allowing the browser to remember the session.
If the SharePoint session cannot be retained by the browser, DocXtender may be unable to retrieve the SharePoint link after uploading the file.
If maintaining an interactive SharePoint session is not practical in the environment, consider the non-interactive integration options described below.
13. Review Non-Interactive Mode
If additional authentication or security prompts occur, review the Non-Interactive Mode configuration on the DocXtender Setup page.
Interactive mode is generally simpler because it uses the individual user’s existing SharePoint browser session.
Non-Interactive Mode can reduce the number of SharePoint licenses required for the integration, but it requires additional Azure configuration and maintenance because the configured client secret eventually expires.
If Non-Interactive Mode is required by another process but you want drag-and-drop to continue using the user’s normal browser authentication, use:
Non-interactive Integration = All Except Drag & Drop
This option is available beginning with DocXtender v2.5.
14. Try another supported browser
If the issue appears browser-specific, test using another supported browser such as:
- Microsoft Edge
- Google Chrome
- Mozilla Firefox
You can also try clearing the browser’s cookies and signing into Business Central and SharePoint again.
Avoid Incognito, InPrivate, or other private browsing modes when using interactive SharePoint integration because the SharePoint session cookies required by DocXtender may not be available.
15. Verify the SharePoint configuration
On the DocXtender Setup page, confirm that both of the following fields are populated correctly:
- SharePoint Site
- SharePoint Host
The configured site should be the first-level SharePoint site rather than a subsite.
16. Make sure the Links FactBox is visible
Documents stored in SharePoint are represented in Business Central as links, rather than standard Business Central document attachments.
As a result, some Business Central pages may need to be personalized so that the Links FactBox is visible in addition to the Documents FactBox.
17. Test SharePoint directly
Sign into SharePoint directly as the affected user and confirm that the user can:
- Access the configured site.
- Create folders where required.
- Upload a file into those folders manually.
If these operations do not work directly in SharePoint, they will also prevent DocXtender from completing the same operation.
18. Test without configured SharePoint folders
If one or more SharePoint Folder values are configured in DocXtender Setup, temporarily remove them and test again.
A user may have access to the SharePoint site itself but not to one of the configured folders.
When multiple SharePoint folders are configured, confirm that each required folder already exists and that the affected user has access to it.
19. Check Duplicate Behavior
If the file already exists in SharePoint, review the Duplicate Behavior setting on the DocXtender Setup page.
Depending on the desired result, try:
- Replace
- Automatically Rename
20. Review Microsoft permission prompts
If the user receives a Microsoft, Azure, or SharePoint permission or consent prompt, the prompt is part of the Microsoft authentication process rather than a DocXtender permission dialog.
When Microsoft requires user consent for an external application to access SharePoint, each affected Business Central user may need to approve that access.
If organizational policies prevent users from granting consent, a Microsoft 365 or Azure administrator may need to review the tenant’s application consent policies.
21. Test without SharePoint storage
If SharePoint authentication remains the issue, temporarily change:
File Storage Behavior = Document Attachments
or, where appropriate:
File Storage Behavior = External Storage
This can help confirm whether the issue is specifically related to the SharePoint integration or affects DocXtender more generally.
Licensing
22. Confirm the required licenses
DocXtender users require an appropriate Business Central license, such as:
- Team Member
- Essential
- Premium
For additional information, see:
https://kb.dmsiworks.com/faq-items/what-licenses-do-i-require-to-use-apps-from-insight-works/
Users accessing SharePoint must also have the appropriate Microsoft SharePoint licensing for the configured environment.
Still Having Trouble?
If the troubleshooting above does not resolve the issue, post the details in the DocXtender community forum:
https://kb.dmsiworks.com/forum/docxtender-and-navxtender/
Including the following information will make it easier to identify the cause:
- Business Central version
- DocXtender version
- IWorks Common version
- Browser being used
- Whether the issue occurs with standard Business Central attachments
- Whether SharePoint storage is enabled
- The Business Central page where the issue occurs
- The exact error message, if any
- Whether the problem affects one user or all users
- Whether the same user can upload the file directly to SharePoint
Screenshots of the DocXtender Setup page and the relevant error message can also be helpful. Avoid including passwords, client secrets, access tokens, or other sensitive authentication information.
Still need help?
Ask other Business Central users in the Insight Works community, or send the details to the support team. Include the steps you took and any error message you saw.