WRONG ID/Instance written into Context when Default Op. sel.

pureist

This relates to when a Custom Query Layout is selected.

According to an issue Bruce discovered, there could be a bug, depending on the answers to the below 2 questions:

Are Item Operations intended to be used with a Custom Query Layout, bearing in mind that Item Operation buttons usually won't display on an Instance which has a Customm Query Layout (subject to it's HTML/CSS)?
If, 'yes', then, is only a Default Item Operation intended to be used (hence why the 'Operations with items' panel still shows when Custom Query Layout is selected)?

If the answer to either of the above it, 'yes', then there is a bug according to Bruce's experience/advice:

"When a Default Item Operation is selected/activated on an Instance which has a Custom Query Layout, the wrong ID/Instance is written into Context"

BLOMASKY

I took the SalesPortal sample app, wrote a custom query on the employee (put it on menu on left). When you select a record, you will see that the system selects the record that is DOUBLE the row number. (i.e. if you click on row 3, you get the 6th record).

Bruce

SalesPortalWithCustomQuery.bsv.zip

61.87kB

SalesPortalWithCustomQuery.bsv.zip

61.87kB

aware_support

When we take out the <style> element from your custom template everything works as expected.

You cannot use <style> inside a custom template - use CSS classes instead of use the "style=" attribute.