Connector Improvement: Recurly Connector - Additional Subscription Add-On attributes
Answered
There a several attributes that are critical to managing our business that aren't available using the current connector.
Specifically, we need more detail for Subscription Add-Ons. API documentation can be found here. In the fetch method for the Subscription object, there is an array object "add-ons" that can be expanded to view that object as well as the "add_on" child object. Both data sets are needed.
-
Official comment
Hello Kalani,
I trust this message finds you well. Thank you for taking the time to submit your feature request, and I appreciate your detailed explanation regarding the need for more information on Subscription Add-Ons.
I want to assure you that your request has been successfully added to our backlog, and our development team will prioritize its implementation in the near future. We recognize the significance of obtaining additional details for Subscription Add-Ons to better manage your business, and we are committed to delivering a solution that meets your requirements.
As we make progress on this feature, we will keep you informed and provide updates accordingly. If you have any further insights or feedback during this process, please don't hesitate to reach out.
Thank you once again for your valuable input. We look forward to delivering an improved connector that better aligns with your business needs.
Best regards,
Sandeep Preetam
Technical Product Owner -
We're hitting the same issue. Specifically, we need add_on.code, add_on.external_sku, and add_on.accounting_code from the nested add_on child object within the subscription add_ons array.
Our use case: we cannot fall back on line_item_history to derive the product code because invoices are not posted for failed or future subscriptions, making the nested add_on fields the only reliable way toi dentify the product across all subscription states.
Please sign in to leave a comment.
Comments
2 comments