Adding payment_scheme_id custom field to "Payment Plan extra attributes" custom group, so we can use it to link a recurring contribution to a payment scheme.
Technical Details
The initial plan was to create new entity with the following:
With API v3 and API v4 support to be able to do all the CRUD operations on this entity.
But I found that we already have a custom group called "Payment Plan extra attributes" on the payment plan, so I found that it is easier and probably better to just add new field to it instead of creating new entity.
Also in general having API v3 support is not that important, and that we can just use API v4, which allows us to update or retrieve the value of this field using its name (unlike V3 that requires the custom field id, which results in more complicated queries), thus saving us from creating new API:
Overview
Adding
payment_scheme_idcustom field to "Payment Plan extra attributes" custom group, so we can use it to link a recurring contribution to a payment scheme.Technical Details
The initial plan was to create new entity with the following:
But I found that we already have a custom group called "Payment Plan extra attributes" on the payment plan, so I found that it is easier and probably better to just add new field to it instead of creating new entity.
Also in general having API v3 support is not that important, and that we can just use API v4, which allows us to update or retrieve the value of this field using its name (unlike V3 that requires the custom field id, which results in more complicated queries), thus saving us from creating new API: