wa
My feedback
11 results found
-
7 votes
An error occurred while saving the comment wa
supported this idea
·
-
33 votes
An error occurred while saving the comment wa
commented
You can reorder answers within a question. You should be able to reorder questions as well. The current UI feels very 1990's and is quite limited.
wa
supported this idea
·
-
1 votewa
shared this idea
·
-
2 votes
An error occurred while saving the comment wa
commented
The "payload" you show is several levels removed from the actual request URL that was generated. Clearly the generated URL is incorrect, but nobody can tell from what you've posted. Can you examine the actual HTTP request?
-
2 votes
An error occurred while saving the comment wa
commented
Based on my experience, you can use the batch API (.../contacts) with $filter=Id eq {contactId} and then specify the fields you want in $select. Try it in SwaggerHub (or Postman). At least then you have the ability to poll until the result is available.
-
2 votes
An error occurred while saving the comment wa
commented
Use
$filter=MembershipLevelId ne [desired level ID]
The level ID will be a number that you obtain from examining other query results or querying the Membership.Levels API. For example
$filter=MembershipLevelId ne 1125777
-
2 voteswa
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 wa
commented
How big is the expected dataset? How long do you wait between polling attempts? If the dataset is large it can take the web service some time to prepare the results. I've seen 20-30 seconds when requesting a complete list of 2400 contacts. If you are returning more than a few hundred objects, you may want to use $skip and $top to page through the results. The query is run only once and the results cached at the server based on the resultId.
In my application I wrote a simple front-end that exposes "run query" and "get next" methods (analogous to SQL query and resultset) that hides all the polling and paging from the client code.
-
2 votes
An error occurred while saving the comment wa
commented
Try
$filter='Member' ne 'true' AND 'Suspended member' ne 'true'
If that doesn't get you the desired results, how about
$filter='MembershipLevel' eq NULL
It's pretty easy to play with the API on SwaggerHub, or using Postman, so the best advice is to experiment until you find something that returns what you want. I prefer Postman since it deals with large results much better than SwaggerHub, which will slow down and crash with large datasets.
-
1 votewa
shared this idea
·
-
84 voteswa
supported this idea
·
All this would really need is the ability to grant "Limited Admin" for a set of pages to members of a group.