We are in the process of upgrading E9 customizations to E10.
We’re seeing a new behavior where Add Operation and Add Material context menu choices are missing from the navigation tree. It seems to be the result of a field being set in an EpiNotification of the dataView that owns the notification. This has shown up for us in a couple of places.
I can see where it could be recursive, but E9 didn’t complain. Should I be creating a class-level flag, setting it at the top of the notify, checking before doing work and clearing it at the bottom of the notification? Is there a cleaner way?
To reproduce the problem, I can create a new, blank workbench customization, use the wizard to add an Notification for ECOGroup and add this code. The catch is never triggered.
Thanks for any advice
private void edvECOGroup_EpiViewNotification(EpiDataView view, EpiNotifyArgs args)
{
if (edvECOGroup.Row > -1)
{
if ((args.NotifyType == EpiTransaction.NotifyType.Initialize))
{
try
{
edvECOGroup.dataView[edvECOGroup.Row]["Character01"] = "Are the nav tree's missing Add Operation and Add Material context menus because of recursion that E9 tolerated?";
}
catch(Exception ex)
{
MessageBox.Show(ex.Message);
}
}
}
}