To complete the mapping in the table from above: Query: select * from QbdtEntityIdMapping where QbdtEntityType='ACCOUNT' and QbdtExportableId='80000023-1439202874'įrom the response above, Account ‘80000023-1439202874’ from desktop can be mapped to ID=33 from QuickBooks Online. Query: select * from QbdtEntityIdMapping where QbdtEntityType='CUSTOMER' and QbdtExportableId='80000001-1431947192' Query: select * from QbdtEntityIdMapping where QbdtEntityType='INVOICE' and QbdtExportableId='4-1439202892'Īs you can see, invoice ‘4-1439202892’ from QuickBooks desktop can be mapped to ID=1 in QuickBooks Online. Get INVOICE 4-1439202892 in QuickBooks Online The V3 Query API for QbdtEntityIdMapping will help in identifying these equivalent IDs after they have been saved in QuickBooks Online. If a third-party app had this Customer, Account, and Invoice stored within their system, then post migration to QuickBooks Online, the application would need to know the new ID assigned within QuickBooks Online to make an API call. Let’s break up the response to identify their various IDs. The IDs of various entities are bolded below. Let’s take an example of an Invoice created in desktop and the SDK (simplified) response. We have this mapping for most of the data that is migrated from desktop to QuickBooks Online and the query service can be used to find this data. During migration of data from QuickBooks desktop to QuickBooks Online, we now have the IDs used in desktop with the equivalent IDs created in QuickBooks Online persistent in our system. The V3 API Query service has a new searchable entity called “ QbdtEntityIdMapping”.
Note: Currently, this mapping API is only applicable for apps using the QuickBooks XML SDK companies taking advantage of Intuit Data Services cannot make use of this feature at this time. This problem is now addressed in the QuickBooks Online v88 release with a new mapping service, available for all companies that migrated after the QuickBooks Online v87 release on July 2, 2015. Details of this new API are described here. Companies using QuickBooks desktop that migrate to QuickBooks Online (via the “Export to QuickBooks Online” menu option in QuickBooks desktop) can have a hard time mapping the transaction and list ids associated with their QuickBooks desktop data to their QuickBooks Online data. When the data is migrated to QuickBooks Online, these IDs are no longer available via the QuickBooks Accounting API (V3 API services used IDs that are generated inside of QuickBooks Online).
0 kommentar(er)
