SQL & PL/SQL

I've tried to reproduce the issue using the EMP table on 20.1 but can't, it works fine

can you put this into your "JavaScript Initialization Code" for the ROWID item, run the page and copy/paste the output from your browser dev tool console

function( options ) {
    console.log(options);
    return options;
}

Hi there,

Your code is ok and use ROWID in select query.

Thank you guys for help, really appreciated!

Added your code in ROWID on Javascript initialization, output:

1. Object
   1. dataType: "ROWID"
   2. id: "147320781881306831"
   3. isHidden: true
   4. isPrimaryKey: true
   5. isReadOnly: false
   6. name: "ROWID"
   7. staticId: "C147320781881306831"
   8. __proto__: Object

As every row in an interactive GRID has it's own ROWID I assume APEX is aware of that.

this is mine from 20.1

1. Object
   1. dataType: "ROWID"
   2. id: "33623506008920468369"
   3. isHidden: true
   4. isPrimaryKey: true
   5. name: "ROWID"
   6. staticId: "C33623506008920468369"
   7. __proto__: Object

isReadOnly is the only difference, you could try setting that back but i don't see why it would break it

personally I'm not a fan of using ROWID, under certain conditions it can change and that would cause you all sorts of problems...

https://docs.oracle.com/en/database/oracle/oracle-database/12.2/sqlrf/ROWID-Pseudocolumn.html#GUID-F6E0FBD2-983C-495D-98…

is there a reason you aren't using a normal Primary Key for your DML?

I initially had it to "value protected" (read only) also to try out if this is the problem....

Now you may laugh: The table HAS a primary and I initially used it but after loading the mask all records in the displayed GRID were blue (selected) and whenever I changed a value in a record and clicked into the same column in another row it took over the values from the previous set record.I don't have this effect using ROWID but nevertheless I can try to set the original PK and see how the save process will handle that. Yes, agree, the official PK of the table should be used...

And all this because it's not possible to set an own separator for multiple chosen values (Poup LOV, Checkbox) in the DB (colon is used). So I have to do a replace ", " -> ":" on reading and on storing back from ":" to "," (it's any existing table I can't change it's content because there are load processes expecting a comma separator). The mask is VERY simple but now spending hours for such things... Nevertheless I'm happy for your hints, thank you!

Switching back to original PK but of course further problems with Apex: They PK (2 columns) are enterable attributes and Apex has difficulties when set/overwritten by user and PK is visible as such. No more words for that...