09-03-2012 05:34 AM
I've recently added about two hundred new opportunity fields to an ACT! 2010 database of which about thirty are yes/no fields.
When you tick some of the new yes/no fields they remained ticked when you look at other opportunity records. It is not all of the new yes/no fields just some of them. They are not 'Yes' in the database but just appear so when you view the record. All the other new fields appear fine.
I've run the check, repair and reindex database options from actdiag but this hasn't helped.
Wondering if anyone had seen this issue before and how they resolved it.
09-06-2012 07:37 AM
09-06-2012 08:13 AM
That doesn't help unfortunately.
I've had a look at the tables that the yes/no fields are stored in by running the Fields List to CSV report in Actdiag. Four custom opportunity tables have been created and the problem fields are in two of the tables. Yes/no fields in the other two tables are fine.
This might of course just be a coincidence.