Error in adding values into inline sub-data grid

himanshu

Hi,

There is a master business object customer and sub details business object in one form, and in the sub details there are three fields one field is combo and another two fields are in number or text fields.

While when we try to fill the values of all fields, it gives an error message "unable to find the record. The record may have been deleted."

please take on priority.

previously it was working fine but after recent release or might be 1205 i found now that i cant able to add new sub data to the master form same which i was easily.

:cry:

himanshu

support if u say then i can send u the test bsv to invoke the same.

aware_support

Yes, please send us a bsv and explain how to reproduce the problem.

ab042

I can confirm a problem exist in the latest build. In our case we have a very simple PEER relationship between a Contact biz object and RegularUser biz object.

It is just about impossible to add a record to the link Regular User without getting an error and it doesn't appear to be just in-line editing.

As an example we have a reference element (Table) of the Regular User on a contact object. When we click on ADD NEW it brings up the RegUser and we can key and save it without issue. However, after it saves and returns to the Contact and we click SAVE is when the following error appears: "has been changed by another user. Please get the latest version of the data and try the operation again."

We also played with In-Line and same type of problem.

aware_support

We spend a lot of time trying to reproduce problems and half of the time it turns out to be a user error or misunderstanding.

So, if you want the problem to be solved in the most efficient and timely manner, PLEASE send us a BSV with the description of steps required to reproduce the problem. Some users do this and they can testify that this is the most efficient way of resolving issues for everyone involved.

tford

I have found support to be very responsive when you do as they describe. I usually create a small bsv that isolates the exact issue & send it to support. They are most often able to quickly identify and fix the problem with this help.

himanshu

test bsv sent to support

aware_support

We fixed the issue reported by himanshu. The fix will be in the next build.

ab042, please send your bsv, we cannot reproduce your problem - it is obviously different from himanshu's.

ab042

I sent a Sample BSV with instructions on how to re-create the error.

himanshu

ab042 would you show here also steps to reproduce.

ab042

This is a quick response but I think it should show the error:

Created a business object: Contact
with a few Attributes: Name / Phone / Notes
Add a new Attribute: LinkUsers
Type: RegularUser
Relation to RegularUser: PEER
Matching Attribute in RegularUser: CREATE LinkContact

On the CONTACT FORM be sure you have a TABLE OF ITEMS for the LinkUser attribute. So that when you bring up a contact form it has a list of users.

Create a NEW Contact

Click on ADD NEW to create a Linked Login
Type a Login Name
Type a Password
Click Created (FYI: The login record did get created in the database and shows without error)
Click Create

List Contacts via some query
Click on the contact you created above
Click on the ADD NEW to create another Linked Login
Type a Login Name
Type a Password
Click Created (FYI: The login record did get created in the database and shows without error)
Click Save (popup record change ERROR Shows)

aware_support

All issues should be fixed in build 1206

Sergej

Getting the same error

Unable to find the record. The record may have been deleted.

when I login in as guest and fill form Candidate that is intelligent BO. When I di the same as admin I dont get it. What could this error been related to?

tford

Sergej,

I don't see the connection between your question / situation and this thread. Seems like you would be better off starting a new thread with complete details of your particular issue.

Sergej

Didnt want to create new topic. The common is the error message, that is exactly the same so I suppose there can be a similar cause of error that support could know.