thelontx
commented
1 year ago Summarizing the variations that WA allow:
- Extra Charge Calculation
- Radio Button selection with Charge
- Multiple Choice selection with Charge NOTE: These types of fields may be used for memberships or for event registration invoices. The old logic depended on the "prefix" on the invoice line item (e.g. Extras), which is different between Memberships and Events. The new logic reads the name of the field/choice directly from the line regardless of whether it is Membership, Event, or Event Guest.
New QBW logic supports these variations of mappings:
- Extra Charge Calculation --> single QBWA mapping per field name only
- Radio Button selection with Charge --> single mapping per field name only (e.g. "T-shirt choice")
- Radio Button selection with Charge --> single mapping per field name and single selection combo (e.g. "T-shirt choice - Old Shirt" or "T-shirt choice - New Shirt")
- Multiple Choice selection with Charge --> single QBWA mapping per field name only
QBWA must read the configured EC mappings for a client and iterate through each, searching for a match on every invoice line item. For clients with many EC mappings and line items, this can increase the number of Make.com operations consumed.
TCM appears to be the first client that has used Extra Cost fields for Event Registrations. Current QBWA logic is not properly parsing the Invoice Line Items to find and use Extra Cost field mappings.
Background: QBWA parses the text of WA Invoice Line items, comparing the text to the expected format for a line using an Extra Cost Charge field. This has been successfully used for Memberships with Extra Cost fields.
Issue: The text format WA uses for Invoices with Extra Cost line items changes for different types of Invoices and different types of extra cost charge fields. This is compounded by Event Registrations with Guests where the Line Item for a Guest has an additional prefix identifying the Guest.
Solution: 1) Need to quantify all the variations of text on an Extra Cost Line item 2) Determine the best logic for deriving a correct mapping for all variation 3) deploy and test the logic
Potential impact: Increase in the number of operations consumed per invoice, especially when Extra Cost fields are used.
This issue has not yet been resolved for TCM.