It is not an issue but potentially a solution. If you did not synchronize your tables it may be a potential source of the problems.
I have mentioned forced synchronisation as it might have been that you have loaded a fob which changed G/L Entry table in a destructive way (changed the type or length of a field, or removed a fields), and the fob did not include upgrade codeunit handling this scenario, therefore 'normal' synchronisation would fail, leaving the metadata in inoperable state.
Forced synchronisation would enforce changes regardless but it may lead to loss of some data in affected tables - which is in some cases an acceptable solution.
Answers
Dynamics NAV, MS SQL Server, Wherescape RED;
PRINCE2 Practitioner - License GR657010572SG
GDPR Certified Data Protection Officer - PECB License DPCDPO1025070-2018-03
is that Issue?
I will do it now
Warm regards
Kris
I have mentioned forced synchronisation as it might have been that you have loaded a fob which changed G/L Entry table in a destructive way (changed the type or length of a field, or removed a fields), and the fob did not include upgrade codeunit handling this scenario, therefore 'normal' synchronisation would fail, leaving the metadata in inoperable state.
Forced synchronisation would enforce changes regardless but it may lead to loss of some data in affected tables - which is in some cases an acceptable solution.
Dynamics NAV, MS SQL Server, Wherescape RED;
PRINCE2 Practitioner - License GR657010572SG
GDPR Certified Data Protection Officer - PECB License DPCDPO1025070-2018-03