Provide public Smart Processing extension APIs for partner lookup codeunits and more
Updated Smart Processing integration by changing six procedures from internal to public in the SIM_DI Templ. Field and SIM_DI Temp. Document Line tables, providing a stable API surface for accessing template and temporary document line data during custom processing.
Smaller improvements
Description: Updated Smart Processing integration by changing six procedures from internal to public in the SIM_DI Templ. Field and SIM_DI Temp. Document Line tables, providing a stable API surface for accessing template and temporary document line data during custom processing.
- Table 5673215 – SIM_DI Templ. Field:
GetFilteredFields(...),GetViaFieldName(...) - Table 5673242 – SIM_DI Temp. Document Line:
GetNextLineNo(),GetCellValueViaFieldNo(...),GetCellIndex(...),HasInvalidLookUpValue(...)
Impact: Partner extensions can now use these public procedures for lookup logic, data access, and validation without relying on internal methods, improving integration stability and maintainability.
Fixed and improved
Description: Fixed an issue where emails containing MSG attachments could repeatedly import attachments without completing processing. Emails now complete processing and are marked as read. New duplicate protection ensures that each email document is imported only once, even if the email remains unread or is manually marked as unread again.
Impact: Prevents duplicate entries and repeated imports. Previously imported emails can no longer be reimported by marking them as unread.
Description: Fixed an issue where the Document Inbound Guided Experience always displayed in English and did not respect the user’s language settings in Business Central. The Guided Experience now correctly follows the configured application language.
Impact: Users now see the Document Inbound Guided Experience in their selected Business Central language, improving usability and making the setup process clearer and more efficient for non-English speakers.
Description: Fixed an issue where template rules executing a custom codeunit within the process template did not persist updated values, causing all changes made by the codeunit to be discarded.
Impact: Custom codeunits invoked by template rules now correctly apply and retain their updates, ensuring that configured automation behaves as expected and that no changes are silently lost.