Don’t believe that’s currently possibly, as advanced search in the Aurena Client is basically using oData filtering and does not do a straight database SELECT call that you can hijack with an extra WHERE condition.

One way around this, for specific use cases only, is to create a custom read only attribute on the entity you’re searching that does this select call for you, and then use advanced search on that specific field, which will then be present and usable through odata filtering.

Note that for entities with lots of data/rows, this will likely have poor performance as the get method for the custom attribute will need to be ran on every row in the CustomerOrder Entity to evaluate the WHERE condition and return only the rows you’re expecting.

Dear @PRODQ ,

I believe such query you can manage by Lobbies. I can show you using example of Incoming customer orders:

The lobby looks as follow. When you drill down

it says that criteria are inherited from the lobby:

So the challenge is to create a proper data source that gets the data from customer_order and customer_credit_info (below the source of incoming_customer_order).

(We copied original lobby and edited the copy, just in case.)

Regards,

Kajetan

Thanks for engaging, Kajetan and Simon. 

To have to set up a data source and add into a lobby where I then have to go into the lobby, find the on stop link, click the link is somewhat overkill when I know the screen I want is “Customer Orders”.

It was also a question in principle.  We have many queries in Apps9 which use this ‘get’ function.  I can see our custom fields/attriutes in Cloud increasing exponentially.  

Another nail in the coffin of Cloud for me, sadly…

Linda