I know this has been discussed before but I can’t quite figure out what is going on. We have many kinetic dashboards where the right click options work just fine. For example, right click on the order num and get the option for Order Entry and Order Tracker. But I have a new dashboard I created and it only has copy options no context options.
I can’t figure out what is different, other than the baq for this dashboard contains reference queries.
Where are the kinetic equivalents to these options? Or what step am I missing here?
I have seen (MANY) instances of right-clicking on the row that is “selected” results in the defunct context menu:
But if I right-click a row that ISN’T selected, the context menu populates:
I often find myself clicking into a different row (to switch the row that is in focus) so I can right-click on the row I actually want. How does THAT make sense?
With BAQ grids, we sometimes have to define everything.
First, make sure the column has the Like property set appropriately in your BAQ.
Then in the dataview, add a Custom Context menu item to the CustID that points to an event with the app-open widget pointing to the Customer Entry app and your customization layer
Seriously? Does anybody have a PRB for this if it really requires custom programming to get functionality back that was out of the box in classic? I would report it but I really don’t have time for a 2 hour webex to demonstrate to support.
I went to double-check where I had done this recently, and adding the Like property in the BAQ got me most of the context menus back
but there was another that opens with app-open (even in base) that I had to add as a custom context menu item
PRB0283904 i reported back in June, from Kinetic Browse if you have to load a Classic version of a screen you have not converted yet example job entry the custom context menu items added don’t appear. The problem was duplicated and acknowledged that they should appear as expected behavior but is listed as net yet planned to be fixed. Makes it hard to make a slow transition from Classic to Kinetic. When they force Browser First keep in mind that will strip custom context menus from all classic screens still used.