Issue: Queries in Queue and NetCommunity no longer work

Jim summers

BUG:  

If you use the Admin Queue  on a query in Raiser's Edge, then if you use that query in a list in NetCommunity the record count will always be zero in NetCommunity.  



This remains true even if you take the query out of the queue.  There is no indication on the list that it was "once queued, and so now won't work in NetCommunity". 



WORKAROUND:

So far the only solution is to create a new copy of the query, and use the new query in a new list in NetCommunity. 



SOLUTION:

Queues turn Dynamic queries into Static Queries.  Update NetCommunity to point to a static queue.

Greg Milton

Hi Jim,


Thanks for bringing this up.  NetCommunity should be able to use dynamic and static constituent queries from The Raiser's Edge for email lists in NetCommunity.

It does look like something happens to a dynamic query when it is added to a queue after the first time is refreshed using the queue.  In my testing I was able to see the same thing-- a refreshed list in NetCommunity with 0 recipients.  


A dynamic-turned-static constituent query should still work in NetCommunity and our product development group will have to evaluate this issue.


In my testing I found an easier alternative solution for the mean time.  After the first time the query is refreshed by the queue, do this one time:

1. Open the affected constituent query,
2. Click Run Query (Green exclamation mark).
3. Click Save.

The query, after being manually refreshed once, seems to behave normally.  I was able to make changes to constituent records, run the queue (refreshing the query), and the changes were reflected in NetCommunity after the email list refreshed.  Hope this helps in the mean time.


Thanks!

Greg