In ARF process, you only specify from which table to load data and what's Primary key column and it's respective item. With this APEX can't load data. You have to specify which DB column corresponds to which page item.
For this edit each item, go to "Source" section, here set following options as
Source Used : Always replacing..
Source Type : Database Column
Source value or expression : <DB_COLUMN_NAME>
With this APEX can map DB Columns to Items and can load data.
should not i see the rows in front of my eyes ?
Yes so something does go wrong. No the question becomes what goes wrong. And the only way to determine that is to debug.
Now in this thread automated row fetch
I have already asked the following:
Seems that we are talking about 2 different things.
I'm talking about creating a new record in the table the form is based on and after saving this new record displaying it in the same form.
You seem to be talking to when you first land on the page you expect a record to be displayed.
How do you move to this form page in your application.
For example do you have a report with a link to the form page?
If not how do you determine what the record is that should be displayed?
Either way as already mentioned by Lakshmi the item that holds the primary key needs to be set to that of the row you want to display before the fetch process is run.
So use the debug to see of the item that holds the primary key has a value before the automated row fetch process is run.
i will debug , but sorry , there is something i want to understand ,
i created a form on "dept" table , and i can see "automated row fetch" process created automatically , and the point is "on load : after header" ,
and the "run process: once per page visit"
when i run the page , i should see the data , and i do not ? why ?
But if there is the rub.. When you fire the form up, the load routine is looking at the page item with the primary key value to lookup in the dept table.. When you fire up the form, this page item is empty, thus it does NOT select a row from the dept table..
However, when the form is called by a report, the report normally will pass in a primary key item to populate on the form, thus the form will SELECT a row of data from the dept table..
Does that make sense??
This the basic code of what the "automatic fetch process" is doing
select deptno, dname, loc into :PX_DEPTNO, :PX_DNAME, :PX_LOC from dep where deptno = :PX_DEPTNO
Now when PX_DEPTNO is null there will never be a row that match the where clause so no row is fetch.