Release Notes - Polish Localization 5.3.0
| Application version | Release date | Compatible with Business Central |
|---|---|---|
| Version 5.3.0 | 16.08.2023 | from Business Central 20.1 (excluding Business Central 22.0) |
Changes and Fixes
The following changes have been made in Polish Localization version 5.3.0.
Functional Changes
| ID | Description |
|---|---|
| 11241 | We have added new publishers in the ITI Get Item Ledger Entry report: OnAfterCalculateTotals, OnAfterItemLedgerEntryOnPreDataItem, OnBeforeHasCrossedBorder, OnBeforeInsertItemJnlLine, OnBeforeInsertJobLedgerLine, OnBeforeInsertValueEntryLine, OnCalculateTotalsOnAfterSumTotalsin. |
| 11279 | We've added the Alt+I shortcut for the Additional NSeI Information action on all sales documents containing this action. |
| 11286 | The new validation has been added to check whether the value entered in the WalutaUmowna (ContractCurrency) element on the NSeI Document Elements page is a valid currency code. |
| 11315 | The Default for Automated Processing field has been added to the numbering series templates for sales/purchase documents. The template will be used during processes where the user interface is not allowed (for exmaple: when documents are created by a job queue). |
| 11600 | Assisted Setup for the NSeI has been changed. If the settings have already been initialized, by restarting the Assisted Setup the user will open the ITI NSeI Schema Versions page. |
| 11575 | We have added a new event publisher: OnBeforeCheckSalesCorrReason in codeunit ITISalesCrMemoCrtrEventHandler. |
| 11587 | We have blocked the ability to edit the Skip On Sending to NSeI field on service documents. The default value is true, because sending a service invoice to the NSeI is not supported in the current version. |
Fixes
| ID | Description |
|---|---|
| 11259 | Service Desk Issue PLFAPPSD-888 We have added a feature for clearing the Corr. Invoice Line No. field after the value in the Corr. Invoice No.field on sales lines is changed manually. |
| 11269 | Service Desk Issue PLFAPPSD-1019 The calculation of the value in the P_62 field within the SAFT VAT with declaration feature has been corrected to exclude the value from the P_60 field. |
| 11302 | Service Desk Issue PLFAPPSD-1013 We have disabled checking mandatory split payment when only receipts on a sales return order and only shipments on purchase return order are posted. |
| 11569 | Service Desk Issue PLFAPPSD-993 We have added a restriction on changing the VAT Reg. No. Origin Country Code field on purchase documents depending on the selected option in the Bill-to/Sell-to VAT Calc. field in the General Ledger Setup table. |
| 11634 | Service Desk Issue PLFAPPSD-1043, PLFAPPSD-1041 We fixed an error during posting the Sales Credit Memo related to inconsistency of the VAT Amount calculated from the Before/After lines. The problem was related to calculating a VAT amount in the sales credit memo line created by using the sales correction wizard for specific amounts. |
| 11635 | We fixed an issue where after deleting a line from the VAT Posting Setup or Payment Method tables, the corresponding line was not deleted in the NSeI VAT Rate Setup or NSeI Payment Method tables during the validation of a NSeI schema version. |
| 11718 | The mechanism for the VAT Registration No. has been adjusted on purchase documents. In the current solution, if the VAT Registration No. and VAT Reg. No. Origin Country Code values entered on the documents are the same as on the vendor card, the system does not re-validate the VAT Registration No. A similar mechanism was previously introduced for sales documents. |
| 11730 | Service Desk Issue PLFAPPSD-1035 We have fixed the way how VAT posting setup is retrieved for lines entered in the general journal. |
See also
Polish Localization User Documentation
Polish Localization on Microsoft AppSource
Technical Support for the App - Contact your Microsoft Dynamics 365 Business Central partner