Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Product Catalog 2.0 expected extracted tables via Stitch data #106

Open
charmaine-g opened this issue Feb 15, 2024 · 0 comments
Open

Product Catalog 2.0 expected extracted tables via Stitch data #106

charmaine-g opened this issue Feb 15, 2024 · 0 comments

Comments

@charmaine-g
Copy link

I originally asked Stitch support and they pointed me here. I'm a newbie user to both Chargebee and this integration so my apologies in advance if my ask isn't clear.

Our Chargebee implementation uses product catalog 2.0 which I expected would be flattened out tables into addons, plans, etc. on extract. I also noticed in the stitch integration documentation it said the tables/fields would be based on the product catalog version. The stitch integration says it's using version 1.0. The main question here is, if we're using product catalog 2.0, should I expect extracted tables to be flatted out and not nested? For example, item constraints is nested into coupons rather than being it's own table. Can you help me understand if I'm missing something or misunderstanding something?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant