Write-back Support

The Simba Shopify ODBC Connector supports Data Manipulation Language (DML) statements such as INSERT, UPDATE, and DELETE for some tables. Additionally, some tables require the DML statement to include a related ID value, and others can only be changed through a stored procedure.

Writable Tables

You can use standard DML statements to write to the following tables:

• Application_Charges
• Blogs
• Carrier_Services
• Collects
• Countries
• Custom_Collections
• Customers
• Customer_Saved_Searches
• Fulfillment_Events
• Fulfillment_Services
• Pages
• Products
• Redirects
• Script_Tags
• Shop_Metafields
• Smart_Collections
• Themes
• Webhooks

Tables that Require ID Values for Write-back

To insert or update the data in the following tables, you must specify the related ID values in your DML statement:

Table	ID Values Required
Articles	Blog_Id
Assets	Theme_Id
Blog_Metafields	Blog_Id
Comments	Article_Id
Custom_Collection_Metafields	Custom_Collection
Customer_Addresses	Customer_Id
Customer_Metafields	Customer_Id
Fulfillment_Events	Order_Id and Fulfillment_id
Order_Metafields	Order_Id
Order_Risks	Order_Id
Page_Metafields	Page_Id
Product_Metafields	Product_Id
Product_Variants	Product_Id
Product_Variant_Metafields	Product_Id and Product_Variant_Id
Transactions	Order_Id

Tables that Require Stored Procedures for Write-back

To insert or update the data in the following tables, you must use the corresponding stored procedure instead of a DML statement. For detailed information about stored procedures, see the Simba Shopify ODBC Data Connector Reference Guide.

Table	Stored Procedure to Use
Fulfillments	CreateNewFulfillment() or CreateNewFulfillmentFromContent()
Orders	CreateOrder() or CreateOrderFromContent()
Product_Images	CreateProductImage() or CreateProductImageFromContent()
Provinces	AddProvinces() or AddProvincesFromContent()
Refunds	CreateRefund() or CreateRefundFromContent()

Related topics

• Features