conductor-node 11.6.12 → 11.6.14

package/dist/package.json

@@ -1,6 +1,6 @@
 {
     "name": "conductor-node",
-    "version": "11.6.12",
+    "version": "11.6.14",
     "description": "QuickBooks Desktop API for Node.js and TypeScript",
     "keywords": [
         "QuickBooks",
@@ -36,7 +36,7 @@
         "prepublishOnly": "pnpm jest"
     },
     "dependencies": {
-        "axios": "^1.7.3"
+        "axios": "^1.7.4"
     },
     "devDependencies": {
         "axios-mock-adapter": "^1.22.0",

package/dist/src/integrations/qbd/qbdTypes.d.ts

@@ -3652,13 +3652,13 @@ export interface DataExtAdd {
     /** The name of the data extension. If this is a custom field, `DataExtName` will be visible as a label in the QuickBooks user interface. Also because `OwnerID` and `DataExtName` together make the data extension unique, and because custom fields all have the same `OwnerID` of zero, the `DataExtName` must be a unique value among existing custom fields. In contrast, the `DataExtName` for private data extensions must be unique only for the specified `OwnerID` GUID. */
     DataExtName: string;
     /** The type of list object (e.g. Customer) that this data extension is attached to. */
-    ListDataExtType: ListDataExtType;
+    ListDataExtType?: ListDataExtType;
     /** Refers to a list object. In a `DataExtAdd` request, the list object ref must be the same type as the type specified in `ListDataExtType`.If a `ListObjRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
-    ListObjRef: ListObjRef;
+    ListObjRef?: ListObjRef;
     /** The type of transaction that the data extension belongs to. */
-    TxnDataExtType: TxnDataExtType;
+    TxnDataExtType?: TxnDataExtType;
     /** 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. */
-    TxnID: string;
+    TxnID?: string;
     /** Identification number of the transaction line. (`TxnLineID` is supported as of v2.0 of the SDK. With qbXML v1.0 and v1.1, `TxnLineID` is always returned as zero.) If you need to add a new transaction line in a transaction Mod request, you can do so by setting the `TxnLineID` to -1. */
     TxnLineID?: string;
     /** Not supported. */
@@ -3679,13 +3679,13 @@ export interface DataExtMod {
     /** The name of the data extension. If this is a custom field, `DataExtName` will be visible as a label in the QuickBooks user interface. Also because `OwnerID` and `DataExtName` together make the data extension unique, and because custom fields all have the same `OwnerID` of zero, the `DataExtName` must be a unique value among existing custom fields. In contrast, the `DataExtName` for private data extensions must be unique only for the specified `OwnerID` GUID. */
     DataExtName: string;
     /** The type of list object (e.g. Customer) that this data extension is attached to. */
-    ListDataExtType: ListDataExtType;
+    ListDataExtType?: ListDataExtType;
     /** Refers to a list object. In a `DataExtAdd` request, the list object ref must be the same type as the type specified in `ListDataExtType`.If a `ListObjRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
-    ListObjRef: ListObjRef;
+    ListObjRef?: ListObjRef;
     /** The type of transaction that the data extension belongs to. */
-    TxnDataExtType: TxnDataExtType;
+    TxnDataExtType?: TxnDataExtType;
     /** 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. */
-    TxnID: string;
+    TxnID?: string;
     /** Identification number of the transaction line. (`TxnLineID` is supported as of v2.0 of the SDK. With qbXML v1.0 and v1.1, `TxnLineID` is always returned as zero.) If you need to add a new transaction line in a transaction Mod request, you can do so by setting the `TxnLineID` to -1. */
     TxnLineID?: string;
     /** Not supported. */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "conductor-node",
-  "version": "11.6.12",
+  "version": "11.6.14",
   "description": "QuickBooks Desktop API for Node.js and TypeScript",
   "keywords": [
     "QuickBooks",
@@ -36,7 +36,7 @@
     "prepublishOnly": "pnpm jest"
   },
   "dependencies": {
-    "axios": "^1.7.3"
+    "axios": "^1.7.4"
   },
   "devDependencies": {
     "axios-mock-adapter": "^1.22.0",