Jun 08, 2022 08:30 AM
I have a table which imports the sales tickets from my Shopify site. In the output are the SKUs of the items sold. I’d like to auto-populate a new table with rows representing each SKU to remove them from another site via API.
This is a sample of the input table, listing_id is what we’re trying to make 1:many rows.
I’ve found a script “Get Single or Multiple Select Options” that gets close (I had to make listing_id a ‘multiple select’ but that’s ok, I think), in that it will output the column values like so:
>11 >194398596211 >12 >888072262546
But I can’t quite thread the needle on getting that to save as a new column in another table. it feels like that should be easy to add to the script but I’m not quite there. open to any solution that creates a one to many value where each SKU is it’s own row basically (the API to remove the values from the other sales solution requires you do them one at a time).
Jun 08, 2022 09:29 AM
I don’t know scripting, but other people here in the forums might chime in with some scripting help.
In the meantime, there are a couple of Shopify add-ons that have been created specifically for Airtable. Here’s one that I know of:
You could also tap directly into the Shopify API by using the datafetcher.com app, which does require knowledge of making API calls:
Or you could use a low-code automation tool like Make.com, which doesn’t require knowledge of API calls:
Jun 08, 2022 09:54 AM
Hi Scott; pulling the data isn’t the problem, I already have Data Fetcher set up and the data pulling just fine. It’s the transformation of it that is difficult.
Jun 08, 2022 10:48 AM
If your Shopify table has a column of SKUs, and all that needs to exist in the SKU table is one row representing each SKU, then you can create a Link to Record field in the Shopify table links to your SKU table.
Since your data is coming in through an API, meaning all fields are filled in at creation, you can use an Automation triggered when “New Shopify table record is created”
Add an Update Record step that copies the value of the plain text SKU into the Link field. Now each unique SKU will be represented in the other table.
If you have a great many number of records that need to be processed, it may be better to do this in a single manual script instead of an Automation as bases only have a limited number of Automation runs each month.