Organisation Class update from Xero, throwing connection error for clients

[chiragtaurther]

the tenant was able to connect and GET Organisation calls were being made. This is usually a call made to get the tenant id and other details for the tenant.

The "Class": "COMPREHENSIVE", field is returned in the call, Does this library updated to have this class as a valid class?

What needs to be done to include this?

Xero recently introduced new plan names and it looks as though your code library to include these new plan names in the accepted list.

Please can you ask your developers to update the enums for the organisation classes. The direct link to the new code in the Open API specification is here

[freakboy3742]

PyXero doesn't currently have any explicit handling of the "Class" field; it's relying on default field handling.

This is an open source project, provided as-is, free of charge. Feel free to submit a pull request to address any problems you find.

[chiragtaurther]

Thank you so much for reply. Really appreciate that. Chirag Tanna Tech Lead M: +91 8320515787 Ahmedabad, IN [Encora]<http://www.encora.com/> [We are proud to be recognized as Leaders in digital engineering services by Zinnov zones]

…

________________________________ From: Russell Keith-Magee ***@***.***> Sent: Tuesday, October 1, 2024 6:13 AM To: freakboy3742/pyxero ***@***.***> Cc: Chirag Anilkumar Tanna ***@***.***>; Author ***@***.***> Subject: Re: [freakboy3742/pyxero] Organisation Class update from Xero, throwing connection error for clients (Issue #360) External Mail: Do not click links or open attachments unless you recognize the sender and know the content is safe. PyXero doesn't currently have any explicit handling of the "Class" field; it's relying on default field handling. This is an open source project, provided as-is, free of charge. Feel free to submit a pull request to address any problems you find. — Reply to this email directly, view it on GitHub<#360 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BAMBEODWXM6LUKXS7UTQQ6TZZHV3PAVCNFSM6AAAAABPCZIHE6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBUGU3DCMZWGU>. You are receiving this because you authored the thread.Message ID: ***@***.***>