Tabular Form created on a View is not Updating [message #600029] |
Thu, 31 October 2013 00:16 |
mm_kanish05
Messages: 493 Registered: January 2007 Location: Chennai
|
Senior Member |
|
|
Dear Experts,
I have created an Update only Tabular Form based on a Query that uses multiple tables, when I update the Tabular Form it throws the following error.
Error:
Current version of data in database has changed since user initiated update process. current row version identifier = "B89EC242C8E18CD81E441889ADFF4A40" application row version identifier = "A884FA378C851786DDFE3A33709CB23C" (Row 1)
My requirement is to insert data into a single table from that query.My query brings 3 columns with multiple records as static fields (non-updatable) and the other 4 fields are updatable and has to insert the data into a single table.
I also tried creating a view based on the same query and used it in the Tabular Form , but still it threw the same error. So I tried creating an instead of trigger for the view and still it threw the same error, but I am able to perform update on the view from the backend and data was inserted into that table also.
Can someone please tell me a solution to fix this error? Do I need to do any specific setting or add any process apart from the Apply MRU Process that is automatically created when a Tabular Form is created on a View?
Thanks and regards,
Kanish
|
|
|
|
|
Re: Tabular Form created on a View is not Updating [message #600242 is a reply to message #600232] |
Mon, 04 November 2013 00:44 |
|
Littlefoot
Messages: 21823 Registered: June 2005 Location: Croatia, Europe
|
Senior Member Account Moderator |
|
|
I see ... unfortunately, I'm not sure that this is the right choice. It means that a view has a primary key column, and it is the BOOKING_ID. Views don't and can't have primary key constraints, so that's rather doubtful. It looks as a nice try to fool Apex, but - eventually - it realized that it can't work.
As you saidQuote:... other 4 fields are updatable and has to insert the data into a single table could you rewrite it so that page is based on the "single table" you mentioned? If not, there's nothing much I can say about it. I never had the same problem so my experience equals zero.
|
|
|