search

NewPath-Consulting / warm

Pro Reports for Wild Apricot is a Google Data Studio connector that helps Wild Apricot administrators understand your organization’s membership engagement, renewal rates, and demographics. Trend your revenue and get expense analyses. Whatever your question, enjoy all the organized data you need at your fingertips to make the business decisions want.
https://newpathconsulting.com/warm
GNU General Public License v3.0
6 stars 4 forks source link

Support custom fields for Contacts endpoint #7

Closed asirota closed 4 years ago

asirota commented 4 years ago

add support for custom fields to be added as dimensions to the current Members endpoint.

The connector should have a configuration checkbox to “Include custom fields” to the fixed schema when Members is selected. The default behaviour is on.

This may make it easier for people to just want to analyze the fixed schema fields or include the custom fields they have configured and the fixed schema fields together.

asirota commented 4 years ago

The current test environment for custom fields does not handle date fields correctly (eg Birthday)

asirota commented 4 years ago

(Resolved) Make sure the Contacts custom field functionality includes UserID and AccountID as implemented in the Contacts endpoint. Right now it is impossible to identify the primary key for these records.

asirota commented 4 years ago

(Resolved) In the configuration of the end points on WARM please place Contacts first and then Contacts (custom fields) right underneath them so they are together in the drop down.

asirota commented 4 years ago

There is always one extra null record being returned for the Contacts (custom fields) end point. It is always the last record.

asirota commented 4 years ago

Radio button with extra charge field not returning data, and should return a string value (not numeric as it does now) @stephenpoole can you look at this one to make sure this is working as intended, a radio button extra charge field called Membership Fee Based on Salary is setup in the sandbox on contacts

asirota commented 4 years ago

(Resolved) Please make the semantic type for User ID and Account ID to a number, not a string as it is now.

asirota commented 4 years ago

I'll reopen until this one until we ship v2.

asirota commented 4 years ago

@stephenpoole can you fix the issue with extra charge calculation fields. They currently load as null

Sample field on sandbox is called Beach Pass and is filled in for user 37415038. This is a numeric field that contains the number stored in the extra charge calculation.