Modifying field order in Mysql table (BO)

pixerp

The following process rule:

PICK FROM Customer WHERE Customer.Name=?Name

will display a table form to select a customer (with the advantage of NO CONFIRMATION FOR ONE).

The problem is that the order of the columns is not controllable in the configuration tool.

In fact, the column order is reflecting the field order of the Mysql table. Each time you test a BSV with "no intial data", all tables are deleted and recreated.

Can Aware support explain how this is done and if it's possible to tweak the process.

Thanks

aware_support

Are you talking about objects created from existing database tables?

Aware IM should respect the order specified in the Configuration Tool unless there is a bug somewhere. Are you sure it doesn't?

pixerp

No, I'm talking about AwareIM database BO (installed with Mysql).

In the Configuration tool, BO attributes are sorted by Name and I don't find any way to specify a kind of "sort key for automatic presentation".

When you use action PICK FROM BOxyz WHERE BOxyz.Name=?Name, the columns are listed in the same order as when you publish the BSV for TEST with "no initial data".

The tables are deleted (drop) and recreated. Where is the information stored to recreate the tables, I don't know but you do. And I would like to be able to make changes in the Field order...

Is it better explained so ?
Thanks for your answer.

aware_support

I understand now. PICK FROM with this syntax does not support column order. If column order is important to you, you need to define a query in the Configuration Tool and specify column order in this query. Then use the following syntax:

PICK FROM queryName ...

pixerp

Yes, I know this form off PICK FROM.

The problem is that NO CONFIRMATION FOR ONE is not supported -> the query result is always displayed even if there is only one instance.

The user must then click in the (very small) select circle and then click OK in the caption of the form or move his hand to the keyboard to press Enter !

In a Contact management application this is just not acceptable by the users.

Of course, the very best solution would be to implement the NO CONFIRMATION FOR ONE principle in the Query definition or to add a "column order" option in the attribute definition form (automatically numbered 10 by 10) ...

pixerp

After further testing, I found how to use the NO CONFIRMATION FOR ONE :

PICK FROM queryBOxyz NO CONFIRMATION FOR ONE

This will work as expected.

My previous error was due to writing PICK FROM queryBOxyz WHERE BOxyz.Name=?Name NO CONFIRMATION FOR ONE and the configuration tool accepting this formulation... but error in operation mode.

Anyway, there is still a possible improvement to implement :

if no matching is found then display ALL instances instead of none !

That would avoid to have to start the process again from the menu (mouse/keyboard flip-flop).

Thanks