Connections
- Release notes
Core extensions
- Release notes
- Introduction
- Company colors
- Exchange rate import
- Reciprocal exchange rate
- User security audit detail report
- General and inventory journal import
- Business process links
- Import budgets
- DMF Toolbox
- Print Management
- Data Anonymization
  - Data Anonymization
  - FAQ
- Other
  - Data-entities
  - Security-configuration
- FAQ
  - FAQ
  - Coming Soon
Electronic Data Interchange (EDI)
- Release notes
- Introduction
- FAQ
- Core module
  - Introduction
  - Process overview
  - Trading partner and documents
  - Setup
  - Processing
    - Functional acknowledgement outbound
    - Functional acknowledgement inbound
  - Managing files
  - Workspaces
    - EDI Document maintenance workspace
  - Inquiries
    - Functional acknowledgement received
    - Trading partner documents
  - Other
  - Technical guide
    - Web API
    - Technical FAQ
- Customer module
- Vendor module
- 3PL module
- Freight forwarder for Landed cost module
  - Introduction
  - Process overview
  - FAQ
  - Setup
  - Processing
  - Workspaces
    - Landed cost processing workspace
  - Other
    - Data entities
    - Security configuration
- Integration systems module
  - Introduction
  - Setup
    - Integration systems
    - Trading partners
  - Processing
    - Customer
    - Customer group
- Roadmap and release schedule
- Definitions and Acronyms
Finance utilities
- Release notes
- Introduction
- Setup
  - Cash and bank management
  - Accounts payable
  - Accounts receivable
  - ABN and IRD validation
    - ABN lookup and validation
    - IRD number validation
  - Budgeting
    - Budget import
  - Encryption/decryption
    - Encryption/decryption
  - Electronic reporting export
- Processing
  - Cash and bank management
  - Accounts payable
  - Accounts receivable
    - Customer remittance import
  - ABN and IRD validation
    - ABN lookup and validation
    - IRD number validation
  - Budgeting
    - Budget import
    - Example file format
  - Electronic reporting export
    - Export electronic reporting file
- Other
  - Data entities
- Technical guide
  - Web API Endpoint
- Roadmap and release schedule
- FAQ
Forex contract
- Release notes
- Introduction
- Setup
  - Forex contract parameters
  - Forex over allocation
- Processing
- Other
  - Data entities
  - Security configuration
- Roadmap
Insights for D365 FO
- Release notes
- Introduction
- Setup
- Periodic monitoring
  - Periodic monitoring configuration
  - Number sequence monitoring
- BatchJob monitoring
- Review and set up monitored data
- Azure Application Insights
  - Dashboards
  - Alerts on Azure Azure Application Insights
- Limitations
- Security configuration
- FAQ
- Definitions and Acronyms
Item creation wizard
- Release notes
- Introduction
- FAQ
- Setup
  - Item creation parameters
  - Item creation workflows
  - Item creation
  - Item setup
    - Item status
    - Item creation workflows
  - File management
    - File management
- Processing
- Periodic tasks
  - Update item status
  - Item creation
    - Creation import files
    - Item import
  - Item status
    - Automatic status update
- Inquiries
  - Creation import sessions
- Other
License manager
Product Lifecycle Management (PLM)
- Release notes
Security Insights for D365 FO
Smart Business Form Email Manager (Smart Send)
- Release notes
- Introduction
- FAQ
- Setup
- Processing
  - Email processing
  - Electronic Reporting
- Other
- Roadmap
Solutions for DocuSign and Dynamics 365
- Release notes
- Introduction
- FAQ
- Setup
- Inquiries
  - Documents
  - Exceptions
- Other

Error reporting

When EDI documents are processed, they may fail for various reasons. EDI module includes defined errors (via development), else the standard D365 error will be provided.

Process

When an Inbound document is received and processed via EDI it could fail for various reasons, examples:

Unit conversion not found
Receipt date not valid
Quantity not available ATP
Not within multiple/max qty
Item or Customer on hold
Mandatory dimension not specified

Previously these errors were only available as text log on the applicable staging document. Staging processing errors are now defined and saved to a table for reporting purposes.

Version log

Version log applies to Inbound documents, and users can access the staging forms by navigating to EDI > Documents. These errors can be viewed on the Version log form on each Staging form or EDI Document maintenance workspace.
If a record’s status was reset and reprocessed the Version log will show all the version’s status and if there were any errors, split these into Header and Lines. If there were no errors, a version is still created with blank error details. If an error is not defined the Staging to target status will be Error and the standard D365 error will be provided.
Show log shows only the latest log.
Version log form displays the following fields for each processing version:

Field	Description
Version	Starts at 1. If record is reset and reprocessed version will increment accordingly
Start timestamp	Date/time version was created
EDI Document type	Staging document type, example Customer purchase order
Staging to target status	The status of the processing record. Options include: • Error: The EDI file has been processed but there are errors with the record that needs to be reviewed. • Completed: The EDI file has been successfully processed.
Header
Error type	Displays: • Defined errors, examples ‘Order duplicate’, ‘Store code not found’, ‘Purchase order ‘%’ already exists on sales order ‘%’‘ • Processing error: displays the standard D365 error, example ‘Inventory dimension Site is mandatory and must consequently be specified.’
Level	Options include: Error or Warning
Message	Detailed error message
Lines
Line number	Staging line number
Error type	Displays defined error
Level	Options include: Error or Warning
Message	Detailed error message