Sage ACT 2013 SP1 Static Group Members removed from Remote - Issue not fixed

[CherieButtsworth]

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...

http://www.linkedin.com/groupAnswers?viewQuestionAndAnswers=&discussionID=207634935&gid=49896&commen...

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?

[CherieButtsworth]

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

[gmartin]

Cherie,
Thank you for the information. We have determined that a 2013 v15.0 installation updated with SP1, will still need the solution in the article applied. If 2013 is installed with the full v15.1 installation files, the solution in the article is not needed.

Article 30558 has been updated with this information. If you have a different experience, please let us know.

[CherieButtsworth]

Thanks for the update Greg!