Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
I've no idea.So I used [column_sale_id] which seems to follow the scheme xxxx, xxxxR2, xxxxR3, xxxxR4 and thus should generate a unique invoice number for each new recurring payment, Is that correct this way ?
I don't know what the intended behavior of sale_id is and I can't make any promises regarding the future.will you keep the sale_id R implementation in the future ?
No, that substitution isn't going to work there as you're confusing 2 completely different usages. The column substitutions are for CB Query Field only. Normal field substitutions will work in that parameter (e.g. [name]). If you want a value that CB Query Field outputs then you need to substitute in a query field that's outputting the value you're wanting.Are you sure about substitution in the invoice number ?
Please Log in or Create an account to join the conversation.
No, that substitution isn't going to work there as you're confusing 2 completely different usages. The column substitutions are for CB Query Field only. Normal field substitutions will work in that parameter (e.g. [name]). If you want a value that CB Query Field outputs then you need to substitute in a query field that's outputting the value you're wanting.
Please Log in or Create an account to join the conversation.
There isn't a way because the invoice you want does not exist. The list output by the solution I provided is an accurate payment history, but those recurring payments do not have a unique invoice as CBSubs does not generate baskets (which is an invoice in CBSubs) for recurring payments. For accounting/legal purposes the payment history should be satisfactory for the user until we can rewrite the recurring payment handling to generate baskets on each payment.So we need to find another way to display invoices with the needed data
Please Log in or Create an account to join the conversation.