07-14-2016 03:29 PM
This issue popped up fairly regularly in our previous version of Act (Act 11) and also does so in the current version, Act Pro 18. Just a continuing glitch in the software, I'm assuming? I'm running Act! Pro Version 188.8.131.52, Update 3.
I'll be working with a contact record, could be a new record or an existing one. Then when I click Add/Remove Groups under the Groups/Companies tab, I'll get the pop up window of groups which I can select and add. However, I'm now working with the contact record I had worked with prior to the current contact. I have to hit Cancel, Back, Forward and I'm brought to the correct contact.
It doesn't happen every time but often enough to be a nuisance.
Thanks for any suggestions!
07-18-2016 03:29 AM
07-22-2016 07:15 AM
We are running Act! Pro Version 184.108.40.206 and have consistently had this same issue since we had upgraded to v16. I found one post on this forum that discussed saving the contact before entering a note as a potential remedy, but I found that did not work. Are there any fixes for this problem? It appears it has lingered for years from what I've read.
07-22-2016 10:39 AM
It has happened if I'm creating a new contact or editing an existing one. What seems to trigger the unintended change of contact is clicking the Add/Remove Groups spot under the Groups tab. It also happens from time to time when I click Cltr + N or [Note] at the top of the screen in order to add a new note. There's a split second where I see the screen jump to the wrong contact. It's as if Act! begins adding the info to the current contact but then hiccups and reverts to the previous contact.
When this issue popped up recently while creating a new contact, I was doing pretty standard adding of info. I was tabbing between fields ending with email address, skipped adding a website, added ID/Status then I clicked the Groups/Companies tab > Add/Remove Groups.
The Database Repair suggestion from another person on the forums here did not seem to solve the issue, Fyi.
07-26-2016 03:25 AM
We're aware that Act will briefly show you the last contact you were viewing when performing some actions, i.e adding the contact to a group. This happens if the contact was found though an active lookup.
If you perform a lookup for an existing contact, then create a new contact, after clicking add/remove groups on the new contact you've just created, you should see the dialog box below:
At this point, the contact displayed behind this dialog box will be the previously looked up contact. Clicking Yes should refresh the screen again and take you to the correct contact.
Are you experiencing different behaviour to this?
07-26-2016 06:29 AM
That is a different behavior than we are experiencing. In Act! Pro Version 220.127.116.11 if I:
1. Perform a lookup and view a contact in the lookup.
2. Create a new contact.
3. Go to add/remove group in the groups tab.
This causes the new contact to flip back to the last viewed contact. I do not get the pop up prompt below. The same happens if a new note is added to the new contact, it flips back to the previously viewed contact requiring users to navigate back to the blank new contact.
07-26-2016 12:03 PM
Sometimes I get that warning message, other times I don't. It doesn't seem to correspond to the issue at hand - whether or not I am reverted back to the previous contact.
As an aside, I don't care for that warning/confirmation message. I know whom I'm editing and if I want to keep editing that contact (i.e. by clicking add/remove groups) I don't need to be asked to confirm as much. If there's a way to turn it off, I'd love to know.
07-27-2016 06:37 AM
07-27-2016 06:46 AM
Should I just make a new topic for this even though the issue appears to be the same? For us the issue happens 100% of the time and I can outline the steps exactly if you like. I have yet to hear any ideas that solve the problem we are having with the contact switching.
07-27-2016 06:48 AM - edited 07-27-2016 06:50 AM
Please do post the steps you are taking so that we can run some tests to try and replicate the issue. Feel free to post them in this topic.
An explanation of your expected result and actual result, and any extra detail you could provide would be useful.