We have been using Microsoft Dynamics NAV 5 from 2008 - 2015 and NAV 2015 version since 2016. Currently we are working on a migration project to BC365.

The problem with wrong or missing dimension values has been bothering us for a long time. Since there was no function for this, many years ago we developed a concept with our NAV partner for the subsequent change, which they then implemented. Due to the numerous differences between NAV 5 and NAV 2015, we had to extensively adapt our function after the migration, but it has now been running smoothly for over three years.

Now I read that Microsoft finally plans to add such a function to the standard as well. Of course, I think this is great in principle, because it means there is a chance that we can work without our customization in future. However, I am still lacking information at the moment to be able to assess whether the planned standard functionality can "keep up" with our own solution and does not represent a step backwards.

It is definitely not sufficient to update only a selected G/L item! All dependent posting transactions must also be identified and updated as well, so that no inconsistencies occur:
- Other G/L items that are related to the changed G/L item.
- Vendor items
- Customer item
- VAT items
- Bank items
- Purchase and sales documents (invoices/credit notes)
- Analysis view items (currently only possible with restrictions, because this involves copying and consolidating data that cannot be subsequently changed)
- Interface tables to connected systems

In addition, a reasonable reporting is required so that it is possible to track at any time which user has changed which dimension values in which G/L item and when, and which dependent items have also been updated automatically as a result.

Maybe someone from Microsoft reads this post and is interested in implementing the planned standard function optimally from the beginning. We are at your disposal for any inquiries... :-)