Roger Far

Don't use Beta10 yet, this release should be marked as a pre-release in NPM because it's missing some vital things.

@atul-wizni could you please pull the 10.0 beta from NPM and mark it as a pre-release, it's far from ready to be used. Every time we upgrade packages it gets...

@atu1kr

> This also no longer seems to work for me, but at one point it did. `"svelte.plugin.svelte.compilerWarnings"` no longer seems like a valid key. This still works for me: `.vscode/settings.json`...

That would be a great idea, if you need any help with doing some of that I can help in the next few weeks.

Unfortunately found another example, `VendorQueryRs` has a field `ReportingPeriod` which can return `Annual`, but according to the XML:  Contacting support about these kind of issues got me nowhere, so...

Meanwile schema 16 has been released, would it be an idea to upgrade? I did a quick compare and it doesn't seem like a lot of breaking changes, just new...

According to QB the qbXML spec is backwards compatible: https://developer.intuit.com/app/developer/qbdesktop/docs/get-started/sdk-compatibility-with-quickbooks-releases I can't speak for other users, but all our customers, about 75, are using at least QB2022+, I'm not sure...

Yes for sure, I had to pull them out the QB16 SDK too. [QBSDK16 XML.zip](https://github.com/jsgoupil/quickbooks-sync/files/10427326/QBSDK16.XML.zip) Let me know if you want me to share the complete 16 SDK.

I get it from here: https://developer.intuit.com/app/developer/qbdesktop/docs/get-started/download-and-install-the-sdk You will need an account, don't think you need a specific type of account. This is a direct link to the latest version: https://developer.intuit.com/app/developer/logged-in-content/QBSDK160_x64.exe