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

Migrating from Product Catalog V1 to V2 #73

Open
laliconfigcat opened this issue Nov 27, 2024 · 1 comment
Open

Migrating from Product Catalog V1 to V2 #73

laliconfigcat opened this issue Nov 27, 2024 · 1 comment

Comments

@laliconfigcat
Copy link

What problem does your feature request address?

We are in the middle of migrating from Product Catalog V1 to V2.
The documentation says that for a seamless migration we can use the V1 and V2 endpoints conditionally whether we are on V1 or V2 at a moment:
https://docs.google.com/document/d/1fBWdStVjk8BW_FuBmnYfYfm6vuMgKqQafrmm1jxmUoo/edit?pli=1&tab=t.0

I don't see a way to query this information via the SDK.

I got to a point where I could make a query against this endpoint with ChargeBee.Api.ApiUtil.GetAsync:
var result = await ChargeBee.Api.ApiUtil.GetAsync("/configurations", new Params(), new Dictionary<string, string>(), ChargeBee.Api.ApiConfig.Instance);
But as the result object is an EntityResult that doesn't contain the configuration property, I couldn't use this. While debugging, i could see that this class has a private m_jobj field and it contains the information I would need, but as the field is private, I cannot access it from our code.

Describe the desired solution

A desired solution would be to be able to query this information with the SDK.

Alternatives considered

An alternative would be to change the GetAsync function with a generic type parameter so we can specify the result type we are interested in.

Additional context

No response

@cb-alish
Copy link
Collaborator

Hi @laliconfigcat, thank you for reporting this. We're working on making this endpoint available in the SDK. We'll provide an ETA soon.

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

2 participants