Custom Query returns wrong ID when record selected

BLOMASKY

I am just starting to get my feet wet with custom queries, however, I have a default operation in the "Operation with Items" table.

I have a process that has the BO as the input. My operation "DISPLAY MESSAGE BO.ID " Returns an ID from the BO but not the one I have selected. There seems to be no rhyme or reason. It seems to be one that is sort of close (2-5 rows away).

Any ideas?

Thanks
Bruce

pureist

dunno.
but you could remove the default item operation and instead add the following to the parent Instance Block Tag itself:

onclick="AwareApp.startProcess2('ProcessName', 'ObjectName', InstanceID, 'RenderOption')"
..InstanceID would be {ID}

might also need href=”#” at the beginning of the Tag, but not always in Aware.
Tag itself might also need to be changed from a div to an a, but not always in Aware.

Try just adding the above first. Thus the opening Instance Block Tag would look something like:
<div class="ClassName" onclick="AwareApp.startProcess2('ProcessName', 'ObjectName', {ID}, 'RenderOption')">
if that doesn't work, then you would add the href="#" before the class

Per user Guide:

..starts the process with the specified name and writes the specified object instance into context, and displays any output of the process according to the render option.

RenderOption can either be:
main - any output will be displayed in the main page replacing the current contents (use if there isn't going to be any output)
new_tab - any output will be displayed in a new closeable tab
AwareApp.getPanelId('FrameName', 'TabName', 'PanelName') <- obviously don't enclose function in ' '

I think FrameName has to be lower case.

BLOMASKY

Good News. That works fine. You da MAN

Bad News, I have a few Operations with items that show up when I right-click on the cell, and this on-click does not run, therefore the wrong ID is passed to those procedures.

This seems VERY strange that a RANDOM ID (from the file) is passed to processes. mmmm wonder if this is a known bug in custom queries....

Bruce

pureist

the "Bad news" sentence does not make sense to me.
What does 'cell' mean? Do you mean the block/div that is the instance itself?
Right clicking makes Item Operations appear (previously hidden?) on a Custom Query instance?

There are no bugs with Custom Queries that I encountered.

BLOMASKY wrote
Good News. That works fine. You da MAN

Bad News, I have a few Operations with items that show up when I right-click on the cell, and this on-click does not run, therefore the wrong ID is passed to those procedures.

This seems VERY strange that a RANDOM ID (from the file) is passed to processes. mmmm wonder if this is a known bug in custom queries....

Bruce

BLOMASKY

While your onclick works fine, I also have some "operations with items" and Aware will consistantly return the record that is double the rows down. so if I click on the 3rd row, I get the 6th row.

Do you have any "Operations with Items" in your custom queries"?

Bruce

pureist

No, never did have Item Operations in a Custom Query. It didn't display them.

Only an Item Operation set to be Default seemed to be recognized. However, based on your recent posts, it appears this contains a bug in that the wrong instance is written into Context.

Probably best just to stick to using <button type="button".. in the HTML if you need an Item Operation.

The following is a nice size slightly animated Bootstrap button which could be used in query instances:

<button type="button" class="btn btn-primary btn-xs" onclick="..

you can add: style="property: setting; property: setting; etc.;" after class and before onclick if you want to change the colour to the septic orange, or adjust other style properties from their default.

If you need more than one Item Operation, you could even have a cascading dropdown menu of Item Operations appear onhover or onclick. Refer:

https://www.w3schools.com/code/tryit.asp?filename=FB2NW1SM3SJY

Note: position: absolute; would need to be changed to position: fixed; if used in Aware, unless you can adjust the z-index of both, the Aware query itself, and, the Menu, so that the Menu overlays.

BLOMASKY

I like the fact that custom queries use the CONTEXT menu for Item Operations (so a right click will bring up the menu, and not take valuable space away from my grid). Too bad regular queries dont do that.

However until the "select the right row' bug is fixed. they have limited use for me.

Bruce

pureist

huh? i'm not following you. the structure of what you wrote suggests that Custom Queries have the bug. But they did not when I used them if you use onclick="..

like i said, just put the onclick in the parent div for instances, and behavior will be identical to having a Default Item Operation... ie. select the instance and the action assigned executes.

if you ask V. i bet there is a strong possibility that Item Operations are not intended to be used in Custom Queries (hence why they don't display), and thus the 'Item Operation in a Custom Query not returning the correct ID' is not actually a bug.

the moment a query layout deviates from a standard grid (which is what Customer Queries are for) it raises the question of, 'Where should the Item Operations be located?'.

and there is no provision in settings of Item Operations to specify their location on the instance.

and for a truly Custom Query layout, you will rarely want to always have Item Operations at the end, like they are for a Standard Query.

simpler just to incorporate the 'item operations' (as onclick="..) in the HTML of the Custom Query.

BLOMASKY

Purest, there IS an option for Operations with Item (check the hamburger menu.) It looks JUST like the ones in a regular query. Me things there is a bug e poo here. Perhaps V will take time off from getting V8 out the door and confirm this.

Am I the ONLY one who is using Operations with Items on a custom query?

Maybe???

Bruce

pureist

Yes, I know the 'Operations with items' panel is still shown when Custom Query layout is selected, and you can create them.

But this doesn't necessarily mean they are intended to be used in a Custom Query.
Or perhaps, only a 'Default' Item Operation is intended to be used, in which case there is a bug.
And regarding the bug, 'completely wrong Instance ID written into Context when Custom Query Default Item Operation activated', it's a pretty serious and careless bug to have gotten through.
...Hence why I reckon there's a good chance Item Operations are not intended to be used with a Custom Query layout.

What I mean by 'not displayed' is the Item Operation buttons themselves, which, if they exist, usually won't display on an Instance having a Custom Query Layout.

And back to the original point about location/positioning, there is no way in 'Operations with items' to define where on an Instance which has a Custom Query Layout they should be placed.

Custom Query layouts will generally not be a bland grid, and thus Item Operation buttons being positioned at the end (the only place they can appear) will not be suited to their layout.

Besides, where is the 'end' on the Layout of a Custom Query Instance?

Really, Support could resolve this question in 5 seconds:

Are Item Operations intended to be used with Custom Queries, 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:
"When a Default Item Operation is selected on an Instance having a Custom Query Layout, the wrong ID/Instance is written into context"

Reported here: https://forum.awareim.com/d/9589>

See what happens.

BLOMASKY

Custom Query Operations with Items show up on context (right mouse) button click. Darn, I wish that was an option for regular queries also. That does make sense, since there is no way to know how my custom query is laid out. But they ARE an option on the hamburger menu, so they should work. Oh well.

Bruce

mrbdrm

your issue is with the code you use to display the records.
try a very simple code to display the query and you will see the issue goes away.

BLOMASKY

I just did. Took the SalesPortal sample app and wrote a simple custom query based on the employee table. It still works the same (wrong) way.

Bruce

(i uploaded it to the Errors page on the forum if you wanna see)

BLOMASKY

If I have each field above each other one, then all is good (block mode)
however, if I use display: flex; then it breaks.
If I use display table-row I can get it to work also. So the issue is with Display:Flex