QBWA uses the Make.com Data Store to configure mappings from Wild Apricot to Quickbooks. Only 1 row (record) is needed to correctly configure QBWA for all transaction types. Other records are backups or specific to separate tests.
Inside the Core Scenarios for each transaction, the first “module” inside the scenario lists the configuration “key” that corresponds to the appropriate record in the configuration Data Store. These screenshots show this key in a scenario and inside the Data Store. These must match exactly in order to use the desired configuration.
Recommendation: Before making QBWA configuration changes, use the Backup scenario to create a copy of the current configuration.
The Backup scenario creates a new record in the configuration Data Store with a new key and the phrase " (copy)" appended to the end of the Config Record Name. The Make.com Core scenarios will be unchanged and will still point to the previously used configuration key record.
- Open the Make.com Scenario “QBWA DS Record Backup”.
- Confirm the first module is using the correct “WA Config Record Name” from the Data Store record that you wish to copy.
- Click the “Run Once” button inside the Backup scenario.
- If successful, the record is copied and added to the Data Store with a new key. The “Config Record Name” field will copy the original value and add the suffix “ (copy)”. Also, the Config Last Updated date will be set to the current date.
- Changes can now be made to the original configuration record key.
- If needed, each Core scenarios can be changed to refer to different record keys (in the 1st module of each scenario). See the next section.
In most cases, this action is not required. Re-pointing scenarios to a different record in the Config Data Store is typically done when referring back to an old configuration record.
Steps:
- Open the QBWA Config Data Store.
- Identify the desired record that should be used for running the Make.com scenarios.
- Copy the key for that record.
- Go to the desired Core scenario and click to open.
- Navigate (drag the screen with mouse) so that you can see the first module to the left (titled Config Key).
- Click on the module to open its properties.
- Change the value in the Key field to match the key from the Config Data Store.
- Click OK.
- Click the Save icon on the bottom left of the scenario screen.
- Exit the Scenario edit mode.
- Repeat steps 4-10 for the other Core scenarios.
NOTE: The Config Key does not need to be set for the Transaction Loader scenarios (QBD or QBO). They read the config that was used in the Core scenario for processing.