You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was just made aware by our fundraisers that there is an option in the TwingleMANAGER to define another product for "additional donation" at the very bottom of the page for the donation shop products.
Unfortunately, Twingle does not return this product together with the other products from the project API under the endpoint products. However, the "additional donation" is listed in the products array in the call to the CiviCRM TwingleAPI. And unfortunately, it is named like the option set in the TwingleMANAGER.
It is annoying that the "additional donation" does not behave like the "top-up donation", which is also available. The latter is not listed in the products array when it is sent to CiviCRM, but only appears as the difference between the "amount" of the donation and the total of the individual products. As a result, it can be easily determined and created as a line item with a donation type that can be selected in the TwingleAPI profile settings.
Since the name of the "additional donation" can be freely chosen, a corresponding option in the TwingleAPI profile would have to be a text field in which you would enter the same name that you chose in the TwingleMANAGER. I find this somewhat clumsy. The alternative seems to be to rely on the “internal_id” always being transmitted as null in contrast to the other products, but should we rely on that?
The text was updated successfully, but these errors were encountered:
I was just made aware by our fundraisers that there is an option in the TwingleMANAGER to define another product for "additional donation" at the very bottom of the page for the donation shop products.
Unfortunately, Twingle does not return this product together with the other products from the
project
API under the endpointproducts
. However, the "additional donation" is listed in the products array in the call to the CiviCRM TwingleAPI. And unfortunately, it is named like the option set in the TwingleMANAGER.It is annoying that the "additional donation" does not behave like the "top-up donation", which is also available. The latter is not listed in the products array when it is sent to CiviCRM, but only appears as the difference between the "amount" of the donation and the total of the individual products. As a result, it can be easily determined and created as a line item with a donation type that can be selected in the TwingleAPI profile settings.
Since the name of the "additional donation" can be freely chosen, a corresponding option in the TwingleAPI profile would have to be a text field in which you would enter the same name that you chose in the TwingleMANAGER. I find this somewhat clumsy. The alternative seems to be to rely on the “internal_id” always being transmitted as
null
in contrast to the other products, but should we rely on that?The text was updated successfully, but these errors were encountered: