Comments
As of now, we have identified same issue for 2 different customers since last one year. I am not sure how many other customers suffer due to this, but this needs immediate attention. There is no logic to provide validation only for FTI transactions. Sales Invoices, Cr notes also should be included in the validation point of view. ex-Invoice Invoice account Name Sales order Date Voucher Currency Invoice amount SIN/0449589 C40023 ABC SO-000616755 14-11-2025 SIV/449591 AED 105 SIN/0449589 C40050 TEST SO-000616678 14-11-2025 SIV/449590 AED 278
This is really a required feature, and we support having this feature in future. As mentioned above proposed idea; by adding warning message and controlling through parameter we should enable this feature. While doing any extensions/ customization related to product/item, developers should follow best practices to avoid inconsistency.
While there is this article on Yun Zhu's website "Dynamics 365 Business Central: How to add Attachments, Links, Notes Factbox to any pages" https://yzhums.com/11177/ how to code it, having it out of the box would be wonderful. I have several clients with a use case requesting it to store the entry backup for how they came to the entry.
Having a payment agent who makes payments independently and provides us with a report would require the ability to manually enter details to the system generated report. Could we have the ability to add and remove vendors payments since the ATO requires only one TPAR report for each entity.
One of our customers has shared with us the work around they have used to link the correct account as bellow:add an extra field 'associated account to the contact for party tablevia javascript, fill the original associated account field with the value that was entered in the new fieldsave the record (MS plugin will update the associated account to another accountadd a power automate flow that will compare the new associated account and the original associated account - and update the original associated account with the value of the new associated account. that way we would always update the field to the value entered by the user - and avoid the problem that is created.