search

NewPath-Consulting / quickbooks-for-wildapricot

QuickBooks for Wild Apricot - Never miss an entry and have peace of mind knowing your books are always up-to-date with accurate transactions. Reduce stress and errors with automated, categorized entries from Wild Apricot to your QuickBooks accounts.
https://newpathconsulting.com/waqm
Apache License 2.0
2 stars 1 forks source link

Support ability to insert common/membership fields into data stream #8

Closed asirota closed 3 years ago

asirota commented 3 years ago

Currently customer fields are limited to a small set of customer fields. Need to support all common/membership fields using the JSON bracketed notation already available from the Wild Apricot API. Useful when configuring customer information and potentially in other areas.

thelontx commented 3 years ago

I did research on this today. I developed a technique that allows me to abstract the Data Store configurations to use WA fields.
e.g. Have a field inside the Data Store Configuration where the Customer Name is specified. If the user enters the WA System Code 'FullName', the system returns the corresponding FirstName from WA. This is without hardcoding the FirstName field within the Integromat scenario.

Generally, it looks like the technique will work well, but may be practically limited by Operations to using 1 WA field abstraction per Data Store Config field. Unfortunately, I think there are several cases where more than 1 field will be desired. (e.g. First Name + Last Name; City + Province + Postal Code). In these cases, I'd need to iterate over the configuration for each field and replace the SystemCode definitions for each occurrence.

Perhaps we pursue this feature, but put some boundaries on it. e.g. only certain fields support more than 1 SystemCode - Customer Name, Billing Address kine 1 and line 5?

thelontx commented 3 years ago

This is ready to test as part of the QBO v5 roll-out.

Decisions and Approach used:

Provide a mechanism to define the field names used in each Wild Apricot instance for Name, contact fields, address fields, and Organization. Once configured, this is automatically used in the scenario in both QBO and QBD.

QBO: Do not allow additional configuration outside specifying the field names above. QBO allows invoice and other formats to be defined internal to QBO. Do not overwrite this capability.

QBD: Continue to allow customization of the Name and Billing Address. Expand the supported tokens as shown in documentation. Tokens rely on above field names being mapped properly.

asirota commented 3 years ago

See details on supported fields in the documentation.