SuiteTalk-Connector 0.0.4

Introduction

The SuiteTalk Connector is a robust integration tool that empowers developers to seamlessly connect and interact with the NetSuite ERP (Enterprise Resource Planning) system using web services. By leveraging the power of SuiteTalk API, the SuiteTalk Connector enables the automation of business processes, data synchronization, and the creation of custom integrations with NetSuite.

The SuiteTalk Connector acts as a bridge between your application and NetSuite, simplifying the integration process and abstracting the complexities of interacting with the underlying SuiteTalk API. It provides a higher-level interface, allowing developers to focus on business logic rather than low-level API implementation details.

Key Features

The SuiteTalk Connector offers the following key features:

1. Authentication: The connector handles secure authentication with NetSuite, ensuring authorized access to the API using the appropriate credentials.

2. API Interaction: It provides a simplified interface for making API requests to NetSuite, abstracting the underlying SOAP (Simple Object Access Protocol) communication and facilitating seamless integration with your application.

3. Data Mapping: The connector simplifies the mapping and transformation of data between your application and NetSuite's data model, ensuring smooth data synchronization and integration.

4. Error Handling: It includes comprehensive error handling mechanisms, allowing for robust error management and graceful recovery during API interactions.

5. Performance Optimization: The connector incorporates optimizations to enhance performance, such as request batching, minimizing network round trips, and optimizing data retrieval and update operations.

6. Flexibility: The SuiteTalk Connector is highly customizable and can be extended to accommodate specific integration requirements. It enables developers to build tailored solutions that align with their unique business processes.

Benefits of Using SuiteTalk Connector

• Streamlined Integration: The connector simplifies the integration process, enabling efficient communication between your application and NetSuite.

• Customizability: Developers can extend and customize the connector to meet specific integration needs and business requirements.

• Automation and Efficiency: The integration capabilities offered by the connector automate business processes, improving efficiency and reducing manual effort.

• Real-Time Data Sync: Achieve real-time data synchronization between your application and NetSuite, ensuring accurate and up-to-date information.

By leveraging the SuiteTalk Connector, developers can unlock the full potential of NetSuite's API, enabling seamless integration, customization, and automation of business processes. Experience streamlined integration and harness the power of NetSuite with the SuiteTalk Connector.

Installation

To install the SuiteTalk Connector using pip and Git, run the following command:

$ python -m pip install SuiteTalk-Connector

or

$ python -m pip install 'git+ssh://git@github.com/ideabosque/suitetalk_connector.git@main#egg=suitetalk_connector'

Configuration

To configure the NetSuite SuiteTalk Connector, you'll need to set up the following files and environment variables:

.env File

Create a .env file in the project directory with the following example configuration:

ACCOUNT=*******
CONSUMER_KEY=****************************************************************
CONSUMER_SECRET==****************************************************************
TOKEN_ID==****************************************************************
TOKEN_SECRET==****************************************************************

Replace the ******* and **************************************************************** placeholders with your actual NetSuite account ID, consumer key, consumer secret, token ID, and token secret.

netsuitemappings_soap.json File

Create a netsuitemappings_soap.json file in the project directory with the appropriate mappings for the desired transaction types, attributes, and data types. Here is an example configuration:

{
  "transaction_data_type": {
    "salesOrder": "ns19:SalesOrder",
    "opportunity": "ns19:Opportunity",
    "estimate": "ns19:Estimate",
    "returnAuthorization": "ns23:ReturnAuthorization"
  },
  "transaction_item_data_type": {
    "salesOrder": "ns19:SalesOrderItem",
    "opportunity": "ns19:OpportunityItem",
    "estimate": "ns19:EstimateItem",
    "returnAuthorization": "ns23:ReturnAuthorizationItem"
  },
  "transaction_item_list_data_type": {
    "salesOrder": "ns19:SalesOrderItemList",
    "opportunity": "ns19:OpportunityItemList",
    "estimate": "ns19:EstimateItemList",
    "returnAuthorization": "ns23:ReturnAuthorizationItemList"
  },
  "person_data_type": {
    "customer": "ns13:Customer",
    "contact": "ns13:Contact"
  },
  "person_addressbook_list_data_type": {
    "customer": "ns13:CustomerAddressbookList"
  },
  "person_addressbook_data_type": {
    "customer": "ns13:CustomerAddressbook"
  },
  "item_data_type": {
    "inventoryItem": "ns17:InventoryItem",
    "nonInventoryResaleItem": "ns17:NonInventoryResaleItem",
    "lotNumberedInventoryItem": "ns17:LotNumberedInventoryItem"
  },
  "lookup_join_fields": {
    "itemFulfillment": {
      "base": [
        "@|custbody_bol_id",
        "@|custbody_bol_number",
        "fulfill_last_modified_date|lastModifiedDate",
        "fulfill_internal_id|internalId",
        "fulfill_ship_status|shipStatus"
      ],
      "lines": [
        "serial_numbers|serialNumbers"
      ],
      "created_from_types": [
        "salesOrder"
      ]
    },
    "invoice": {
      "base": [
        "invoice_tran_id|tranId",
        "invoice_status|status",
        "invoice_tran_date|tranDate",
        "invoice_total|total"
      ],
      "lines": [],
      "created_from_types": [
        "salesOrder"
      ]
    },
    "vendorBill": {
      "base": [
        "transaction_number|transactionNumber",
        "due_date|dueDate",
        "erp_bill_ref|internalId"
      ],
      "lines": [],
      "created_from_types": [
        "purchaseOrder"
      ]
    },
    "itemReceipt": {
      "base": [
        "receipt_internal_id|internalId",
        "receipt_created_date|createdDate"
      ],
      "lines": [],
      "created_from_types": [
        "purchaseOrder"
      ]
    },
    "returnAuthorization": {
      "created_from_lookup_type": "salesOrder"
    }
  },
  "lookup_record_fields": {
    "salesOrder": {
      "field": "custbody_pct_so_ecomso",
      "search_data_type": "ns5:TransactionSearchBasic"
    },
    "opportunity": {
      "field": "custbody_bid_reference",
      "search_data_type": "ns5:TransactionSearchBasic"
    },
    "estimate": {
      "field": "otherRefNum",
      "search_data_type": "ns5:TransactionSearchBasic"
    },
    "returnAuthorization": {
      "field": "custbody_rma_reference",
      "search_data_type": "ns5:TransactionSearchBasic"
    },
    "inventoryItem": {
      "field": "itemId",
      "search_data_type": "ns5:ItemSearchBasic"
    },
    "lotNumberedInventoryItem": {
      "field": "itemId",
      "search_data_type": "ns5:ItemSearchBasic"
    },
    "customer": {
      "field": "entityId",
      "search_data_type": "ns5:CustomerSearchBasic"
    },
    "contact": {
      "field": "entityId",
      "search_data_type": "ns5:ContactSearchBasic"
    },
    "vendor": {
      "field": "entityId",
      "search_data_type": "ns5:VendorSearchBasic"
    },
    "subsidiary": {
      "field": "name",
      "search_data_type": "ns5:SubsidiarySearchBasic"
    },
    "location": {
      "field": "name",
      "search_data_type": "ns5:LocationSearchBasic"
    },
    "classification": {
      "field": "name",
      "search_data_type": "ns5:ClassificationSearchBasic"
    },
    "employee": {
      "field": "entityId",
      "search_data_type": "ns5:EmployeeSearchBasic"
    },
    "priceLevel": {
      "field": "name",
      "search_data_type": "ns5:PriceLevelSearchBasic"
    },
    "inventoryNumber": {
      "field": "inventoryNumber",
      "search_data_type": "ns5:InventoryNumberSearchBasic"
    }
  },
  "lookup_select_values": {
    "terms": {
      "values": {
        "Net 10": "1",
        "Net 15": "2",
        "Net 20": "3"
      }
    },
    "paymentMethod": {
      "values": {
        "ACH": "1",
        "American Express": "2",
        "Cash": "3",
        "Check": "4",
        "Discover": "5",
        "Master Card": "6",
        "VISA": "7",
        "Wire": "8"
      }
    },
    "taxSchedule": {},
    "customForm": {},
    "shipMethod": {
      "values": {
        "Truck": "1",
        "UPS": "2",
        "UPS 2nd Day Air®": "3",
        "UPS Next Day Air®": "4",
        "UPS Next Day Air® Early A.M.®": "5",
        "UPS® Ground": "6"
      },
      "record_type": "shipItem",
      "field": "displayName"
    },
    "salesRep": {
      "record_type": "employee",
      "field": "entityId"
    },
    "class": {
      "record_type": "classification",
      "field": "name"
    },
    "subsidiary": {
      "record_type": "subsidiary",
      "field": "name"
    },
    "location": {
      "record_type": "location",
      "field": "name"
    },
    "custbody_delivery_option": {
      "values": {
        "Standard": "4",
        "Premium": "5",
        "Expedited": "6"
      }
    },
    "custentityyyy": {
      "record_type": "customlist_yyyy_list",
      "field": "name"
    },
    "custentity_program_sales_rep": {
      "record_type": "employee",
      "field": "entityId"
    },
    "custentityxxx": {
      "record_type": "customlistxxx",
      "field": "name"
    }
  },
  "custom_records": {
    "customrecord_shipping_carrier": "111"
  },
  "item_detail_record_types": [
    "purchaseOrder",
    "returnAuthorization"
  ],
  "inventory_detail_record_types": [
    "purchaseOrder",
    "itemReceipt",
    "itemFulfillment",
    "salesOrder",
    "returnAuthorization"
  ],
  "transaction_update_statuses": {
    "salesOrder": ["Cancelled"],
    "returnAuthorization": []
  }
}

Parameters:

• transaction_data_type: This parameter defines the SOAP data type associated with each transaction type in NetSuite. It specifies the data type used to represent the transaction data.
• transaction_item_data_type: This parameter determines the SOAP data type associated with the items within a transaction. It indicates the data type used to represent individual items in a transaction.
• transaction_item_list_data_type: This parameter indicates the SOAP data type for the list of items within a transaction. It specifies the data type used to represent the collection of items in a transaction.
• person_data_type: This parameter defines the SOAP data type for person-related records, such as customers and contacts, in NetSuite.
• person_addressbook_data_type: This parameter specifies the SOAP data type for the address book of a person, typically used for customers or contacts in NetSuite.
• person_addressbook_list_data_type: This parameter indicates the SOAP data type for the list of address books associated with a person, usually used for customers or contacts in NetSuite.
• item_data_type: This parameter determines the SOAP data type for various item types in NetSuite, such as inventory items, non-inventory resale items, and lot-numbered inventory items.
• lookup_join_fields: This parameter includes configurations for joining related records in NetSuite. It defines how different records are linked together in search results.
• lookup_record_fields: This parameter contains configurations for field mappings when looking up records in NetSuite. It specifies the fields used for searching and linking records.
• lookup_select_values: This parameter provides configurations for select field values in NetSuite. It defines the possible values and their corresponding internal IDs for specific fields.
• custom_records: This parameter contains configurations for custom records in NetSuite. It specifies the internal IDs of custom records that can be used in the integration.
• item_detail_record_types: This parameter lists the record types in NetSuite that have detailed information about items. For example, purchase orders and return authorizations may have additional item details.
• inventory_detail_record_types: This parameter lists the record types in NetSuite that have detailed information about inventory-related transactions, such as purchase orders, item receipts, item fulfillments, sales orders, and return authorizations.
• transaction_update_statuses: This parameter serves two pivotal purposes for updating records. Firstly, it facilitates updates only when the transaction status aligns with the statuses listed. Secondly, it ensures updates occur if the transaction's record type is absent from the keys within transaction_update_statuses.

Sample Configuration

Here is a sample configuration file that loads the environment variables and sets up the NetSuite SuiteTalk Connector:

import logging
import os
import sys
import json
from dotenv import load_dotenv
from suitetalk_connector import SOAPConnector

logging.basicConfig(stream=sys.stdout, level=logging.INFO)
logger = logging.getLogger()

load_dotenv()
setting = {
    "ACCOUNT": os.getenv("ACCOUNT"),
    "CONSUMER_KEY": os.getenv("CONSUMER_KEY"),
    "CONSUMER_SECRET": os.getenv("CONSUMER_SECRET"),
    "TOKEN_ID": os.getenv("TOKEN_ID"),
    "TOKEN_SECRET": os.getenv("TOKEN_SECRET"),
    "VERSION": "2021_2_0",
    "TIMEZONE": "America/Los_Angeles",
    "NETSUITEMAPPINGS": json.load(
        open(
            f"{os.path.abspath(os.path.dirname(__file__))}/netsuitemappings_soap.json",
            "r",
        )
    )
}

soap_connector = SOAPConnector(logger, **setting)

Ensure that you have the required Python packages installed, including dotenv. You can install them using the following command:

$ python -m pip install dotenv

Make sure to replace the path to the netsuitemappings_soap.json file with the appropriate location in your project directory.

With this configuration, you can now use the soap_connector object to interact with the NetSuite SuiteTalk API.

Usage

To use the NetSuite SuiteTalk Connector, you can follow the examples below:

Get the ID value of a dropdown custom field for a specific record type

Use the get_select_value_id method to retrieve the ID value of a dropdown custom field.

Parameters:

• value: The value of the dropdown option.
• custom field name: The name of the custom field.
• record_type: The record type in which the custom field is defined.

id = soap_connector.get_select_value_id(
    "To Be Determined",
    "custbody_carrier_other",
    record_type="salesOrder"
)

This method will return the ID value associated with the specified dropdown option.

Get a record by its internal ID

Use the get_record method to retrieve a record by its internal ID.

Parameters:

• record_type: The type of the record.
• internalId: The internal ID of the record.

record = soap_connector.get_record(
    "purchaseOrder",
    "11234567"
)

This method will return the record object corresponding to the specified record type and internal ID.

Retrieve Transactions

You have the capability to fetch transactions based on the cut date and various other parameters using the SuiteTalk Connector. Let's delve into the available parameters:

• record_type: This parameter allows you to specify the transaction record type, offering a range of options, including:
  • "salesOrder"
  • "invoice"
  • "purchaseOrder"
  • "estimate"
  • "opportunity"
  • "returnAuthorization"
  • "itemFulfillment"
  • "itemReceipt"
  • "vendorCredit"
  • "vendorPayment"
  • "inventoryAdjustment"
  • "creditMemo"
  • "inventoryTransfer"
• kwargs: Additional parameters that provide flexibility for fine-tuning and customization.

Here's an illustrative example of how to retrieve transactions with the SuiteTalk Connector:

# Define filtering criteria using kwargs
kwargs = {
    "cut_date": "2022-02-04T16:00:00+00:00",
    "end_date": "2022-02-05T16:00:00+00:00",
    "limit": 100,
    "subsidiary": "ABC",
}

# Acquire the initial result containing search information
result = soap_connector.get_transaction_result(
    "itemReceipt", **kwargs
)

records = soap_connector.get_transactions(
    "itemReceipt", result["records"], **kwargs
)

Additionally, you have the option to retrieve data using a search ID and page index, as demonstrated below:

# Define the filtering criteria with search ID and page index
kwargs = {
   'search_id': 'WEBSERVICES_xxxxxxxxxxxxxxxxxxxxxxxxx', 
   'page_index': 1, 
}

# Obtain the initial result containing search information using the search ID and page index
result = soap_connector.get_transaction_result(
    "itemReceipt", **kwargs
)

records = soap_connector.get_transactions(
    "itemReceipt", result["records"], **kwargs
)

The result data returned by the get_transaction_result method includes essential information:

{
   'search_id': 'WEBSERVICES_xxxxxxxxxxxxxxxxxxxxxxxxx', 
   'total_records': 85, 
   'total_pages': 1, 
   'page_index': 1, 
   'records': [....]
}

This method empowers you to retrieve transactions of the specified record type based on the provided parameters, granting you the flexibility to tailor your data retrieval process.

Retrieve Items

To obtain specific items based on various criteria, you can harness the power of the SuiteTalk Connector. Let's break down the available parameters:

• record_type: This parameter specifies the item record type you intend to retrieve. You can select from the following options:
  • "product"
  • "inventory"
  • "inventorylot"
  • "pricelevel"
• kwargs: Additional parameters that offer advanced filtering and customization options.

Here's an example demonstrating how to retrieve items:

# Set the filtering criteria using kwargs
kwargs = {
    "cut_date": "2022-02-04T16:00:00+00:00",
    "end_date": "2022-02-05T16:00:00+00:00",
    "limit": 100,
    "subsidiary": "ABC",
    "item_types": [
        "inventoryItem",
        "lotNumberedInventoryItem",
    ],
    "custom_fields": {
        "custitem3": "kg",
    },
}

# Acquire the initial result containing search information
result = soap_connector.get_item_result(
    "inventoryLot", **kwargs
)

records = soap_connector.get_items(
    "inventoryLot", result["records"], **kwargs
)

Furthermore, you have the option to retrieve data using a search ID and page index, as demonstrated below:

# Define the filtering criteria, including the search ID and page index
kwargs = {
   'search_id': 'WEBSERVICES_xxxxxxxxxxxxxxxxxxxxxxxxx', 
   'page_index': 1, 
}

# Acquire the initial result containing search information using the search ID and page index
result = soap_connector.get_item_result(
    "inventoryLot", **kwargs
)

records = soap_connector.get_items(
    "itemReceipt", result["records"], **kwargs
)

The result data returned by the get_item_result method contains vital information:

{
   'search_id': 'WEBSERVICES_xxxxxxxxxxxxxxxxxxxxxxxxx', 
   'total_records': 85, 
   'total_pages': 1, 
   'page_index': 1, 
   'records': [....]
}

This method empowers you to access specific item records while providing flexibility in filtering and customization.

Get Persons

You can also retrieve persons based on the cut date and other parameters using the SuiteTalk Connector. Here's an overview of the available parameters:

• record_type: The person record type. Choose from the following options:
  • "customer"
  • "vendor"
  • "company"
  • "contact"
• kwargs: Additional parameters for refining and customizing your query.

Here's an example of how to retrieve persons:

# Define the filter criteria using kwargs
kwargs = {
    "cut_date": "2022-02-04T16:00:00+00:00",
    "limit": 100,
    "hours": 0.5,
    "subsidiary": "ABC",
}

# Obtain the initial result containing search information
result = soap_connector.get_person_result(
    "customer", **kwargs
)

records = soap_connector.get_persons(
    "customer", result["records"], **kwargs
)

Similarly, you have the option to retrieve data using a search ID and page index, as demonstrated below:

# Define the filter criteria, including the search ID and page index
kwargs = {
   'search_id': 'WEBSERVICES_xxxxxxxxxxxxxxxxxxxxxxxxx', 
   'page_index': 1, 
}

# Obtain the initial result containing search information
result = soap_connector.get_person_result(
    "customer", **kwargs
)

records = soap_connector.get_persons(
    "customer", result["records"], **kwargs
)

The result data returned by the get_person_result method contains crucial information:

{
   'search_id': 'WEBSERVICES_xxxxxxxxxxxxxxxxxxxxxxxxx', 
   'total_records': 85, 
   'total_pages': 1, 
   'page_index': 1, 
   'records': [....]
}

This approach equips you to retrieve persons of the specified record type, enabling you to further tailor your data retrieval process as needed.

Parameters within kwargs for get_transaction_result, get_item_result, and get_person_result:

• cut_date: This parameter signifies the timestamp of the most recent cut-off date. Format: YYYY-MM-DDTHH:MM:SS.
• end_date: The concluding date for processing the request. Format: YYYY-MM-DDTHH:MM:SS.
• hours: The time span in hours, starting from the cut date.
• subsidiary: Denotes the subsidiary of the company.
• item_types (for get_items): A list enumerating the item record types to retrieve.
• custom_fields (for get_items): A dictionary specifying custom fields and their corresponding values to serve as filtering conditions.
• search_id (for pagination): Facilitates retrieval of prior search results.
• page_index (for pagination): Indicates the page index to retrieve from previous search results.

Inserting or Updating Transactions

The insert_update_transaction function in the SuiteTalk Connector allows you to seamlessly insert new transactions into NetSuite or update existing ones. This function provides a comprehensive set of features to handle various aspects of the transaction, including data mapping, custom fields, item details, and more. Below, we'll explain how to use this function and its key capabilities.

Function Signature:

def insert_update_transaction(self, record_type, transaction):

• record_type: The type of transaction you want to insert or update (e.g., "salesOrder", "invoice", "purchaseOrder", etc.).
• transaction: A dictionary representing the transaction data that you want to insert or update.

Key Features:

1. Data Mapping: The function handles the mapping and transformation of data between your application and NetSuite's data model, ensuring seamless integration.

2. Custom Fields: It supports custom fields, allowing you to include additional custom data in your transactions.

3. Item Details: You can include item details, such as item lines and item lists, as part of the transaction.

4. Address Handling: The function can manage billing and shipping addresses associated with the transaction.

5. Date and Status Handling: It handles dates (e.g., shipDate, tranDate) and transaction statuses efficiently.

6. Customer Deposit: For "salesOrder" transactions, it can automatically insert a Customer Deposit if specified in the configuration.

7. Notes: You can add notes to the transaction for additional context.

Usage Example:

Here's an example of how to use the insert_update_transaction function:

# Example transaction data
transaction_data = {
    "recordType": "salesOrder",
    "extCustomerId": "12345",
    "notes": [
        {
            "title": "Important Note",
            "memo": "This is an important note for the order.",
        }
    ],
    # ... Other transaction data ...
}

# Insert or update the transaction
result = soap_connector.insert_update_transaction("salesOrder", transaction_data)

# The result will contain the transaction ID or other relevant information.
print("Transaction ID:", result.tranId)

This function simplifies the process of inserting or updating transactions in NetSuite, allowing you to focus on your business logic while abstracting the complexities of the SuiteTalk API.

Inserting or Updating Persons (Customers, Vendors, etc.)

The insert_update_person function in the SuiteTalk Connector allows you to insert new person records (e.g., customers, vendors) into NetSuite or update existing ones. This function provides extensive capabilities for managing person details, including addresses, categories, custom fields, and more. Below, we'll explain how to use this function and its key features.

Function Signature:

def insert_update_person(self, record_type, person):

• record_type: The type of person record you want to insert or update (e.g., "customer", "vendor", etc.).
• person: A dictionary representing the person data that you want to insert or update.

Key Features:

1. Data Mapping: The function handles the mapping and transformation of person data between your application and NetSuite, ensuring smooth integration.

2. Addresses: You can associate multiple addresses with a person, including specifying default shipping and billing addresses.

3. Company Linkage: It supports linking a person to a company record, simplifying the representation of relationships between individuals and organizations.

4. Categories: You can assign categories to a person, facilitating segmentation and categorization of your records.

5. Custom Fields: It supports custom fields for person records, allowing you to capture additional information as needed.

6. Contacts: The function handles contacts associated with a person record, including adding or updating contact details.

Usage Example:

Here's an example of how to use the insert_update_person function:

# Example person data for a customer
customer_data = {
    "recordType": "customer",
    "entityId": "CUST123",
    "firstName": "John",
    "lastName": "Doe",
    "email": "johndoe@example.com",
    "phones": [{"phone": "123-456-7890", "default": True}],
    "addresses": [
        {
            "addr1": "123 Main St",
            "city": "Anytown",
            "state": "CA",
            "zip": "12345",
            "country": "US",
            "defaultShipping": True,
            "defaultBilling": True,
        }
    ],
    "companyInternalId": "COMP456",  # Link to the associated company
    "categories": ["Category1", "Category2"],  # Assign categories
    "customFields": {"customField1": "Value1", "customField2": "Value2"},
    # ... Other person data ...
}

# Insert or update the person (customer)
result = soap_connector.insert_update_person("customer", customer_data)

# The result will contain the internal ID of the person record or other relevant information.
print("Person Internal ID:", result)

This function simplifies the process of inserting or updating person records in NetSuite, allowing you to focus on your business logic while abstracting the complexities of the SuiteTalk API. Whether you're managing customer or vendor records, this function provides the flexibility and features you need to streamline your integration efforts.

Inserting or Updating Items

The insert_update_item function in the SuiteTalk Connector allows you to insert new items into NetSuite or update existing items. This function provides extensive capabilities for managing item details, custom fields, pricing, and more. Below, we'll explain how to use this function and its key features.

Function Signature:

def insert_update_item(self, record_type, item):

• record_type: The type of item you want to insert or update (e.g., "inventoryItem", "lotNumberedInventoryItem", "nonInventoryResaleItem", etc.).
• item: A dictionary representing the item data that you want to insert or update.

Key Features:

1. Data Mapping: The function handles the mapping and transformation of item data between your application and NetSuite, ensuring smooth integration.

2. Custom Fields: It supports custom fields, allowing you to include additional custom data for your items.

3. Subsidiaries: You can associate items with one or more subsidiaries, streamlining multi-subsidiary operations.

4. Vendors: The function can link items to vendor records, enabling efficient vendor management.

5. Item Custom Fields: You can include custom fields specific to items to capture additional item-related information.

6. Pricing: It supports pricing, including the ability to set MSRP (Manufacturer's Suggested Retail Price) and price levels for items.

Usage Example:

Here's an example of how to use the insert_update_item function:

# Example item data
item_data = {
    "recordType": "inventoryItem",
    "itemId": "ITEM123",
    "upcCode": "123456789012",
    "mpn": "MPN123",
    "weight": 0.5,
    "weightUnit": "lb",
    "salesDescription": "This is a sample item.",
    "cost": "50",
    "subsidiaries": ["ABC Subsidiary", "XYZ Subsidiary"],
    "vendorEntityIds": ["Vendor1", "Vendor2"],
    "customFields": {
        "customField1": "Value1",
        "customField2": "Value2",
    },
    "msrp": "100",
    "msrpPriceLevel": "Standard",
    # ... Other item data ...
}

# Insert or update the item
result = soap_connector.insert_update_item("inventoryItem", item_data)

# The result will contain the internal ID of the item or other relevant information.
print("Item Internal ID:", result)

This function simplifies the process of inserting or updating items in NetSuite, allowing you to focus on your business logic while abstracting the complexities of the SuiteTalk API.

License

The SuiteTalk Connector is licensed under the MIT License.

MIT License

Copyright (c) [Year] [Your Name]

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Support

For support and inquiries related to the SuiteTalk Connector, please refer to the following resources:

• GitHub Repository: Link to GitHub Repository
• Issues: If you encounter any issues or have questions, please open an issue on the GitHub repository.
• Documentation: Detailed documentation and usage instructions can be found in the repository's README and Wiki.

We welcome your contributions and feedback to improve this module and make it even more valuable for the community.

Feel free to adapt and modify these sections based on your specific requirements and the structure of your project.