Connector Improvement: Allow for required Subtables to be disabled
Answered
We had a client that had a huge amount of data in subtables associated to the connector Shopify > Order table.
This caused us to have a slower than normal sync time for the client and we had questions of how it would be billed over the life span of this connector to even know if we could actually support the customer contract.
It would be ideal for us to be able to disable any subtable associated to a parent table for this reason.
In the example we had with this client these tables being disabled would remove 99.4M rows:
(parent table customer):
- discount_allocation
- discount_application
- fulfillment
- fulfillment_order_line
- order_adjustment
- order_line
- order_line_refund
- order_note_attribute
- order_shipping_line
- order_shipping_tax_line
- order_url_tag
- tax_line
(parent table customer):
- customer_address
- customer_tag
- customer_tax_exemption- abandoned_checkout_line
(parent table abandoned_checkout):
- abandoned_checkout_shipping_line
- abandoned_checkout_tax_line
- abandoned_checkout_url_tag
-
Official comment
Hi Tony,
This is a really important improvement for delivering a better user experience. We are currently scoping this out and will keep you updated on our progress.
Thank you for your feedback!
Best,
Sandeep -
My company is also being impacted by this, and it would be great to have the ability to block child tables with a primary key that I don't need and just be able to include parent tables in general. But Shopify is the worst offender, as order_custom_attribute is my highest MAR usage in my project and I don't need it at all, but am forced to include it.
Please sign in to leave a comment.
Comments
2 comments