Changelog eMessaging¶
What’s Changed¶
1.12.20250428.120 April 28, 2025¶
Features¶
Be able to approve for other users¶
Users can now approve documents on behalf of other users, streamlining workflows and improving flexibility.
Be able to edit lines in approval¶
Lines in approval workflows can now be edited, providing greater control and reducing errors.
Show lines for unapproved headers¶
Added functionality to display lines for headers that are still awaiting approval.
GL account should default to not having a discount % in line¶
Ensures that GL account lines default without a discount percentage, improving accuracy.
Add Approval field to Purchase documents list¶
Introduced a new "Approval" field in the Purchase documents list for better visibility.
Create a posting worksheet¶
Added a new posting worksheet feature to simplify and organize posting tasks.
Bug Fixes¶
Get payment info from BII documents¶
Resolved an issue where payment information was not being retrieved correctly from BII documents.
Take invoice discount into calculation¶
Fixed a bug where invoice discounts were not being factored into calculations.
PDF Viewer does not work on Purchase Document list pages¶
Addressed an issue where the PDF Viewer was not functioning on Purchase Document list pages.
1.12.20250416.106 April 16, 2025¶
Features¶
Able to link to existing vendor/customer¶
This feature allows users to associate e-documents with existing vendors or customers in the system. It ensures seamless integration and accurate tracking of business relationships, reducing duplication and improving data consistency.
Be able to post to VAT less item¶
When posting to items that carry no VAT amount incl. VAT will be used instead of amount without VAT.
Add CountrySubentity to purchase and sales headers¶
Introduces the ability to include the CountrySubentity (e.g., state, province, or region) from e-documents to purchase and sales document headers. This enhancement improves localization and reporting accuracy by capturing additional geographic details for transactions.
Bug Fixes¶
Status is still "in approval" after being approved¶
Resolved an issue where the status of a document incorrectly remained as "In Approval" even after the approval process was completed. The status now updates correctly to reflect the approval state.
Open purchase return order from inbound documents¶
Addressed an issue where users were unable to open purchase return orders directly from inbound documents. This functionality now works as expected, allowing seamless navigation.
1.12.20250402.79 April 02, 2025¶
Bug Fixes¶
When uploading the certificate wrong date is shown¶
In the new Centara Setup, you can now see your certificate and it's validity. Before it would show you the incorrect expiry date ( it would show you the start date). Now it's going to show you the expiry date.
Format the comparision Price Amount¶
eMessaging has a function where it will calculate the rounding of each line, so that it's more likely that all invoices send correctly out and without extra lines. In previous version, you could have a mismatch between our calculation of rounding and how Business Central was calculating if the G/L Setup rounding was setup in a way where you would have no extra places in the comma of the unit price. The error would come up in custom code in the customer environment, where the underlying database was saving the data with decimal points, but showing with out, which mean that a rounding was calculated. This fix, changes how we calculate the comparision so it's the same.
Work description is not shown as Note¶
When work description was configured in Sales & Receivables it was not always getting copied over to the XML.
Scheme for the JSON receiving when GLN¶
In some cases when end-users were sending Sales Invoices where the final destination was a GLN, the scheme was not set correctly. This fixed that.
1.12.20250327.63 March 27, 2025¶
New Features¶
Unit of measure convert on import¶
Now eMessaging can help with when two parties do not agree on the Unit of Measures. When the system is importing data from a third-party, we can remap the UoM so that BC thinks it was sent with another.
Let's take the example of ACME and EEA companies. ACME buys milk from the EEA company, when ACME creates a Purchase Order, they order 1 BOX of milk. But EEA company knows that when ACME company is buying 1 BOX of milk it's a carton for them. Because of some issue it's not feasable for the partners to agree on this in both systems, nor to use a base unit of measure.
In this case EEA can create a mapping when this ItemNumber get's selected so that both when it's ingested and sent out of the system, BC will swap the values.
Enhanchements¶
Rename Labels from Courier to Centara¶
To reflect our new branding of Centara, labels in our core applications that contained the word Courier, were changed to Centara. This should have minimal effect on users. The largest effect for end users is that the Role Centers called "Courier", "Courier Documents", are now known as "Centara" and "Centara Docuemnts"
Only validate item reference for Item lines¶
Before this version, if there was a Item Reference inbound, then we would validate that item reference against the system regardless of it the posting setup on the line was configured against an Item or an G/L. In this version this was changed so we are only validating and checking the item reference if the line is configured against Items.