The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
Getting an error called "Error saving: Unable to save "(0)" BusinessObject UID is undefined"
Posted: 31 Jul 08 11:51 PM
|
Hi,
I am trying add a new form "ContactPhone" with a new table "ContactPhone". this table has 1:M relation with "Contact" table. This new form will launched from a new tab with data grid in "Contact" form. Now i am able to add multiple phone numbers for each contact using this form and new table.
The problem is i am getting an error if i edit any field from contact table for eg: postal, workphone. and try to save it. It is giving an error "Error saving: Unable to save "(0)" BusinessObject UID is undefined". I am not understanding why this error is coming. Can anybody suggest me regarding this error.
Thanks in advance
Mallikarjun |
|
|
|
Re: Getting an error called "Error saving: Unable to save "(0)" BusinessObject UID is undefined"
Posted: 02 Aug 08 8:30 AM
|
I would look into the relationship between contact and contact phone. If you have established a relationship between these tables you may have inadvertenly caused the problem. 1 to many relationship are established through the grid and not really at the entity level. Take a look at things like Account->Contact and you will see that there is no relatioinship defined. Assuming from your error you have defined a relationship and your binding is requiring a ID to be specifically set. That being said take a look at BaseContact java class and see that there is code for paring the relationships. Also look at the presave to see how address is managed to ensure that the entity id is set correctly.
I hope this sets you in the right direction
Mark |
|
|
|
Re: Getting an error called "Error saving: Unable to save "(0)" BusinessObject UID is undefined"
Posted: 07 Apr 09 3:37 PM
|
I am receiving the error, "Error saving: Unable to save "(0)" when trying to add a new contact and I am wondering if whether you resolved your issue.
Some background and steps I've take so far to troubleshoot
Three 1:1 Account tables as well as a 1:1 Contact table have been added to the database.
The relationships are 1:1 between the contact tables and 1:1 for the account tables as defined in the tablerelationships.
There are also relationship as 1:1 between the Contact table and the three Account tables where the contact table is parent the acount extension tables are the child tables. (like the address and contact/account relationship is set up)
I looked at the Presave under the Contact Base and validated that the contactid is being generated as the entityid for the address table. The userid was also validated
There is no issue when editing the fields in the tabs that reference the new tables. The only issue is when adding a new contact or account.
Any insight regarding where to look to fix the issue or where to look to get more information on the error? Thanks! |
|
|
|
Re: Getting an error called "Error saving: Unable to save "(0)" BusinessObject UID is undefined"
Posted: 08 Apr 09 6:02 AM
|
Martin, I think I am missing something but how is the 3 account tables a 1:1 relationship with the contact table. Since they are already 1:1 with account (Expecting that the primary key is Account Id in your account extension tables). It sounds like a 1:Many relationship between contact and the account extension tables from what you are describing. Depending on how the relationship is setup you may have to specifically set the key properties in the presave event. The mobile will handle the true 1:1 as defined by a relationship but will not do one to many without some effort.
Mark |
|
|
|
Re: Getting an error called "Error saving: Unable to save "(0)" BusinessObject UID is undefined"
Posted: 08 Apr 09 9:38 AM
|
Thanks Mark, let me push my low articulation skills to the edge. I set up the relationship for the contact to the 3 account extension tables by linking on accountid. The reason I did that was to include some account information under the contact. Thinking a bit more about the the 1:1 relationship, I related it to for each single contact, there is a single account. That being may be true but it ignores that there are many contacts per single account. Stepping back and putting on my thinking cap, I see that it ends up being a many to one relationship.
Once I removed the relationships between the contact and the 3 account extension tables, I was able to add a contact. Woot!
Going through the code on the contact base presave appeared to have the correct key properties though to handle it. I'll try looking at it a bit more carefully and take some more time figuring out the best method of debuggin.
Martin |
|
|
|