Comments
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.
This can be configured but not using standard methods. Neil Parkhurst has a blog article here https://neilparkhurst.com/2023/11/11/omnichannel-for-customer-service-identify-customers/ where he outlines the steps to patch your Workstream with the revised conditional logic. These are the same steps you are given if you go through support.