Geoffrey Gerhard

This error can result when an Item or Customer has been deleted, or when the Customer record identified by the ListID has been merged with another Customer. The latter is much more common when the problem is a Customer ListID, as deleting a Customer record in the QB UI is terrible idea unless there are no transactions related to it. HTH! Geoffrey Gerhard Creative Solutions Incorporated 14000 Creekside Drive Matthews, NC 28105 704.814.6852

Coming to this thread late, but a couple notes for readers who might have similar issues: Use an ItemQuery to find all Items, regardless of their QB type, that match the request's criteria. PCI Pal correctly notes that the "ManufacturerPartNumber" is not available as a filter in a Query Request. But if "Part Number" is meant to describe the QB Item Name/Number value, you can use the NameFilter in your Query Request. HTH! Geoffrey Gerhard Creative Solutions Incorporated 14000 Creekside Drive Matthews, NC 28105 704.814.6852

If I'm reading correctly, you're looking at the response from an ItemInventoryQuery. It only shows the ListID and FullName values of the three Accounts relevant to an inventory item: IncomeAccount, COGSAccount, and AssetAccount. To get the AccountNumber value for any one of them, you'll need to create an AccountQuery request. Use the ListID or FullName value returned by the ItemInventoryQuery. HTH! Geoffrey Gerhard Creative Solutions Incorporated 14000 Creekside Drive Matthews, NC 28105 704.814.6852

Yes. Use the AppliedToTxnAdd node to identify the Invoice's TxnID and PaymentAmount values. HTH! Geoffrey Gerhard Creative Solutions Incorporated 14000 Creekside Drive Matthews, NC 28105 704.814.6852

Hey Bruce— I can't provide an example because my process is built into a "black box" file that I use as middleware between a client solution and QB. That file is the result of many projects that iteratively improved it, and it has hundreds of development hours in it. I started a basic outline of how it works on the Request side, and realized you'd be much better off using the normal functions to create Requests. Responses, though, are a different matter. The PCQB_Rs functions work fine for simple integrations, but parsing the Response from a complex Query or a Report is much more pow

Hey Bruce-- I don't have an example file. What I meant was that I don't use the PCQB_Rq... or PCQB_Rs... functions to create a Request or parse a Response, preferring to build a Request using a process I came up with years ago. I use the PCQB_Z functions to Execute it, and the PCQB_ZParseXML function to process the Response data. When processing a QB Report or a multi-record Query Response, Xpath filtering is awesome. Using PCQB_SGetXML you can see all the elements of a Request or Response at one time, which is especially useful when digging into problems that may hinge on the presen

It's been a long time since I looked at Payroll via the API. It's possible that the Response doesn't contain the data you want. Are you logging into QB via an Admin credential? and does the plug-in have permission to putt "sensitive data" ? It might be useful to use PCQB_SGetXML( "Response" ; "" ) to see everything that's being returned and confirm that the Earnings node is present. HTH! Geoffrey Gerhard Creative Solutions Incorporated 14000 Creekside Drive Matthews, NC 28105 704.814.6852

The Earnings node may repeat, so you'll need to use PCQB_RsOpenFirstRelatedRecord and PCQB_RsOpenNextRelatedRecord to walk through them and get the values you want from each iteration. PCQB_rsGetFirstFieldValue ( PayrollItemWageRef::FullName ) and PCQB_rsGetFirstFieldValue ( Rate ) should get the values you need. (I say "should" because I'm not positive--I work with raw xml and XPath.) Are you looking for values from all repetitions of Earnings, or just a particular one or two? If it's just one and you already know how to apply XPath filters, that's faster than looping through the it

Hey Bruce– You can update the "Name" value for a Vendor record, but cannot set it to empty (clear it) because it's effectively the Vendor record's primary key in QB. For the same reason, you cannot update it to a value that's already in use by another Vendor record. The error message you cite implies that this record's Vendor::VendorName field was empty at the time you created the VendorModRq. HTH! Geoffrey Gerhard Creative Solutions Incorporated 14000 Creekside Drive Matthews, NC 28105 704.814.6852

Productive Computing updated the link to the original OSR in their documentation, but for anyone still looking for it... https://static.developer.intuit.com/qbSDK-current/common/newosr/index.html Long-time FMP/QB integrators will likely prefer the familiar views and behavior of the above link, but it's worth noting that the link Bruce posted above... https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference ...is a new version of the OR that puts the descriptive information about each Request, including context for how its behaviors equate to those found in th

Just found the page Bruce linked and came here to share it. It may grow on me, but first impression is not great. If you find it, PCI Pal, please post a link. ( If you know the name of the downloaded file, please post that. ) Thanks! Geoffrey Gerhard Creative Solutions Incorporated 14000 Creekside Drive Matthews, NC 28105 704.814.6852

Same problem. Productive Computing had, once upon a time, a downloadable version that you could open in your browser and it worked great. I can't find any reference to it on their web site now, nor remember the file's name to find it on my computer. Kinda stuck on some development work right now.

This may be the result of an Auto-Update in QB. One of my clients reported on Monday that he was seeing my "Can't connect to QB" error message. The only change was the update to QB, and logging into it as Admin, deleting the certificate, and then running the QB Connection script from FMP fixed the issue. He approved the API connection in QB when prompted, and all was good again. Geoffrey Gerhard Creative Solutions Incorporated 14000 Creekside Drive Matthews, NC 28105 704.814.6852

Make sure any FMP scripts that interact with QB do so only for the user/credential on that one computer. Will the user on that computer be working within the QB UI? If so that user should log into QB using a credential with sufficient privileges to perform all of the automated tasks. QB, just like FMP, is a database and will lock a record when a user begins editing. That can lead to an error if one of your scripts attempts to edit a "locked" QB record, so make sure you're sharing error messages with your user. HTH! Geoffrey Gerhard Creative Solutions Incorporated 14000 Creek

You identified the right fields: Either a ListID or FullName value identifies the Customer/CustomerJob. (You only need one, has you send both QB uses ListID and ignores the FullName value.) When you identify the Customer/Job and identify BillableStatus as True, QuickBooks will ask, when adding an Invoice via the UI, whether to display the list of BillItems not yet Invoiced to the Customer/Job for inclusion on the new Invoice. You can also use it for generating reports in QB. In FMP/QB integrations, there may not be much value to in identifying the Customer/CustomerJob if most of the