01-23-2013 10:59 PM
Hi guys
I'm not sure how many of you have come across this yet, or even noticed you have some group memebers missing, but I've had it at a clients and have also replicated it with my own database. So pretty sure I'm not alone...
The Following KB says the issue with static group members was a fix with the release of SP1
http://kb.sagesoftwareonline.com/app/answers/detail/a_id/32103
Static Group members removed from Group in remote databases
However, I've tested this in both ACT Pro and Premium 2013 (with and without SP1). If you create a new RDB in 2013 (with or without the SP) the static membership of Groups doesn't come across to the remote. Any groups with Dynamic membership are fine. It only seems to apply to the Static members.
Has anyone else had this issue?
01-28-2013 07:53 PM
Additionally, if you create a new group with static members in the main database (after the RDB has already been created) then that group and its contacts (static or otherwise) will come across on the next sync. So the issue only lies with groups and static members that are already in the database at the time you create the remote.
If you're experiencing any issues with static members and groups in your remote please refer to the following KB article for a temporary solution.
http://kb.sagesoftwareonline.com/app/answers/detail/a_id/30558
01-31-2013 08:46 AM
01-31-2013 12:10 PM
Thanks for the update Greg!