Form won't query existing record

Question

I'm creating a User Preferences page based on a table that contains one record per user, with the primary key = user_id.
The form creates the record fine. If I exit the form and get back in, however, it does not fetch that existing record.
The form has:
- An Application Item called GLOBAL_ID
- An Application Computation called GLOBAL ID with:
Computation Point=*On New Instance*
Computation Type=SQL Query
Computation=select f_get_id from dual
- A page Process called Fetch row from SZBRPRF with:
Process Point=*On Load Before Header*
Run Process=Once per Page Visit, ...
Item Containing Primary Key Column Value=*P1_USER_ID*
Primary Key Column=*USER_ID*
DML Fetch Mode=Set Memory Cache on Fetch
Runtime Where=*USER_ID = :GLOBAL_ID*
Success Message=*Fetched record for &GLOBAL_ID.*
- The P1_USER_ID item has the following attributes set:
Source Type=*Database Column*
Source Value or Expression=*USER_ID*
Default Value=*:GLOBAL_ID*
Default Value Type=*PL/SQL Expression*
When I open the page, the success message (Fetched record for +389+ is displayed, but the values are not.
So it looks like GLOBAL_ID does contain the value I want it to contain, at the time the fetch is executed, but the record is not found?
If I enter a value in one of the fields and click on Create, I get a unique constraint error.
I have also confirmed, via SQL*Plus, that the record exists in the database.
I keep thinking the problem is with the P1_USER_ID field, and have tried various combinations, but it still isn't working.
Any suggestions would be greatly appreciated.

Answer 1

Laura - Please change your handle to something easier to read and put your first name in your profile to assist us. Thanks.
Computation=select f_get_id from dualIf f_get_id uses APP_USER to determine the record ID, you should move that item-setting code into the authentication scheme's post-authentication process instead of using an on-new instance computation.
- A page Process called Fetch row from SZBRPRF with:
Process Point=*On Load Before Header*After-Header is a good firing point for ARF processes
Runtime Where=*USER_ID = :GLOBAL_ID*This seems redundant. I'd remove it.
- The P1_USER_ID item has the following attributes set:
Source Type=*Database Column*
Source Value or Expression=*USER_ID*
Default Value=*:GLOBAL_ID*
Default Value Type=*PL/SQL Expression*The ARF process fires way before any form item attributes (like Default Value) are evaluated. Plus, if the PK item is null, the ARF process doesn't fetch anything (the process success message notwithstanding).
I keep thinking the problem is with the P1_USER_ID field, and have tried various combinations, but it still isn't working.I think a before-header computation to set P1_USER_ID is your best bet (as Dimitri suggested). Make sure it fires before the ARF process.
Scott