Interactive report's data not displaying on the edit form.

Question

I have an interactive report that contains 3 rows. When I click on the edit button next to one of these rows, the edit form displays the data from that row.
But when I click the edit buttons next to the other 2 report rows, I get an error message that states: "ORA-01403: no data found. Error Unable to fetch row."
I do not see why this is happening. The PK of the table involved is "Request Date", so the report's "Link Column" region sends the value "Request Date" to the item P54_Request_Date in the form page.
Any idea why this would work correctly for one of the report rows but not for the other 2?
Clearly, each of the report rows must have a value for the PK, so why would the form not be able to find the same row that the report displays? Is it a problem with the form's "Fetch Row from" process?
Thanks.

Answer 1

Hello:
Your problems are primarily related to in your choice of a 'Date' type as the PK for your table. The Automated Row Fetch (ARF) process uses a SQL statement similar to the one below to retrieve a record from a table select c1, c2, c3 ... from tab where PK_col = :page_item_containing_PK_value . This would work find if the the 'page_item_containing_PK_value' were of the DATE data type. However, all APEX binds are done using varchar2. This means that the 'page_containging_PK_value' needs to have the char representation of the date that matches the default date setting on your database. So the page-item needs to be something like 'DD-MON-YYYY HH24:MI'. In your case the PK item is probably being set to 'DD-MON-YYYY' and therefore the fetch fails.
Now, for the 'issue with the :' in the character representation of the date.The link on the report page uses the standard APEX URL syntax to construct the link
f?p=App:Page:Session:Request:Debug:ClearCache:itemNames:itemValues:PrinterFriendly
As you can see, the ':' acts as the separator that delineates the components that make up the APEX URL. So, having a ':' in the 'itemValues' component will make the APEX engine treat whatever follows the ':' in the value passed as a delimiter as opposed to being part of the value being passed.
Varad