Forcing a new row to validate

I have the following problem:
I create a new row using an invokeAction. The row has several attributes set to default values by overriding the create() method in the EntityImpl.
When I view the JSF if I click my commit button without entering any attribute values it says everything committed fine. This is not the case however because several required attributes were not entered. I believe the framework doesn't see any modifications to the row and fails to run the validateEntity() method on the EntityImpl.
I can solve this by raising a flag in the backing bean when a UI component is modified, however I don't think that solution is very good. Is there any better way to handle this scenario?
I am using JDEV 10.1.3.4.

I have discovered what is causing this problem. On the detail table the command button used to remove rows has its immediate property set to true. I do not understand why this would cause validation not to occur when I click a different command button that simply commits the page. Can anyone explain what is occuring? I would like to understand the problem and solution not just solve it.

Similar Messages

FillBy always fills in the same row in data grid view. How to make it fill in a new row for each click of the Fillby Button? VB 2010 EXPRESS?

Hi there,
I am a beginner in Visual Basic Express 2010. I have a Point of Sale program that uses DataGridView to display records from an external microsoft access
database using the fillby query.
It works, but it repopulates the same row each time, but i want to be able to display multiple records at the same time, a new row should be filled for
each click of the fillby button.
also I want to be able to delete any records if the customer suddenly decides to not buy an item after it has already been entered.
so actually 2 questions here:
1. how to populate a new row for each click of the fillby button
2. how to delete records from data grid view after an item has been entered
Thanks
Vishwas

Hello,
The FillBy method loads data according to what the results are from the SELECT statement, so if there is one row then you get one row in the DataGridView, have two rows then two rows show up.
Some examples
Form load populates our dataset with all data as it was defined with a plain SELECT statement. Button1 loads via a query I created after the fact to filter on a column, the next button adds a new row to the existing data. When adding a new row it is appended
to the current data displayed and the primary key is a negative value but the new key is shown after pressing the save button on the BindingNavigator or there are other ways to get the new key by manually adding the row to the backend table bypassing the Adapter.
The following article with code shows this but does not address adapters.
Conceptually speaking the code in the second code block shows how to get the new key
Public Class Form1
Private Sub StudentsBindingNavigatorSaveItem_Click(
sender As Object, e As EventArgs) Handles StudentsBindingNavigatorSaveItem.Click
Me.Validate()
Me.StudentsBindingSource.EndEdit()
Me.TableAdapterManager.UpdateAll(Me.MyDataSet)
End Sub
Private Sub Form1_Load(sender As Object, e As EventArgs) Handles MyBase.Load
'TODO: This line of code loads data into the 'MyDataSet.Students' table. You can move, or remove it, as needed.
Me.StudentsTableAdapter.Fill(Me.MyDataSet.Students)
End Sub
Private Sub Button1_Click(sender As Object, e As EventArgs) Handles Button1.Click
Me.StudentsTableAdapter.FillBy(Me.MyDataSet.Students, ComboBox1.Text)
End Sub
Private Sub Button2_Click(sender As Object, e As EventArgs) Handles Button2.Click
Me.MyDataSet.Students.AddStudentsRow("Jane", "Adams", "Female")
End Sub
End Class
Get new key taken from
this article.
Public Function AddNewRow(ByVal sender As Customer, ByRef Identfier As Integer) As Boolean
Dim Success As Boolean = True
Try
Using cn As New OleDb.OleDbConnection With {.ConnectionString = Builder.ConnectionString}
Using cmd As New OleDb.OleDbCommand With {.Connection = cn}
cmd.CommandText = InsertStatement
cmd.Parameters.AddWithValue("@CompanyName", sender.CompanyName)
cmd.Parameters.AddWithValue("@ContactName", sender.ContactName)
cmd.Parameters.AddWithValue("@ContactTitle", sender.ContactTitle)
cn.Open()
cmd.ExecuteNonQuery()
cmd.CommandText = "Select @@Identity"
Identfier = CInt(cmd.ExecuteScalar)
End Using
End Using
Catch ex As Exception
Success = False
End Try
Return Success
End Function
In closing I have not given you a solution but hopefully given you some stuff/logic to assist with this issue, if not perhaps I missed what you want conceptually speaking.
Additional resources
http://msdn.microsoft.com/en-us/library/fxsa23t6.aspx
Please remember to mark the replies as answers if they help and unmark them if they provide no help, this will help others who are looking for solutions to the same or similar problem.

Problem creating a new row when using tabbed regions

I am new to JHeadstart and ADF and have been using the evaluation version of JHeadstart (in JDev 11.1.1.3) to judge its efficacy for a new significantly-sized application. As part of that evaluation I have created a small application (you can do this with HR schema using say the Departments table) with a single entity and VO. On JHeadstart I have then placed some of the fields into multiple Item regions within a Tabbed region on the same page and below the Group (layout style Table, Table Overflow Style below With Splitter). Existing rows display fine and I can view the data on the separate tabs.
However, if I try to create a row, I can fill in the data on the main region, but if I fill in data on the first tabbed region I cannot switch to the next tab without an error being generated.
e.g. using Departments - fill in DepartmentId and DepartmentName on main region, fill in ManagerId on first tabbed region and try to switch to second tabbed region to fill in LocationId:
Missing mandatory attributes for a row with key null of type HRModule.DepartmentsView1
Attribute DepartmentId in HRModule.DepartmentsView1 is required.
Attribute DepartmentName in HRModule.DepartmentsView1 is required.
If you save, then you can navigate.
You can also demonstrate something similar (different error message but probably the same root cause) on the myJHSTutorial demo. If you navigate to an employee off the regions page and try and create a new employee (using the '+' button below the 'Employees' label), then the tabs are not refreshed and any attempt to change the tabs results in an error
Failed to validate a row with key oracle.jbo.Key[999 ] in HRModule.EmployeesView3
Attribute Salary in HRModule.EmployeesView3 is required.
Salary must be between 6000 and 12000 for this job.
The JHS devguide does not help. Any thoughts? I can send the HR sample if you wish.

OK, I was able to reproduce this. The problem is that when you switch tabs, a partial page request is send to the server which does not include the items filled in the table row itself, hence these items are not updated in the underlying view object row.
Solution is to have a partial trigger at the table or group level listening to tab events. We will add that to the next release, but you can also apply the fix yourself by adding the following lines to the stackedRegionContainer.vm template:
#if (${JHS.current.pageComponent.tableLayout} && !(${JHS.current.pageComponent.hasOverflowInline}))
## when creating a new row in a table, and using overflow right/below, when switching overflow tabs
## the items filled in the table itself must also be processed as part of JSF model update phase, to
## prevent required item error when clicking another tab in overflow area
## we can enforce this by making the whole group listen to tab events
#ADD_CUR_GROUP_PARTIAL_TRIGGER("#REGION_ID()Tabs")
#end
Add these lines just before the line starting with
<af:${elemName}
Steven Davelaar,
JHeadstart team.

PROBLEM WITH NEW ROW --- PLEASE HELP

Hello,
I've had it with the framework. It's been 20 hours and counting that I am trying to insert/validate a new record.
Things just don't work as advertised.
Here's the situation:
I have an entity object with various validation rules in the validate() method.
Then I have a simple JSP page to insert new records.
At submit of button, I follow the framework's default
create new row and fill it up, with the difference
that i need to validate the row as soon as I fill it up
with data from the http request:
<jbo:OnEvent name="Create">
<jbo:Row id="newrow" datasource="ds" action="CreateInRange" >
<% try { %>
<jbo:SetAttribute dataitem="*" />
<%
newrow.validate(); //******* NOTICE HERE THAT I VALIDATE
} catch (JboException ex) {
newrow.remove();
throw ex;
} %>
</jbo:Row>
</jbo:OnEvent>
Unexpected behavior 1: If the validation fails,
newrow DOES NOT GET REMOVED!!!! I know this
since when I view data thru a data table component,
the row is there WITH THE ERROR INFORMATION set!!.
If I do a commit transaction, then the erroneous information ENDS UP IN THE DATABASE!!!!!
Unexpected behavior 2: If I do a rollback, every
call to subsequent pages results in a jsp error:
java.lang.ClassCastException: oracle.jbo.html.jsp.datatags.OnEventTag
PLEASE HELP.
Chris Lambrou

I have (hopefully) found a solution to my part of this problem. I was getting the ClassCastExceptions on any page with a <jbo:row> tag after doing a failed DML action. I have tested this with the delete event. (btw, I am using jdev9.0.3.3 w/ BC4J/JSP) Before what I was doing was this:
<% try { %>
<jbo:Row id="delrow" datasource="ds" rowkeyparam="jboRowKey" action="Delete" />
<% } catch (JboException jboEx) { %>
do something
<% } catch (Exception ex) { %>
uh-oh, this is bad
<% } %>
If I removed the try/catch block everything worked fine. Unfortunatlely, I need to try/catch block here. To work around the problem I changed the code to this:
<% Row rowDelete = ds.getRowFromKey(params.getParameter("jboRowKey")); %>
<% try { %>
<%
rowDelete.remove();
%>
<% } catch (JboException jboEx) { %>
do something
<% } catch (Exception ex) { %>
uh-oh, this is bad
<% } %>
The second bit of code does the same thing (but it doesn't use a bean like I think <jbo:Row> does) and it doesn't cause the ClassCastError on subsequent errors.
I really hope this helps someone else because it took me forever to get a workaround!
~Rob Lundeen

Creating new rows in OrderLines child

I am currently having an issue when trying to create a new row in my order_lines table for an existing Order. When I try to do row.createRow() I get:
Trying to create a new order line
oracle.jbo.InvalidOwnerException: JBO-25030: Failed to find or invalidate owning entity.
     void oracle.jbo.server.EntityImpl.create(oracle.jbo.AttributeList)
     void org.cgfns.cerpass.bc.products.CrpOrderLinesImpl.create(oracle.jbo.AttributeList)
     void oracle.jbo.server.ViewRowStorage.create(oracle.jbo.AttributeList)
     void oracle.jbo.server.ViewRowImpl.create(oracle.jbo.AttributeList)
     oracle.jbo.server.ViewRowImpl oracle.jbo.server.ViewObjectImpl.createInstance(oracle.jbo.server.ViewRowSetImpl, oracle.jbo.AttributeList)
     oracle.jbo.server.RowImpl oracle.jbo.server.QueryCollection.createRowWithEntities(int[], oracle.jbo.server.EntityImpl[], oracle.jbo.server.ViewRowSetImpl,oracle.jbo.AttributeList)
     oracle.jbo.Row oracle.jbo.server.ViewRowSetImpl.createRowWithEntities(int[], oracle.jbo.server.EntityImpl[], oracle.jbo.AttributeList)
     oracle.jbo.Row oracle.jbo.server.ViewRowSetImpl.createRow()
     oracle.jbo.Row oracle.jbo.server.ViewObjectImpl.createRow()
     void org.cgfns.cerpass.bc.products.TestMasterDetailView.main(java.lang.String[])
This is the meat of the program. I've started simple to try to isolate the issue. BCs are having trouble inserting using the example provided in other OTN posts covering the same type of issue. I thinking BC4J might have a problem with the primary keys. The OrderHeaders table is linked to the OrderLines table via the OrderHeaderID but there is also a DB Sequence field for OrderLines called OrderLinesId. Both of there are checked as PK. I'm not sure if this may be causing an issue or not.
I did create a test using the OE schema on Orders and Orderlines and I am able to create rows in it. Howerver there is no DBSequence in the OrderItems table like there is in the OrderLines table that is giving me a problem. I am able to create a view link to the OrderHeaders table and the do the link.getSource and link.getDestination calls to get the viewObjects. I then create a new row using createRow and set the attributes and commit. All works fine in OE. I do the same on the other table (OrderLines, OrderHeaders) I get the error. My source is a follows.
public static void main(String[] args) {
TestMasterDetailView test = new TestMasterDetailView();
test.getApplicationModule();
String orderId = "1106";
if(test.am == null) {
System.out.println("Error appMod null");
ViewLink ordersToItems = test.am.findViewLink("CrpOrderHeaderFk1Link");
ViewObject ordersV = ordersToItems.getSource();
ordersV.setWhereClause("ORDER_HEADERS_ID = " + orderId);
ordersV.executeQuery();
System.out.println("RowCnt = " + ordersV.getRowCount()); // returns 1
Row oRow = ordersV.next(); // throws invalid entity
System.out.println("OrderHeadersId = " + oRow.getAttribute("OrderHeadersId"));
ViewObject itemsV = ordersToItems.getDestination();
if(itemsV == null) {
System.out.println("Error itemsV == null!");
System.out.println("Trying to create a new order line");
Row itemRow = itemsV.createRow();
itemRow.setAttribute("OrderHeadersId", orderId);
itemRow.setAttribute("OrderLinesId", "3030");
itemRow.setAttribute("StatusTypesId", "125");
itemRow.setAttribute("Quantity", "111");
itemRow.setAttribute("BundlesId", "139");
itemsV.insertRow(itemRow);
test.am.getTransaction().commit();
test.am.remove();
All I really want to do is insert a new record into the OrderLines table. From what I've read this seems to be an issue because of the associations. Any help would be greatly appreciated.
Thanks,
Brad Gibson
TUSC

It doesn't look like you're using DBSequence domain for the OrderLinesId attribute. If you are then you do not need to fill in the sequence as you've done in the create method.
Getting back to create issue, You may want to set the 'order' id (foreign key) values before calling super and then call the getOrder() (or getXXX where XXX is the order accessor in this entity) method to verify if the order of the given ID exists/found in the cache.
By the way, are you also using a similar create() in order with DBSequence as the type for the pK and you force a sequence value on top of it via setAttribute?
Yes, this is the create method inside CrpOrderLinesImpl.java
protected void create(AttributeList attributeList) {
super.create(attributeList);
SequenceImpl s = new SequenceImpl("CRP_ORDER_LINES_ID_SEQ", getDBTransaction());
setAttribute("OrderLinesId",s.getSequenceNumber());
Thanks,
Brad

OBIEE Write Back - Insert New Row

Hello,
I am new to these forums and looking for some help with OBIEE's Write Back feature.
I have Write Back working fine with respect to updating existing rows in a table (ie: the UPDATE tag), but was wondering how to force Write back to invoke the INSERT feature. I would like to be able to create new rows in a table to allow my end user to dynamically add and remove information. I have heard of this being possible (perhaps through some sort of temp. table) in other forum posts, but have yet to see how this is implemented. Also, is it at all possible to use Write Back to delete rows in a table? Any help here would be greatly appreciated. Thanks!
-Mike
Here is an exerpt from my working XML file:
<WebMessage name="NEWSNOTESADMIN">
<XML>
<writeBack connectionPool="Oracle Data Warehouse Connection Pool">
<insert>INSERT INTO WC_NEWS_NOTES (CONTENTS, CONTENT_DATE, IMPORTANCE_LVL) VALUES(@{c0},@c{4},@{c2})</insert>
<update>UPDATE WC_NEWS_NOTES SET CONTENTS='@{c0}', CONTENT_DATE='@{c4}', IMPORTANCE_LVL=@{c2} WHERE CONTENT_ID='@{c1}' </update>
</writeBack>
</XML>
</WebMessage>

Well first and foremost, Oracle explicitly states that writeback isn't meant to be used to transform OBIEE into a data entry system. Check the other posts on this subject...
On the "force insert": put the same statement you have for INSERT into the UPDATE tag. Related to the initial point I mentioned: you will have to worry about uniqueness yourself. OBIEE isn't an OLTP platform!
Re. delete: I liked Stijns recent post, so I'm going to use that as well:
http://www.justfuckinggoogleit.com/search.pl?query=obiee+delete+through+writeback
Third hit. Venkats blog.

Update statement inserts a new row instead of updating

My code should just update a single specific row in the table. I used a simple procedure to update a record in the current application as well and it runs without any problem except this case. Every time the query runs, it actually inserts a new row instead
of just updating an existing:
So here is my c# code:
try
command.Parameters.Clear();
command.Parameters.AddRange(vars);
command.CommandText = "Update" + tableName;
conn.Open();
command.ExecuteNonQuery();
conn.Close();
this.GetData(tableName);
catch
throw;
And here is my SQL code (please ingore 'Alter Procedure' statement, I just wanted to get the core script of the procedure):
ALTER procedure [dbo].[UpdateExpenditureItems]
(@ID int,
@Name nvarchar(50),
@IsGroup bit,
@Parent nvarchar(50),
@Description nvarchar(50)
AS
Begin
--a new inserted row seems to be a result of running IF statement rather than ELSE
if @Parent is not null
begin
declare @ParentID int
set @ParentID = (select ID from ExpenditureItems where Name=@Parent);
UPDATE ExpenditureItems SET Name =@Name, Parent =@ParentID, [Description] =@Description, IsGroup = @IsGroup WHERE ID=@ID;
end
else
begin
UPDATE ExpenditureItems SET Name =@Name, [Description] =@Description WHERE ID=@ID
end
end
I ran the query itself from sql management studio and it works fine. The problem seems to be in c# code, but there's nothing unusual. Same code for operations with the databse works fine in other parts of the software... I appreciate your help!
Thanks in advance!

Please can you post your full C# code for this function? Also the code you sent is not calling an SP? so why do we need to validate against the SP?
Fouad Roumieh
So here is my code:
//Update is called on OK button click
private void okBut_Click(object sender, EventArgs e)
//edit code runs here
SqlParameter[] pars = new SqlParameter[5];
pars[0] = new SqlParameter("@ID", int.Parse(idTB.Text));
pars[0].SqlDbType = SqlDbType.Int;
pars[1] = new SqlParameter("@Name", itemTB.Text);
pars[1].SqlDbType = SqlDbType.NVarChar;
pars[2] = new SqlParameter("@IsGroup", true);
pars[2].SqlDbType = SqlDbType.Bit;
pars[3] = new SqlParameter("@Parent", DBNull.Value);
pars[3].SqlDbType = SqlDbType.Int;
pars[4] = new SqlParameter("@Description", descTB.Text);
pars[4].SqlDbType = SqlDbType.NVarChar;
try
DAL dal = new DAL();
dal.UpdateData("ExpenditureItems", pars); //Update is called here
catch (Exception ex)
StaticValues.WriteEventLogXML(ex, this.Text);
switch (StaticValues.user.Language)
case "English":
MessageBox.Show("Database error", "Error", MessageBoxButtons.OK, MessageBoxIcon.Error);
break;
default:
break;
finally
this.DialogResult = System.Windows.Forms.DialogResult.OK;
StaticValues.currentNode = itemTB.Text;
public void UpdateData(string tableNameString, SqlParameter[] vars)
string tableName = tableNameString.Replace(" ", string.Empty);
try
command.Parameters.Clear();
command.Parameters.AddRange(vars);
command.CommandText = "Update" + tableName;
conn.Open();
command.ExecuteNonQuery();
conn.Close();
this.GetData(tableName);
catch
throw;
And here is GetData procedure:
public void GetData(string tableNameString)
string tableName = tableNameString.Replace(" ", string.Empty);
command.CommandText = "Get" + tableName;
command.Parameters.Clear();
if (!StaticValues.dataSet.Tables.Contains(tableName))
StaticValues.dataSet.Tables.Add(tableName);
else
StaticValues.dataSet.Tables[tableName].Clear();
try
adapter.SelectCommand = command;
conn.ConnectionString = DAL.ConnectionString;
command.Connection = conn;
conn.Open();
adapter.Fill(StaticValues.dataSet.Tables[tableName]);
conn.Close();
catch
throw;
And this is my complete code for sql procedure:
USE [ISWM project]
GO
/****** Object: StoredProcedure [dbo].[UpdateExpenditureItems] Script Date: 13.04.2015 9:09:36 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
ALTER procedure [dbo].[UpdateExpenditureItems]
(@ID int,
@Name nvarchar(50),
@Parent nvarchar(50),
@Description nvarchar(50),
@IsGroup bit
AS
Begin
if @Parent IS NOT null
begin
declare @ParentID int
set @ParentID = (select ID from ExpenditureItems where Name=@Parent);
UPDATE ExpenditureItems SET Name =@Name, Parent =@ParentID, [Description] =@Description, IsGroup = @IsGroup WHERE ID=@ID;
end
else
begin
UPDATE ExpenditureItems SET Name =@Name, [Description] =@Description WHERE ID=@ID
end
end
The codes posted above work great in other similar parts of the application where select, insert, delete and update is required.
Concerning my current problem - I ran the procedure itself in SQL Server Management Studio, and it works well. I would say that there's something wrong with my c# code, but it can't be wrong because it's quite simple and works in other place in my application...
I really don't get what's missing...

Generate a surregate key only when insert a new row - (SCD1)

Hi all,
I´m starting with OWB (10gR2) and I'm creating a simple template dimension with SDC type 1 with one source, one target and a sequence do generate the surrogate key.
The main properties configurations are:
- Target property: Loading type = INSERT/UPDATE.
- Only match the natural key between source and target.
- Only use the sequence.nextval when inserting a new row.
- Mapping: Set based.
The generated code was something like this:
{color:#000080}+MERGE INTO DIM_DEFAULT+{color}
{color:#000080}+USING SCR_TABLE+{color}
{color:#000080}+ON(SCR_TABLE.NATURALKEY=DIM_DEFAULT.NATURALKEY)+{color}
{color:#000080}+WHEN MATCHED THEN+{color}
{color:#000080}+UPDATE SET NAME=SCR_TABLE.NAME+{color}
{color:#000080}+WHEN NOT MATCHED THEN+{color}
{color:#000080}+INSERT(SK_DEFAULT,NATURALKEY,NAME)+ {color}
{color:#000080}+VALUES(SQ_DIM_DEFAULT.NEXTVAL,SCR_TABLE.NATURALKEY,SCR_TABLE.NAME)+{color}
Ok, it works fine! But the merge statement generates a new SK for each merged row even if the action is update! What I want is a new SK only when the process inserts a new row. Hard-coding, I possible solve this problem creating a function to return the nextval from a sequence and put it on the insert clause like this:
{color:#000080}+MERGE INTO DIM_DEFAULT+{color}
{color:#000080}+USING SCR_TABLE+{color}
{color:#000080}+ON(SCR_TABLE.NATURALKEY=DIM_DEFAULT.NATURALKEY)+{color}
{color:#000080}+WHEN MATCHED THEN+{color}
{color:#000080}+UPDATE SET NAME=SCR_TABLE.NAME+{color}
{color:#000080}+WHEN NOT MATCHED THEN+{color}
{color:#000080}+INSERT(SK_DEFAULT,NATURALKEY,NAME)+ {color}
{color:#000080}+VALUES(FN_SQC_NEXTVAL('SQ_DIM_DEFAULT'),SCR_TABLE.NATURALKEY,SCR_TABLE.NAME)+{color}
Hard-coded it works fine as I need and that´s the point that I want to know:
It´s possible perform this solution using OWB?
I tried to use Constants but this solution doesn´t work then I tried an expression calling my sequence.nextval function but the result was:
{color:#000080}+MERGE INTO DIM_DEFAULT+{color}
{color:#000080}+USING (SELECT FN_SQC_NEXTVAL('SQ_DIM_DEFAULT') AS SK_DEFAULT_0,NATURALKEY,NAME FROM SCR_TABLE) AS SCR_TABLE+{color}
{color:#000080}+ON(SCR_TABLE.NATURALKEY=DIM_DEFAULT.NATURALKEY)+{color}
{color:#000080}+WHEN MATCHED THEN+{color}
{color:#000080}+UPDATE SET NAME=SCR_TABLE.NAME+{color}
{color:#000080}+WHEN NOT MATCHED THEN+{color}
{color:#000080}+INSERT(SK_DEFAULT,NATURALKEY,NAME)+ {color}
{color:#000080}+VALUES(SK_DEFAULT_0,SCR_TABLE.NATURALKEY,SCR_TABLE.NAME)+{color}
It´s the same of merge the row using the SEQUENCE.NEXTVAL direct.
Does anyone have a workaround to solve this situation?

Hi,
Perhaps this comes a bit late but...
Have you tried to change attribute properties in the mapping? For simple example you have a source table in sa-stage which have to fields: code (varchar2(2), natural key) and description (varchar2(50)). You want to map those fields to target table where you have 3 fields: id (NUMBER(10), surrogate id, nextval from sequence when new row inserted), code (as from the source, natural key, the field to determine if the coming row is new or one to be merged) and description as in source table. Fields and datatypes are just for an example.
When you have source and target tables in your mapping (and fields mapped), drag the sequence operator to the mapping and map the nextval to target table's surrogate id field.
- Change target table operator properties:
* loading type = UPDATE/INSERT
* Match by constraint = no constraint
- Change target table attribute properties for:
* surrogate id field: Load column when updating row = no; match column when updating row = no; load column when inserting row = yes
* natural key field(s): Load column when updating row = no; match column when updating row = yes; load column when inserting row = yes
* all the regular fields: Load column when updating row = yes; match column when updating row = no; load column when inserting row = yes
- change the deleting rules as you want them to be
- Validate your mapping. If the green light is shown, the settings in field properties are suitable for merge.
Hope this is what you wanted to get. I think this kind of solution works fine. Trigger in the table that holds and where one inserts millions of rows sounds scary...
Regards,
jk
Added text: sorry about false alarm. I think that was what you did. The solution above steals the nextvals from sequence. Perhaps no-native-english-reader should be more careful when reading questions ;-)
Edited by: jkoski on 5.11.2008 1:30

Tabular form loses data on validation check and new row

When you add new rows inside a tabular form and you have a validation which troughs out an error then all data inside the new rows are lost.
Is there any workaround available?
Tobias
Edited by: Tobias Arnhold on Jun 29, 2012 12:48 PM
I forgot to tell:
Current version of APEX 4.0.2
I also get this firebug error: uncaught exception: Syntax error, unrecognized expression: #
Somebody else had this issue before too: APEX 4.0 Tabular Form - Javascript error due to validation
Is there any workaround available?

Yeah, you cannot validate on tabular forms so you pretty much have to find work-arounds in order to validate your information. When you create an LOV you can create it with a dynamic query which is the basis for your select list. You can just modify the query in the dynamic query to include a where clause. The where clause could then just state 'where EMP_ID2 <> EMP_ID1'. That way your select list for each row should not have matching values between EMP_ID1 and EMP_ID2. APEX can create the dynamic query for you, you just select the columns you want to base the LOV on, then modify the query after.

While creating a new row in table,the total data present in table is coming

Hi,
From search page,i click add button,it goes to next transaction page.In transaction page i drag and drop one VO in table and in form also.But in that transaction page,The table is coming with data and a new row is also able to insert.But i don't want the previous data whatever present in table in create a new row time.Please give me the solution.
Thanks in advance
Sravanthi

Not sure I understand what you are trying to do.
If you have a table and a form based on the same data on one page you see the already existing data in the table. If you don't want to see the existing data in the table while entering a new row, the simplest solution would be to
a) hide the table after the use hits create new row or
b) navigate to an other page which only shows the form
Timo

Creation of new Row in Tree Table

We are creating a new row using CreateListener which is written in Bean, after creating the row, we are adding it to the iterator and the new row is not getting highlighted and focus is not in new row in the table by default. It takes an click to make it editable. 'setActiveRowKey()' method didnot help here which is used in the af:table component to achieve the same.
Any pointers regarding this issue would be helpful..
Thanks,
Shruthi

Hi Max:
According to what you described, it's really wierd. An ADF table is Surrounded by a panelCollection or not doesn't matter in terms of CreateInsert operations, I think. Also each step you said OK doesn't mean that step is 100% problem free towards your final goal. For example, when you drag and drop and ADF table onto a JSF page, you forget to turn on 'row selection', it will be OK, you won't get any error message, but later on when you find that you need to turn it back on, you have to go back to JSF page source, to manually added codes to do so.
The simpliest solution and quickest one is to reinitiate a clean ADF project and do it all over again. It's simple straightforward in my view. Probably don't use PanelCollection first, just drop your ADF table on a form, or af:panelForm, but make sure your table and 'CreateInsert' button is surrounded by a form, otherwise, when you click on 'CreateInsert', nothing will happen. When everything works, then probably back it up and replace your form or af:panelForm with panelCollection. See how it goes.
Thanks,
Alex

New rows become deleted from snapshot sites after refresh

Hi buddy
I am facing problem in snapshot at snapshot sites.
I have oracle 8.0.5 4 database server machines.
all servers machines have O.S windows 2000 advance server
all servers machine have same oracle version ( 8.0.5 ).
there is Site A ( Master site ) site B ( snapshot site ) Site C ( snapshot site).
snapshot has been created at all snapshots sites ( B,C and at D)
snapshot log against each table are also present at master site ( Site A )
refresh group is present at snapshot site.
these are working since feb-2002 successfully. now problem occur in these sites if some miner issues comes then it has been resolved successfully.
Replication parameter in init.ora all all sites are as follows
global_names = true
job_queue_processes = 2
job_queue_interval = 60
job_queue_keep_connections = false
distributed_lock_timeout = 60
distributed_transactions = 16
open_links = 4
snapshot_refresh_interval = 60
snapshot_refresh_keep_connections=false
snapshot_refresh_processes = 2
few days ago one problem occurs in master site A. it become crashed. we did its recovery from previous night backup ( cold backup).
Now all branches are working. but my current problem is that we have 20 tables in replication.It is a snapshot replication old version of materialized view.
when site B start refresh procedure then it show message procedure successfully completed.
it show no error message.
but when we check no of rows at snapshot site ( site b )
all new rows which were inserted at snapshot ( site b ) after previous refresh has been deleted.
mean all data which is inserted after previous refresh command has been finished. but data which is inserted at master site is present at snapshot site after refresh.
this problem is present at all the snapshot sites ( site B, Site C and site D).
database link is also present from master to snapshot site anf from snapshot to master. but problem is still suspended.
i have checked at all snapshot site and master site there is no invalid procedure or package.
there is no error message in alert file at all site.
if any body has its solution kindly told me.
thanks in advance
Abdul Hameed
[email protected]

This is still going on when the page fails the call to getCurrentRow().refresh(Row.REFRESH_REMOVE_NEW_ROWS) goes out to lunch and stops processing for the rest of the function. I tried adding a try catch around it but nothing is caught and the function still fails.
getSiteMealLogsV().getCurrentRow().refresh(Row.REFRESH_REMOVE_NEW_ROWS);
---Stops working here -----
getSiteMealLogsV().clearCache();
getDBTransaction().commit();
Jim

I can't insert new row in database when there is a secondary key.

hi experts. I am using Jdeveloper since a while. I would like to know If there is a way to insert a new row with secondary key attribute in database. As example if we have a sessionEJBLocal data control can't we add new row by using single selection choice item for secondary key attributes? I tried to use single selection even jdbc with sql queries in a managed bean but nothing. Can you help me please?

would this solve your problem
http://kohlivikram.blogspot.com/2008/10/add-new-row-in-adf-table-on-button.html

JTable checkboxes doesn't retain their selection when a new row is added!!

HI,
My gui has the JTable component which has 5 columns. out of which 4 columns are checkboxes. whenever i select an item from the Jlist and click on the add button it will add a new row in JTable.
but the problem is whenever a new row is added to the table. the previously selected checkboxes of previous rows are being deselected. But i want to retain the selection of my previous rows even when a new row is added. please help me how to achieve this..i am posting my JTable code here:
class FunctionTableModel extends AbstractTableModel{
       /** The instances who's attribute structure we are reporting */
    //protected InitModel m_init;
    protected String func_element;
    protected int counter;
    //protected String[] func_array;
    protected Vector func_vector;
    /** The flag for whether the instance will be included */
    protected boolean [] m_Sum;
    protected boolean [] m_Min;
    protected boolean [] m_Avg;
    protected boolean [] m_Max;
    protected boolean [] m_SD;
     * Creates the tablemodel with the given set of instances.
     * @param instances the initial set of Instances
    public FunctionTableModel() {
      counter =0;
         func_vector = new Vector();
     public FunctionTableModel(Vector vec) {
        func_vector = vec;
    public Vector getDataVector(){
        return func_vector;
     * Sets the tablemodel to look at a new set of instances.
     * @param instances the new set of Instances.
    public void setElement(Vector vec) {
           for(int i=0;i<vec.size();i++){
        func_vector.add(vec.elementAt(i));
        counter++;
      fireTableDataChanged();
      m_Sum = new boolean [counter];
      m_Min = new boolean[counter];
      m_Avg = new boolean[counter];
      m_Max = new boolean[counter];
      m_SD = new boolean[counter];
     * Gets the number of attributes.
     * @return the number of attributes.
    public int getRowCount() {
           return func_vector.size();
     * Gets the number of columns: 3
     * @return 3
    public int getColumnCount() {
      return 6;
     * Gets a table cell
     * @param row the row index
     * @param column the column index
     * @return the value at row, column
    public Object getValueAt(int row, int column) {
      switch (column) {
      case 0:
        return func_vector.elementAt(row);
      case 1:
        return new Boolean(m_Sum[row]);
      case 2:
        return new Boolean(m_Min[row]);
      case 3:
        return new Boolean(m_Avg[row]);
      case 4:
        return new Boolean(m_Max[row]);
      case 5:
        return new Boolean(m_SD[row]);
      default:
        return null;
    public void removeAll(){
        func_vector.removeAllElements();
        fireTableDataChanged();
     * Gets the name for a column.
     * @param column the column index.
     * @return the name of the column.
    public String getColumnName(int column) {
      switch (column) {
      case 0:
        return new String("Function Selected");
      case 1:
        return new String("Sum");
      case 2:
        return new String("Min");
      case 3:
        return new String("Avg");
      case 4:
        return new String("Max");
      case 5:
        return new String("SD");
      default:
     return null;
     * Sets the value at a cell.
     * @param value the new value.
     * @param row the row index.
     * @param col the column index.
    public void setValueAt(Object value, int row, int col) {
      if(col == 0){
        counter++;
        func_vector.add(counter,value.toString());
      if (col == 1)
        m_Sum[row] = ((Boolean) value).booleanValue();
      if (col == 2)
        m_Min[row] = ((Boolean) value).booleanValue();
      if (col == 3)
        m_Avg[row] = ((Boolean) value).booleanValue();
      if (col == 4)
        m_Max[row] = ((Boolean) value).booleanValue();
      if (col == 5)
        m_SD[row] = ((Boolean) value).booleanValue();
     * Gets the class of elements in a column.
     * @param col the column index.
     * @return the class of elements in the column.
    public Class getColumnClass(int col) {
         return getValueAt(0, col).getClass();
     * Returns true if the column is the "selected" column.
     * @param row ignored
     * @param col the column index.
     * @return true if col == 1.
    public boolean isCellEditable(int row, int col) {
      if (col >= 1) {
         return true;
      return false;
    public void removeRow(int row){
        if(row<=func_vector.size()){
                      func_vector.removeElementAt(row);
            counter--;
        fireTableDataChanged();
    }

hi parvathi,
i have made changes to my previous code and here's the code:
class FunctionTableModel extends DefaultTableModel{
       /** The instances who's attribute structure we are reporting */
    //protected InitModel m_init;
    protected String func_element;
    protected int counter;
    protected int counter1;
    //protected String[] func_array;
    protected Vector func_vector;
    /** The flag for whether the instance will be included */
    protected boolean [] m_Sum;
    protected boolean [] m_Min;
    protected boolean [] m_Avg;
    protected boolean [] m_Max;
    protected boolean [] m_SD;
    //protected Vector m_Sum1;
    //protected Vector m_Min1;
    //protected Vector m_Avg1;
    //protected Vector m_Max1;
    //protected Vector m_SD1;
     * Creates the tablemodel with the given set of instances.
     * @param instances the initial set of Instances
    public FunctionTableModel() {
        System.out.println("entered the constr");
      counter =0;
      //counter1=0;
      //m_Sum1 = new Vector();
      //m_Min1 = new Vector();
      //m_Avg1 = new Vector();
      //m_Max1 = new Vector();
      //m_SD1 = new Vector();
      //func_array = new String[];
      func_vector = new Vector();
     public FunctionTableModel(Vector vec) {
        func_vector = vec;
        //setElement(func_vector);
    public Vector getDataVector(){
        return func_vector;
     * Sets the tablemodel to look at a new set of instances.
     * @param instances the new set of Instances.
    public void addRow(Vector vec) {
      //counter++;
      //func_element = ele;
      //System.out.println("FunctionTableModel- setElement() method");
      for(int i=0;i<vec.size();i++){
        func_vector.add(vec.elementAt(i));
        counter++;
       //System.out.println("counter ="+counter+new boolean[counter]);
        //m_Sum1 = m_Sum;
        //m_Min1 = m_Min;
        //m_Avg1 = m_Avg;
        //m_Max1 = m_Max;
        //m_SD1 = m_SD;
        //m_Sum = new boolean[counter];
        //System.out.println("at setElement");
        m_Sum = new boolean[counter];
        //System.out.println(counter);
        m_Min = new boolean[counter];
        //m_Min;
        m_Avg = new boolean[counter];
        //m_Avg1 = m_Avg;
        m_Max = new boolean[counter];
        //m_Max1 = m_Max;
        m_SD = new boolean[counter];
        //m_SD1 = m_SD;
        //counter1++;
      //func_array[counter]=ele;
      //func_vector.add(counter,ele);
      fireTableDataChanged();
     * Gets the number of attributes.
     * @return the number of attributes.
    //public int getRowCount() {
      //System.out.println("FunctionTableModel- getRowCount() method");
      //return func_vector.size();
     * Gets the number of columns: 3
     * @return 3
    public int getColumnCount() {
      return 6;
     * Gets a table cell
     * @param row the row index
     * @param column the column index
     * @return the value at row, column
    public Object getValueAt(int row, int column) {
      switch (column) {
      case 0:
        return func_vector.elementAt(row);
      case 1:{
        //System.out.println("in case 1");
        //Boolean m_Sum_Value = new Boolean(m_Sum[row]);
        //System.out.println("m_Sum_Value:"+m_Sum_Value.booleanValue());
        return new Boolean(m_Sum[row]);
        //m_Sum1.add(m_Sum_Value);
        //return m_Sum_Value;
      case 2:
        return new Boolean(m_Min[row]);
      case 3:
        return new Boolean(m_Avg[row]);
      case 4:
        return new Boolean(m_Max[row]);
      case 5:
        return new Boolean(m_SD[row]);
      default:
        return null;
    public void removeAll(){
        func_vector.removeAllElements();
        //m_Sum1.removeAllElements();
        fireTableDataChanged();
     * Gets the name for a column.
     * @param column the column index.
     * @return the name of the column.
    public String getColumnName(int column) {
      switch (column) {
      case 0:
        return new String("Function Selected");
      case 1:
        return new String("Sum");
      case 2:
        return new String("Min");
      case 3:
        return new String("Avg");
      case 4:
        return new String("Max");
      case 5:
        return new String("SD");
      default:
     return null;
     * Sets the value at a cell.
     * @param value the new value.
     * @param row the row index.
     * @param col the column index.
    public void setValueAt(Object value, int row, int col) {
      if(col == 0){
        counter++;
        func_vector.add(counter,value.toString());
      if (col == 1) {
        m_Sum[row] = ((Boolean) value).booleanValue();
        //System.out.println("m_Sum length "+m_Sum.length);
        //for(int i=0;i<=row;i++)
        //    System.out.println("m_Sum1 "+i+((Boolean)m_Sum1.elementAt(i)).booleanValue());
        //System.out.println("m_Sum1["+row+"] "+ ((Boolean)m_Sum1.elementAt(row)).booleanValue());
        //    System.out.println("m_Sum["+i+"] "+ m_Sum);
if (col == 2)
m_Min[row] = ((Boolean) value).booleanValue();
if (col == 3)
m_Avg[row] = ((Boolean) value).booleanValue();
if (col == 4)
m_Max[row] = ((Boolean) value).booleanValue();
if (col == 5)
m_SD[row] = ((Boolean) value).booleanValue();
* Gets the class of elements in a column.
* @param col the column index.
* @return the class of elements in the column.
public Class getColumnClass(int col) {
return getValueAt(0, col).getClass();
* Returns true if the column is the "selected" column.
* @param row ignored
* @param col the column index.
* @return true if col == 1.
public boolean isCellEditable(int row, int col) {
if (col >= 1) {
     return true;
return false;
public void removeRow(int row){
if(row<=func_vector.size()){
func_vector.removeElementAt(row);
counter--;
fireTableDataChanged();
previouslu i was using the setElement method. now i have replaced with the addRow method...
but anyways...the control is not going to any of these overridden methods...and none of the elements are added to the table. But i comment of all the addRow, getValueAt, getColumnClass methods...then it's adding rows to the table but with only the first column all the remaiing columns are just empty...
i am fed up with this...if you observe i have commented out somany lines...becoz i am trying to save my boolean array values into a vector..but that was also in vain...
i appreciate for ur help...
thanks
sri

How to apply the constraint ONLY to new rows

Hi, Gurus:
   I have one question as follows:
   We need to migrate a legacy system to a new production server. I am required to add two columns to every table in order to record who updates the row most recently through triggers, and I should apply not null constraint to the columns . However, since legacy system already has data for every table, and old data does not have value for the 2 new columns. If we apply the constraint, all of existing rows will raise exception. I wonder if there is possibility to apply the constraint ONLY to new rows to come in future.
Thanks.
Sam

   We need to migrate a legacy system to a new production server. I am required to add two columns to every table in order to record who updates the row most recently through triggers, and I should apply not null constraint to the columns .
The best suggestion I can give you is that you make sure management documents the name of the person that came up with that hair-brained requirement so they can be sufficiently punished in the future for the tremendous waste of human and database resources they caused for which they got virtually NOTHING in return.
I have seen many systems over the past 25+years that have added columns such as those: CREATED_DATE, CREATED_BY, MODIFIED_DATE, MODIFIED_BY.
I have yet to see even ONE system where that information is actually useful for any real purpose. Many systems have application/schema users and those users can modify the data. Also, any DBA can modify the data and many of them can connect as the schema owner to do that.
Many tables also get updated by other applications or bulk load processes and those processes use generic connections that can NOT be tied back to any particular system.
The net result is that those columns will be populated by user names that are utterly useless for any auditing purposes.
If a user is allowed to modify a table they are allowed to modify a table. If you want to track that you should implement a proper security strategy using Oracle's AUDIT functionality.
Cluttering up ALL, or even many, of your tables with such columns is a TERRIBLE idea. Worse is adding triggers that server no other purpose but capture useless infomation but, because they are PL/SQL cause performance impacts just aggravates the total impact.
It is certainly appropriate to be concerned about the security and auditability of your important data. But adding columns and triggers such as those proposed is NOT the proper solution to achieve that security.
Before your organization makes such an idiotic decision you should propose that the same steps be taken before adding that functionality that you should take before the addition of ANY MAJOR structural or application changes:
1. document the actual requirement
2. document and justify the business reasons for that requirement
3. perform testing that shows the impact of that requirement on the production system
4. determine the resource cost (people, storage, etc) of implementing that requirement
5. demonstrate how that information will actually be used EFFECTIVELY for some business purpose
As regards items #1 and #2 above the requirement should be stated in terms of the PROBLEM to be solved, not some preconceived notion of the solution that should be used.
Your org should also talk to other orgs or other depts in your same org that have used your proposed solution and find out how useful it has been for them. If you do this research you will likely find that it hasn't met their needs at all.
And in your own org there are likely some applications with tables that already have such columns. Has anyone there EVER used those columns and found them invaluable for identifying and resolving any actual problem?
If you can't use them and their data for some important process why add them to begin with?
IMHO it is a total waste of time and resources to add such columns to ALL of your tables. Any such approach to auditing or security should, at most, be limited to those tables with key data that needs to be protected and only then when you cannot implement the proper 'best practices' auditing.
A migration is difficult enough without adding useless additional requirements like those. You have FAR more important things you can do with the resources you have available:
1. Capture ALL DDL for the existing system into a version control system
2. Train your developers on using the version control system
3. Determining the proper configuration of the new server and system. It is almost a CERTAINTY that settings will get changed and performance will suffer even though you don't think you have changed anything at all.
4. Validating that the data has been migrated successfully. That can involve extensive querying and comparison to make sure data has not been altered during the migration. The process of validating a SINGLE TABLE is more difficult if the table structures are not the same. And they won't be if you add two columns to every table; every single query you do will have to specify the columns by name in order to EXCLUDE your two new columns.
5. Validating the performance of the app on the new system. There WILL BE problems where things don't work like they used to. You need to find those problems and fix them
6. Capturing the proper statistics after the data has been migrated and all of the indexes have been rebuilt.
7. Capturing the new execution plans to use a a baseline for when things go wrong in the future.
If it is worth doing it is worth doing right.

Forcing a new row to validate

Similar Messages

Maybe you are looking for