Hi, thanks for reporting. In case you need a patch, kindly create an issue on github with some details. I tried to reproduce using textarea/rich text editor, but to no avail. Glad you find it useful.

2 files to be imported indeed and compatibility is with APEX 24.2. Unfortunately I don't have a 24.1 environment to backport the plugins.

There are 2 separate plugins for set and unset.

Mohamed, I disabled the regular IR searchbar, and then added a static content region with 'item container' template. Upon apply, I'm calling 'apex_collection.create_collection_from_query_b' and this collection is the source of the IR. I've uploaded 'condition-builder-demo-app.sql' to github in case you want to explore any further.

Hi Tom, in the demo page (see link at bottom of article), I put a on change DA on Name, Job and Manager. They have a Set Value on the Sal. They all seem to work fine. I've tested both 24.1 and 24.2. Do you have a page in apex.oracle.com where I can see the issue?

edited my answer

That makes sense, because your IG is not editable. So you don't have any column items, only cells. Once you make your IG an editable grid, it should work. For non-editable IG (and probably also for editable grids), you will need to check the underlying data in the model, which is conveniently passed in this.data You can check with help of the js model api. Eg: (this.data.selectedRecords.length && this.data.model.getValue(this.data.selectedRecords[0], 'DESCRIPTION') != "") Notice upon selection change, there can be multiple rows selected depending on the IG configuration.

Nice illustration of these methods. I found also the getNativeValue() method of use, from the numberFieldItem interface. eg apex.item( "P10_NUMBER_FIELD" ).getNativeValue(); This method automatically takes into account any format mask as configured on the item field.