Jim Garrison
My feedback
31 results found
-
6 votesJim Garrison
supported this idea
·
-
1 vote
Dmitry Smirnov
responded
There are 2 options:
1. If you need data immediately, then you may add a parameter $async=false to the initial query. With this flag API returns a list immediately. If your number of contacts is below 500 it is a reasonable option.
2 Another option is to do exactly what you do, but wait for several seconds between API calls.
No matter what option you prefer, I’d recommend using $select parameter to read only the fields you actually need. It will significantly improve performance.
Here is an example:
GET https://api.wildapricot.com/v2.2/Accounts/183112/Contacts/?$async=false&$select='First name’,‘Last name’,‘Renewal due’
An error occurred while saving the comment -
2 votes
An error occurred while saving the comment Jim Garrison
commented
Agreed, not having a sort by ID means I have to load the entire list of contacts into memory, instead of being able to stream them and do a merge.
Jim Garrison
supported this idea
·
-
2 votesJim Garrison
shared this idea
·
-
3 votesJim Garrison
shared this idea
·
-
3 votesJim Garrison
supported this idea
·
-
1 voteJim Garrison
shared this idea
·
-
4 votesJim Garrison
supported this idea
·
-
6 votesJim Garrison
supported this idea
·
-
6 votesJim Garrison
supported this idea
·
-
14 votesJim Garrison
supported this idea
·
-
73 votesJim Garrison
supported this idea
·
-
9 votesJim Garrison
supported this idea
·
-
26 votesJim Garrison
supported this idea
·
-
2 votesJim Garrison
shared this idea
·
-
2 votesJim Garrison
shared this idea
·
-
1 voteJim Garrison
shared this idea
·
-
6 votes
An error occurred while saving the comment Jim Garrison
commented
I've just realized that there is a quick workaround for this that I actually found years ago and forgot about :-(
All we have to do is use time-span overlap-finding trick, using the overall event's start and end dates, assuming that the event's dates encompass all session dates.
Given a filter range of dates X..Y, write the filter as
EndDate ge X and StartDate le Y
This returns all events that overlap the filter range, greatly reducing the size of the result set. Then all you have to do is select only the zero or more sessions that are within the filter range.
Jim Garrison
shared this idea
·
-
14 votesJim Garrison
supported this idea
·
-
213 votes
Hello everyone,
I've been working on this idea for a while, and most of you have described the same trap. You need a volunteer to run one or several events, and the only way to let them is to hand over your whole contact database and your finances. But there are different events and different needs. So I'd like to test the shape with you before we build it.
The idea is to maintain the current role of Event Manager, which currently grants access to all events. However, you can also limit this access and assign the person to specific events by choosing from one of three levels of access:
- Check-in assistant - welcome people at the door, handle walk-ins. Sees their assigned events and who's registered. Checks people in, signs up whoever turns up, takes payment at the door. Cannot edit the event or its registrations.
- Registration manager -…
Jim Garrison
supported this idea
·
An error occurred while saving the comment Jim Garrison
commented
We have a use case where it is necessary, for certain events and ticket types, for the list of registrants to be always visible to one or more people who are designated as event leaders. This is defeated by the option presented to members at registration time to remain anonymous.
There would be two ways of doing this:
1) For every event, the option to designate one or more members as "Event Leader", with the ability to view the registrant list regardless of a registrant's choice to remain anonymous. Currently WA provides no mechanism to designate an Event Leader.
2) Provide an option on an event's ticket type to prevent anonymous registration.
Option (1) would be more general and useful, but would probably require a lot more work as it's a significant database schema change. Option (2) seems it would be easier to accomplish.
This seems to be a known bug if the results of a previous instance of the same query are still cached on the server. The answer from WA says to wait a few seconds, but I've seen it take several minutes. I've filed a bug report. Also $select doesn't seem to do anything, for me it always returns all fields, and the last-modified date doesn't capture all modifications so we ended up having to scrape the entire contact list daily to catch updates reliably.