virtual search columns
Description
Environment
Attachments
relates to
testing discovered
Activity
Diego Ruiz July 3, 2024 at 2:15 PM
Bug found caused by not setting isDisplayed to N by default
Diego Ruiz December 19, 2019 at 11:29 AM
Carlos Ruiz December 4, 2019 at 8:10 PM
So, the AD_Column.ColumnSQL is working like this:
Prefix | Type | Master | Grid | PO.get | Find | Report |
|---|---|---|---|---|---|---|
(none) | Virtual | Y | Y | Y - can impact the database heavily | Y | Y |
@SQL= | Virtual UI | Y | just on actual row | N | N | N |
@SQLFIND= | Virtual Find | N | N | N | Y | Y |
Carlos Ruiz November 29, 2019 at 9:32 AM
Thanks - I suggested adding the new syntax @SQLFIND= to avoid the ticket to bee too impactful - as this is expected to be added in 7.1. Adding a new flag implies changing the views AD_Field_V and AD_Field_VT, and those changes are usually painful as some people have also those views customized.
For this case I would suggest to keep it simpler with the @SQLFIND= and document it properly in the field Help.
Regards,
Carlos Ruiz
Heng Sin Low November 29, 2019 at 9:06 AM
Hi ,
I think it is simpler to developer that we can use existing virtual column and add a IsSearchOnly flag to indicate the virtual column is only for search dialog. One less special syntax to remember.
Regards,
Low
Details
Assignee
Diego RuizDiego RuizReporter
Thomas BayenThomas BayenLabels
Priority
Major
Details
Details
Assignee
Reporter
Labels
Priority
Major
We discussed that at the iDempiere workshop 2019.
Murilo showed the new functionality of virtual ui columns.
Thomas advised to add the possiblility of "virtual search columns" to have virtual columns to search with an sql formula. Perhaps we can even use that for reports. That allows to create advanced search logic without adding performance bottlenecks to the normal user interface windows.
Carlos liked the idea so we agreed to create this ticket for it.
That can also be combined with our ide to have relative saved searches.