I wanted to communicate this policy enforcement, that went into effect yesterday, to the broader audience. I have reached out, via email, to any developers that are directly affected by this change.
Policy Enforcement:
Restrict the QuickBooks Online REST API v2 from accessing QuickBooks Online Global Companies
Why:
QuickBooks Online REST API v2 is neither designed nor compatible with features of QuickBooks Online global companies, this new restriction will ensure that no data incompatibility occurs. Some of the data incompatibility can be seen on the sales tax reports, since the QuickBooks Online REST API v2 doesn’t support the global tax model.
QuickBooks Online REST API v2 is neither designed nor compatible with features of QuickBooks Online global companies, this new restriction will ensure that no data incompatibility occurs. Some of the data incompatibility can be seen on the sales tax reports, since the QuickBooks Online REST API v2 doesn’t support the global tax model.
When:
Effective with the QuickBooks Online release on December 11th, 2013, the QuickBooks Online REST API v2 will be restricted from accessing QuickBooks Online global companies.
Effective with the QuickBooks Online release on December 11th, 2013, the QuickBooks Online REST API v2 will be restricted from accessing QuickBooks Online global companies.
Action Needed:
Migrate to QuickBooks Online REST API v3, to correctly support the global QuickBooks Online market.
Migrate to QuickBooks Online REST API v3, to correctly support the global QuickBooks Online market.
In regards to migrating to QuickBooks Online REST API v3. It’s pretty much a 1 to 1 mapping between v2 to v3 with the exception of Checks/Cash/Credit Card which all now map to a single Purchase entity.
-david
Leave a Reply