Hi

I have an upgraded installation to 4.0 where new fields created on accounts
won't save data. When I change data in any new field and hit save it blanks
out the field.
When I type somehting in the old fields on the form these fields save fine.

What could this be ?

Jack

It sounds like a javascript issue with the form. I would check to see if any
javascript is running against the form (Onload, Onchange, etc.)

Regards

"CRM consultant" wrote:

No there isn't any scripts but see what I found out last night

I have a customer who has moved CRM 3.0 to new server by them self and I
have converted it to CRM 4.0
Now they have made some custom fields and we are able to save data in these
fields on new accounts but not on the old ones.
We can save data in the old fields.
I then took a look at the database and there is only fields in the
accountextensionsbase since after they moved the database.
How can I fix this ? They can merge each to a new customer but that would
take a long time.

Can I do a insert into with data from the Account table or is there another
solution ?

ok, that is quite different from what I thought you were asking.

It looks like something didn't go well with the redeployment of the CRM 3
server based on the following statement "I then took a look at the database
and there is only fields in the accountextensionsbase since after they moved
the database". Is it possible that this client did not follow the
re-deployment guide? When you upgraded to CRM 4, did you attach to an
existing database?

Direct inserts into the database is not supported. Additionally, this might
not be the only issue that this client has, as other issues may not have been
discovered yet. If it were me, I would re-deploy the CRM 3 server again and
go through the upgrade process but that is your choice.

Thank you

"CRM consultant" wrote:

I'm affraid the data was already missing when they moved the database to new
domain/server. They probably did this with migration tool and not with a
backup of the database, else everything would have been there.
I have looked at other tables and they seem ok, it's not the upgrade to 4.0
that made the problem since there are data in the accountextensionbase 2
months before the upgrade, but they first discover the problem now because
they haven't added custom fields before now.

Wouldnt it be wise to create new database exporting the customisations (so it
creates those fields), and reimporting the export data!
--
http://halo9.co.uk/blog


"CRM consultant" wrote: