25

we experienced an issue yesterday upgrading one third party extension for BC23.2 onprem where the data schema version was synched to the latest version (i.e. sync-navapp) but upgrading the codeunit (start-navappdataupgrade) failed due to bad code in the extension's OnUpgradePerCompany trigger in it's upgrade codeunit.


This leaves Business Central in a difficult position where the field(s) causing the upgrade problem is inaccessible to fix (not without rolling out throw-away PTE to fix the field errors via code, or fix the affected records via MSSQL, etc).


For onprem this is a hinderance with workrounds, but it becomes an even bigger problem with saas.


in RTC, the generic table viewer was RIMD, but in web client it is (and always has been) read-only.


I think it's time for Microsoft to re-assess that decision to make the built-in web client table viewer read only. It would save our implementors and developers a great deal of time if there were a way to edit these records should an emergency arise.

Category: General
STATUS DETAILS
Declined
Ideas Administrator

Thank you for your feedback. We are unfortunately not considering changing the current behavior of this feature.
 
Sincerely, 
Blazej Kotelko
PM, Microsoft 

Comments

S

Pay no mind to my last comment.


I was unaware that in newer versions of BC, both install-navapp and start-navappdataupgrade both have a -syncMode switch (meaning you don't need to first run sync-navapp first).


If install/upgrade fails, the schema sync will also roll back

Category: General

S

That's unfortunate that it was declined but I'm not surprised.


That said, I think Microsoft needs to re-think how extensions are synched and upgraded.


Currently if you successfully sync-navapp but start-navappdataupgrade fails, it leaves the app in an unusable state!


I think there should be a way to somehow batch both sync-navapp and start-navappdataupgrade into a single transaction.


If sync-navapp succeeds but start-navappdataupgrade fails, everything should be rolled back including the schema sync.


Unfortunately that doesn't happen currently and because it this, it leaves the app in a useless uninstalled + unupgraded state.



Category: General

S

Hello,

hopefully will you reopen this idea later. What is the critical number of voices to reconsider your decision, Blazej?

Regards,

Kamil

Category: General