conductor-node 11.6.9 → 11.6.11
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "conductor-node",
|
|
3
|
-
"version": "11.6.
|
|
3
|
+
"version": "11.6.11",
|
|
4
4
|
"description": "QuickBooks Desktop API for Node.js and TypeScript",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"QuickBooks",
|
|
@@ -36,7 +36,7 @@
|
|
|
36
36
|
"prepublishOnly": "pnpm jest"
|
|
37
37
|
},
|
|
38
38
|
"dependencies": {
|
|
39
|
-
"axios": "^1.7.
|
|
39
|
+
"axios": "^1.7.3"
|
|
40
40
|
},
|
|
41
41
|
"devDependencies": {
|
|
42
42
|
"axios-mock-adapter": "^1.22.0",
|
|
@@ -2718,8 +2718,8 @@ export default class QbdIntegration extends BaseIntegration {
|
|
|
2718
2718
|
query: (endUserId: string, params?: QbdTypes.TransactionQueryRq) => Promise<NonNullable<QbdTypes.TransactionQueryRs["TransactionRet"]>>;
|
|
2719
2719
|
/**
|
|
2720
2720
|
* Deleting a transaction removes it completely and irreversibly. (Using a
|
|
2721
|
-
* TxnVoid request to void a transaction, on the other hand, sets its
|
|
2722
|
-
* to zero but keeps a record of it in QuickBooks.)
|
|
2721
|
+
* `TxnVoid` request to void a transaction, on the other hand, sets its
|
|
2722
|
+
* amount to zero but keeps a record of it in QuickBooks.)
|
|
2723
2723
|
*
|
|
2724
2724
|
* If you try to delete or void a transaction while it is in use, you will
|
|
2725
2725
|
* get an error. You will also get an error if you try to delete or void a
|
|
@@ -2730,13 +2730,33 @@ export default class QbdIntegration extends BaseIntegration {
|
|
|
2730
2730
|
* QuickBooks.
|
|
2731
2731
|
*
|
|
2732
2732
|
* The mode in which a QuickBooks company file is open (single-user or
|
|
2733
|
-
*
|
|
2733
|
+
* multi-user) does not impact your application’s ability to delete
|
|
2734
2734
|
* transaction objects from it. (List objects can only be deleted if the
|
|
2735
2735
|
* company file is open in single-user mode.)
|
|
2736
2736
|
*
|
|
2737
2737
|
* See more: https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/TxnDel
|
|
2738
2738
|
*/
|
|
2739
2739
|
delete: (endUserId: string, params: QbdTypes.TxnDelRq) => Promise<NonNullable<QbdTypes.TxnDelRs>>;
|
|
2740
|
+
/**
|
|
2741
|
+
* Voiding a transaction sets its amount to zero but keeps a record of it in
|
|
2742
|
+
* QuickBooks. (Using `TxnDel` to delete a transaction, on the other hand,
|
|
2743
|
+
* removes the transaction completely.)
|
|
2744
|
+
*
|
|
2745
|
+
* If you try to void or delete a transaction while it is in use, you will
|
|
2746
|
+
* get an error. You will also get an error if you try to void or delete a
|
|
2747
|
+
* transaction (say a sales receipt) while a linked transaction (such as a
|
|
2748
|
+
* deposit) is in use. If you try to void or delete a transaction that was
|
|
2749
|
+
* created before the company’s closing date, you might or might not get an
|
|
2750
|
+
* error, depending on the permissions and passwords that are set in
|
|
2751
|
+
* QuickBooks.
|
|
2752
|
+
*
|
|
2753
|
+
* The mode in which a QuickBooks company file is open (single-user or
|
|
2754
|
+
* multi-user) does not impact your application’s ability to void
|
|
2755
|
+
* transaction objects in it.
|
|
2756
|
+
*
|
|
2757
|
+
* See more: https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/TxnVoid
|
|
2758
|
+
*/
|
|
2759
|
+
void: (endUserId: string, params: QbdTypes.TxnVoidRq) => Promise<NonNullable<QbdTypes.TxnVoidRs>>;
|
|
2740
2760
|
};
|
|
2741
2761
|
/**
|
|
2742
2762
|
* A transfer is a transaction that moves money from one account to another
|
|
@@ -2723,8 +2723,8 @@ class QbdIntegration extends BaseIntegration_1.default {
|
|
|
2723
2723
|
query: async (endUserId, params = {}) => this.sendRequestWrapper(endUserId, { TransactionQueryRq: params }, "TransactionQueryRs", "TransactionRet"),
|
|
2724
2724
|
/**
|
|
2725
2725
|
* Deleting a transaction removes it completely and irreversibly. (Using a
|
|
2726
|
-
* TxnVoid request to void a transaction, on the other hand, sets its
|
|
2727
|
-
* to zero but keeps a record of it in QuickBooks.)
|
|
2726
|
+
* `TxnVoid` request to void a transaction, on the other hand, sets its
|
|
2727
|
+
* amount to zero but keeps a record of it in QuickBooks.)
|
|
2728
2728
|
*
|
|
2729
2729
|
* If you try to delete or void a transaction while it is in use, you will
|
|
2730
2730
|
* get an error. You will also get an error if you try to delete or void a
|
|
@@ -2735,20 +2735,45 @@ class QbdIntegration extends BaseIntegration_1.default {
|
|
|
2735
2735
|
* QuickBooks.
|
|
2736
2736
|
*
|
|
2737
2737
|
* The mode in which a QuickBooks company file is open (single-user or
|
|
2738
|
-
*
|
|
2738
|
+
* multi-user) does not impact your application’s ability to delete
|
|
2739
2739
|
* transaction objects from it. (List objects can only be deleted if the
|
|
2740
2740
|
* company file is open in single-user mode.)
|
|
2741
2741
|
*
|
|
2742
2742
|
* See more: https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/TxnDel
|
|
2743
2743
|
*/
|
|
2744
2744
|
delete: async (endUserId, params) =>
|
|
2745
|
-
// Call `this.sendRequest` directly instead of using
|
|
2746
|
-
// `this.sendRequestWrapper` because `TxnDel` has a unique input and
|
|
2745
|
+
// Call `this.sendRequest()` directly instead of using
|
|
2746
|
+
// `this.sendRequestWrapper()` because `TxnDel` has a unique input and
|
|
2747
2747
|
// output structure.
|
|
2748
|
-
this.sendRequest(endUserId, "quickbooks_desktop",
|
|
2749
|
-
|
|
2750
|
-
|
|
2751
|
-
|
|
2748
|
+
this.sendRequest(endUserId, "quickbooks_desktop", {
|
|
2749
|
+
TxnDelRq: params,
|
|
2750
|
+
}),
|
|
2751
|
+
/**
|
|
2752
|
+
* Voiding a transaction sets its amount to zero but keeps a record of it in
|
|
2753
|
+
* QuickBooks. (Using `TxnDel` to delete a transaction, on the other hand,
|
|
2754
|
+
* removes the transaction completely.)
|
|
2755
|
+
*
|
|
2756
|
+
* If you try to void or delete a transaction while it is in use, you will
|
|
2757
|
+
* get an error. You will also get an error if you try to void or delete a
|
|
2758
|
+
* transaction (say a sales receipt) while a linked transaction (such as a
|
|
2759
|
+
* deposit) is in use. If you try to void or delete a transaction that was
|
|
2760
|
+
* created before the company’s closing date, you might or might not get an
|
|
2761
|
+
* error, depending on the permissions and passwords that are set in
|
|
2762
|
+
* QuickBooks.
|
|
2763
|
+
*
|
|
2764
|
+
* The mode in which a QuickBooks company file is open (single-user or
|
|
2765
|
+
* multi-user) does not impact your application’s ability to void
|
|
2766
|
+
* transaction objects in it.
|
|
2767
|
+
*
|
|
2768
|
+
* See more: https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/TxnVoid
|
|
2769
|
+
*/
|
|
2770
|
+
void: async (endUserId, params) =>
|
|
2771
|
+
// Call `this.sendRequest()` directly instead of using
|
|
2772
|
+
// `this.sendRequestWrapper()` because `TxnVoid` has a unique input and
|
|
2773
|
+
// output structure.
|
|
2774
|
+
this.sendRequest(endUserId, "quickbooks_desktop", {
|
|
2775
|
+
TxnVoidRq: params,
|
|
2776
|
+
}),
|
|
2752
2777
|
};
|
|
2753
2778
|
/**
|
|
2754
2779
|
* A transfer is a transaction that moves money from one account to another
|
|
@@ -12832,6 +12832,26 @@ export interface TxnDelRs {
|
|
|
12832
12832
|
export type TxnDelType = "ARRefundCreditCard" | "Bill" | "BillPaymentCheck" | "BillPaymentCreditCard" | "BuildAssembly" | "Charge" | "Check" | "CreditCardCharge" | "CreditCardCredit" | "CreditMemo" | "Deposit" | "Estimate" | "InventoryAdjustment" | "Invoice" | "ItemReceipt" | "JournalEntry" | "PayrollLiabilityAdjustment [PRIVATE]" | "PayrollPriorPayment [PRIVATE]" | "PayrollYearToDateAdjustment [PRIVATE]" | "PurchaseOrder" | "ReceivePayment" | "SalesOrder" | "SalesReceipt" | "SalesTaxPaymentCheck" | "TimeTracking" | "TransferInventory" | "VehicleMileage" | "VendorCredit";
|
|
12833
12833
|
export type TxnType = "ARRefundCreditCard" | "Bill" | "BillPaymentCheck" | "BillPaymentCreditCard" | "BuildAssembly" | "Charge" | "Check" | "CreditCardCharge" | "CreditCardCredit" | "CreditMemo" | "Deposit" | "Estimate" | "InventoryAdjustment" | "Invoice" | "ItemReceipt" | "JournalEntry" | "LiabilityAdjustment" | "Paycheck" | "PayrollLiabilityCheck" | "PurchaseOrder" | "ReceivePayment" | "SalesOrder" | "SalesReceipt" | "SalesTaxPaymentCheck" | "Transfer" | "VendorCredit" | "YTDAdjustment";
|
|
12834
12834
|
export type TxnTypeFilter = "All" | "ARRefundCreditCard" | "Bill" | "BillPaymentCheck" | "BillPaymentCreditCard" | "BuildAssembly" | "Charge" | "Check" | "CreditCardCharge" | "CreditCardCredit" | "CreditMemo" | "Deposit" | "Estimate" | "InventoryAdjustment" | "Invoice" | "ItemReceipt" | "JournalEntry" | "LiabilityAdjustment" | "Paycheck" | "PayrollLiabilityCheck" | "PurchaseOrder" | "ReceivePayment" | "SalesOrder" | "SalesReceipt" | "SalesTaxPaymentCheck" | "Transfer" | "VendorCredit" | "YTDAdjustment";
|
|
12835
|
+
export interface TxnVoidRq {
|
|
12836
|
+
/** The type of transaction being voided. */
|
|
12837
|
+
TxnVoidType: TxnVoidType;
|
|
12838
|
+
/** QuickBooks generates a unique `TxnID` for each transaction that is added to QuickBooks. A `TxnID` returned from a request can be used to refer to the transaction in subsequent requests. Notice that you cannot supply the `TxnID` of a `TimeTracking` transaction to `TransactionQueryRq` requests. If you do, you get an error stating that no such record could be found, even though the transaction is in QuickBooks. This behavior reflects the behavior in the QuicKBooks UI in the Find window. */
|
|
12839
|
+
TxnID: string;
|
|
12840
|
+
}
|
|
12841
|
+
export interface TxnVoidRs {
|
|
12842
|
+
/** The type of transaction being voided. */
|
|
12843
|
+
TxnVoidType?: TxnVoidType;
|
|
12844
|
+
/** QuickBooks generates a unique `TxnID` for each transaction that is added to QuickBooks. A `TxnID` returned from a request can be used to refer to the transaction in subsequent requests. Notice that you cannot supply the `TxnID` of a `TimeTracking` transaction to `TransactionQueryRq` requests. If you do, you get an error stating that no such record could be found, even though the transaction is in QuickBooks. This behavior reflects the behavior in the QuicKBooks UI in the Find window. */
|
|
12845
|
+
TxnID?: string;
|
|
12846
|
+
/** Time the object was created. */
|
|
12847
|
+
TimeCreated?: string;
|
|
12848
|
+
/** Time the object was last modified. */
|
|
12849
|
+
TimeModified?: string;
|
|
12850
|
+
/** A string of characters that refers to this transaction and that can be arbitrarily changed by the QuickBooks user. In a `BillPaymentCheckAdd` request, if you want to set the check number, use `RefNumber`.`Note` (especially relevant to `CheckAdd` requests): When `RefNumber` is left blank in an SDK transaction add request (that is, or ), the `RefNumber` will be left blank in QuickBooks. This behavior is new as of QBFC3. It used to select the next sequential reference number since the last one used by QuickBooks, as though no `RefNumber` had been provided. This is especially relevant to `CheckAdd` requests because with the current behavior, you will not know the number until the check is printed. */
|
|
12851
|
+
RefNumber?: string;
|
|
12852
|
+
ErrorRecovery?: ErrorRecovery;
|
|
12853
|
+
}
|
|
12854
|
+
export type TxnVoidType = "ARRefundCreditCard" | "Bill" | "BillPaymentCheck" | "BillPaymentCreditCard" | "Charge" | "Check" | "CreditCardCharge" | "CreditCardCredit" | "CreditMemo" | "Deposit" | "InventoryAdjustment" | "Invoice" | "ItemReceipt" | "JournalEntry" | "SalesReceipt" | "VendorCredit";
|
|
12835
12855
|
export interface UnitOfMeasureSetRef {
|
|
12836
12856
|
/** Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
|
|
12837
12857
|
ListID?: string;
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "conductor-node",
|
|
3
|
-
"version": "11.6.
|
|
3
|
+
"version": "11.6.11",
|
|
4
4
|
"description": "QuickBooks Desktop API for Node.js and TypeScript",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"QuickBooks",
|
|
@@ -36,7 +36,7 @@
|
|
|
36
36
|
"prepublishOnly": "pnpm jest"
|
|
37
37
|
},
|
|
38
38
|
"dependencies": {
|
|
39
|
-
"axios": "^1.7.
|
|
39
|
+
"axios": "^1.7.3"
|
|
40
40
|
},
|
|
41
41
|
"devDependencies": {
|
|
42
42
|
"axios-mock-adapter": "^1.22.0",
|