Connectivity Studio now supports automatic posting of Route card journals when using the Report as finished journal document type. Previously, when the Post journals toggle was set to “Yes” in the document header, the journal was created but not posted. This happened because the system expected the ProdParmReportFinished table, which lacks necessary route-specific data.
The solution now supports posting based on actual production activity by using ProdJournalTable and ProdJournalRoute as target records. This ensures that route card journals created during message execution are automatically posted without user action.
This is especially useful in automated production reporting scenarios where downstream processes depend on completed route entries.
Connectivity Studio now triggers default Dynamics 365 field methods during message execution. This enables automatic calculation of key budget fields, such as Original Budget on project budget lines.
Previously, when inserting ProjBudgetLine records via CS messages, the Original Budget stayed at zero, even with valid Cost Price values. This differed from manual entry, which uses system logic (e.g., close() on ProjBudgetLineDetail) to update values. The enhancement applies the same logic automatically during message execution.
This helps maintain financial accuracy when importing budget structures programmatically.
This update improves usability and automation for large-scale data migrations. Enhancements simplify field mapping, validation, and paging, while reducing manual effort and import errors.
A new feature shows source field mapping status. You can check whether a source field is:
This eliminates the need to query source structures manually, especially in complex or customized setups.
You can now make external reference fields mandatory. The import process validates their presence and shows an error if missing, improving data integrity.
The accelerator can now query legacy AX 2012 databases. You can build query views inside the AX 2012 database for use during migration.
New metadata fields—Implementation status and Development status—track each record’s stage and readiness, supporting testing and planning.
Paging now respects range filters on child records. The system avoids incorrect page counts by supporting:
ODBC documents are now supported in the sync type, alongside D365FO.
You can now sync only changed records using a datetime field. This improves performance in recurring loads.
A new field, CreatedByCompany, was added to external references. This improves data traceability and reporting across legal entities.
A new EDI staging rule checks that the requested receipt date on the sales header is a working day per the customer’s receipt calendar. If a calendar is assigned, the system verifies that the requested date is valid. This prevents orders from being scheduled on closed days.
The STAEDEAN Accelerator library now includes new EDI messages, accessible via the BisProject_TutorialEDI resource. Key additions:
These are part of a broader update to Order-to-Cash EDI flows.
Additional updates include:
