Problem With Customized Accounts

[JustinGould]

I'm in a pretty big jam and I need some help. My old Sugar 6.0.3 installtion went belly up somehow, and after spending 2 man weeks trying to get it running again, I was unable to.

I installed a fresh copy of 6.1.3 and got that up and running okay. Using SSIS in SQL 2005, I was able to bring over my users and contacts from the old installation without any real problems.

Where I'm hitting a problem is in bringing over my cutomized accounts data. I did not have an export of the customizations from the old installation available. So, I applied the exact same customizations to the new installation's accounts module that were on the old one. Same fields, same field types, etc. I then used SSIS to transfer the data from the old to the new installation successfully (all fields were accounted for, nothing missing in the new that was in the old).

Now, I can pull up my accounts module and see all the accounts listed out in ListView. When I try to bring them up in EditView, I get:

"Error retrieving record. This record may be deleted or you may not be authorized to view it.

If I try to click the pencil next to the account record to edit it, it instead takes me to Create.

A SQL profiler trace of database activity shows:

SELECT TOP 1 accounts.*,accounts_cstm.* FROM accounts LEFT JOIN accounts_cstm ON accounts.id = accounts_cstm.id_c WHERE accounts.id = N'2a31fa82-eb59-ac95-31fd-4d50504dc489' AND accounts.deleted=0

Which returns exactly 1 row as it should. The next thing though:

SELECT ea.*, ear.* FROM email_addresses ea
LEFT JOIN email_addr_bean_rel ear ON ea.id = ear.email_address_id
WHERE ear.bean_module = N'Accounts'
AND ear.bean_id = ''
AND ear.deleted = 0
ORDER BY ear.reply_to_address, ear.primary_address DESC

Is a bit odd. ear.bean_id = '' ??

PLEASE, I really need some help here. We spent months entering data from paper into this system and now can't access or manipulate it. It's right there in the database, but I can't touch it... very frustrating.

Please, any help anyone could provide me would be immensely appreciated.

Thanks,
Justin Gould

[Angel]

Does the same thing happen for newly entered Accounts?

Were you able to edit the records prior to copying over to applying the customizations?

How were the ID values in the accounts table generated?

[JustinGould]

Does the same thing happen for newly entered Accounts?

Were you able to edit the records prior to copying over to applying the customizations?

How were the ID values in the accounts table generated?

Newly entered Accounts behave properly. They show up, can be viewed in DetailView, can be edited, etc.

I applied the customizations before brining the account records over. I had to do that before I could bring the Accounts_Cstm table over.

The ID values for the Accounts and Accounts_cstm records are the same ones from the old system. I brought the iDs over to preserve the Accounts->Accounts_Cstm relationship, and the parent/child relationships between accounts.

The tables I copied, BTW: accounts, accounts_cstm, accounts_contacts, contacts, contacts_users, email_addr_bean_rel, email_addresses, users.

Contacts do show up fine, can be edited, added, deleted, etc. Users that were brought over can log in fine.

Thanks for the help!

[Angel]

Hmm...

Any way that you could provide a view of a non-working and a working record from the various tables?

[JustinGould]

Hmm...

Any way that you could provide a view of a non-working and a working record from the various tables?

No need, that set me off in the right direction. Table by table, I compared the working account with the non-working one and found the problem. There was a float type field in accounts_cstm that was misbehaving. When I nulled it out, the record would work fine, but when I put a value in it, it wouldn't let me view/edit the record again.

I removed the float type field, recreated it as a text type field and repopulated it. Everything's up and running again!

Thanks for your time and for nudging me off in the right direction!!

Justin