09-08-2009 01:19 PM
We're running into an odd bug, here. Running ACT 2009, updated to the latest version, with a Publisher-Subscriber setup. (~8000 records in the DB, if that matters).
When we try to duplicate a record in a Subscriber database, it displays the new record, with the Primary field information showing. You can add new stuff, but the record doesn't really exist - as soon as you move to a new record, the (intended) duplicate disappears forever. [No effect on the orginal record.] Hitting save gives you a "That contact no longer exists in the database" message.
Duplicate Checking is turned off in the Publisher database; it's grayed out in the subscriber database.
Any suggestions for what we should look at next?
09-09-2009 06:56 AM
09-09-2009 08:49 AM
09-10-2009 07:33 AM
First check within the demo database to ensure its database specific. If its determined to be database specific, you will have to narrow it down to the which field(s) is causing the issue. You can recreate the field if its not a system field. You will want to copy the information from that field to another fieild before deleting it though. Also create a backup of the database prior to deleting anything.
If its a system field (you can verify in Define Fields under the Details section) an option could be to create an empty copy of the database and see if you create a duplicate contact. If you can, you will have to import the existing database into the empty copy and recreate the remotes.
Another option would be to contact database services.
I suggest you giving a call into support to have a support agent look into the issue to verify that its a corrupted field.