-
Yes... I understand and it worked. However, what I was trying to do is use the customer (recordID) as a "job number" because it's unique and auto generating number.
Would it be better if I created a new field in customer table and make that auto generate? if so, how?
-
The Entity table is a 'special' table that exists in Method only - it doesn't exist in QuickBooks and you cannot add fields directly to it. You can add fields to either the Customer, Employee or Vendor table and miraculously the field will automatically show up in the Entity table for you! :)
This is similar to the ...
-
Why?
When tring to ad a field in the Entity Table I receive the following:
Table does not allow adding fields.
-
I'm only trying to delete 1 record per call, just make multiple calls in a row.
I am trying to delete ofut of a table I created called a1test.
I tried it again just now get :
<ERROR><MESSAGE>ExecuteNonQuery requires an open and available Connection. The connection's current state is ...
-
Are you just trying to reference a Customer's name on a PO? PO's are usually reserved for Vendors.
-
Well also it seems like the original error message you were getting may have been caused by you trying to alter an number that is assigned by QuickBooks. The PO number is a number generated by QuickBooks and cannot be altered or QuickBooks won't be able to recognize it. What you might want to consider is taking that value from ...
-
What am I missing?
I created a button, and created 3 actions on the click:
1. Retrieve value from screen: full name
2. go to tab: purchase order
3. Enter value onto field on screen: field - Ship to , Action from #1.
-
What is the process for the follow:
If I am in the customer screen and want to create a PO for that customer. From the customer screen I want to select a button that opens the Purchase Order screen and automatically insert the customer (ship to) information.
-
Ok. After some thought, I check my customizaton and I believe that the error was caused by it. I'm still havng problems, but I need to check some things out before posting.
-
Matt,
For each APIDelete call there will only be one record deleted at a time. The problem appears to be the table was an accounting table and there were some locking issues when trying to perform some accounting clean up tasks that caused the error.
We've updated the APIDelete. Can you call the APIDelete again and see if the error ...