fiogf49gjkf0d Let's check this a different way:
Go into the User's Profile (on SLX Administrator).
Select the Sync Tab
Click on the "Accounts" button.
Click on the "Lookup" icon on the top section (do not enter any criteria.
Once you get the result, click on the "Statistics button".
The results will show:
Total Accounts
Subscribed (not including Forced)
Forced
Total Subscribed (Subscribed and Forced)
Not Subscribed but has access
Requested (accounts that will be sent)
Removed (accounts that will be removed)
That may show you were the accounts are coming from, but there are a couple of things that you could do:
a) Remove the Subscription Rules, clear the UserSubscription table for this user as previously shown by Adam.
b) Re-Add the Subscription Rules
c) Add an UnSubscription rule that has the opposite criteria of your subscription rule ( == This may just be your workaround ==)
From what I recall, when SLX creates the Remote Database, it takes all those IDs from the Blob on the User Subscription table and then adds those records into the Account Table.
So, if you are ending up with 5000 rows, that may be the explanation for it.
On the other hand, and just going out on a limb, I would check your group definition.
For starters, I would create a new group, only place the Account.Account field on it, remove all conditions, apply the Distinct Checkbox, use the "Show SQL" to make sure no extra tables are being joined and then get your Account Count. It is always possible that some extraneous condition has been added to the group that is making it show duplicates, thus increasing your Count.
|