fmEcommerce Link (Shopify Edition) Frequently Asked Questions

What versions of FileMaker Pro/Pro Advanced does fmEcommerce Link (Shopify Edition) require?

fmEcommerce Link (Shopify Edition) currently works with FileMaker Pro/Pro Advanced v12, v13, v14, v15, v16 and v17. We continue to develop fmEcommerce Link (Shopify Edition) and will ensure it works with future releases of FileMaker Pro.

Can I use fmEcommerce Link (Shopify Edition) with FileMaker Server scripts/Perform Script on Server?

Yes you are able to use FileMaker Server scheduled scripts or Perform Script on Server to interact with your Shopify online store. You would simply need to create “server compatible” script steps using the examples in the fmEcommerce Link (Shopify Edition) file.

Is FileMaker Pro Advanced required?

FileMaker Pro Advanced is only required to copy/paste the Custom Functions that fmEcommerce Link (Shopify Edition) file uses when you are integrating this into your own FileMaker solution file. Otherwise you can use both FileMaker Pro and Pro Advanced when using the fmEcommerce Link (Shopify Edition) functionality.

Does fmEcommerce Link (Shopify Edition) use a plug-in?

Version 1.3 of fmEcommerce Link (Shopify Edition) runs natively under FileMaker Pro/FileMaker Go v16 or later and does not require a plug-in. If you are using FileMaker Pro v15 or earlier a plug-in is required as FileMaker Pro v15 and earlier do not have the required functions to integrate with the Shopify API.

Is FileMaker Go supported?

Version 1.3 of fmEcommerce Link (Shopify Edition) runs natively under FileMaker Go v16 or later as it does not require a plug-in.

Earlier versions of FileMaker Go do not have the required functions to integrate with the Shopify API, so a FileMaker plug-in is currently required. This means that you cannot natively use FileMaker Go to communicate with the Shopify API as FileMaker plug-ins aren’t supported under FileMaker Go, however there is a solution. If the fmEcommerce Link file (or your FileMaker database that you integrate it with) is hosted by FileMaker Server you can use the server side features of FileMaker Server to communicate with the Shopify API (server side scheduled scripts or Perform Script on Server) as FileMaker Server can use plugins.

What’s the best way to integrate this into my existing FileMaker solution?

How you go about integrating the functionality from the fmEcommerce Link (Shopify Edition) file is entirely up to you – as the file is completely unlocked you get to go behind the scenes to learn how to handle the authentication, uploading, downloading etc and then recreate that in your existing FileMaker solution. Based on feedback from customers there have been three main ways they have approached the integration:

Linking – this involves using the fmEcommerce Link file as a ‘interface’ or front-end file to your existing FileMaker file. This is a relatively quick way to get up and running – you relink the table occurrences to reference the matching tables in your existing FileMaker file and then update the layouts and add any new fields (such as the ‘Shopify ID’ fields and the POST data calculation fields). You also need to update any field references in scripts and create any new value lists.

Use the fmEcommerce Link file as a Controller File – this involves downloading data to the fmEcommerce Link file from Shopify (e.g. new Orders each day) and then pushing that data from the fmEcommerce Link file to your existing FileMaker file. This is also a relatively quick way to get up and running – you simply write some additional scripts in the fmEcommerce Link file to push to push Customers, Orders, Order Items etc across to your file. To prevent duplicate Customers from being created you would create a ‘Shopify Customer ID’ field to store the Shopify Customer ID value in your FileMaker solution, otherwise everything else happens in the fmEcommerce Link file. You could then do an download once a day of all Orders received in Shopify and push them to your primary FileMaker solution.

Embedding – this is the most complex and time consuming type of integration as it involves recreating the required functionality from the fmEcommerce Link file in your existing FileMaker solution. Our integration guide covers the high level steps that you need to take and the order in which to complete them. Most of the code can be copied and pasted, however you will need to manually create some relationships, table occurrences and valuelists. You can typically be up and running with authentication and downloading a Customer/Order in around 4 – 8 hours depending on the complexity of your existing FileMaker solution.

If you do decide to use the fmEcommerce Link file you will have to create and manage any required FileMaker Accounts and Privilege Sets.

Is there any documentation to help us get started with using the fmEcommerce Link (Shopify Edition) file?

Yes – we have a dedicated Getting Started page. We also plan to add some additional videos to illustrate particular aspects of the using fmEcommerce Link (Shopify Edition).

Can I upload Product Images using fmEcommerce Link (Shopify Edition)?

Shopify supports two ways of uploading Product Images:

  1. you can enter the URL for an Image and Shopify will download that Image when uploading a Product. That URL must be publicly accessible and point to a valid image file (e.g. .jpg, .png etc)
  2. you can store the Image in a FileMaker container field which will be uploaded directly from the container field when uploading a Product

We have a video demonstrating Product Image uploads on our Videos page.

Can I filter the Shopify API requests by additional parameters ?

Yes – most of the Shopify REST API endpoints accept additional parameters to filter the returned set of records (Orders, Customers, Products etc). We have an example of this in the fmEcommerce Link file when filtering the Orders between 2 dates. The Shopify API Reference has additional information under each endpoint about what parameters you can use to filter each request.

I’m getting an ‘unexpected token’ error when uploading a Product or Product Variant to Shopify

If you’re getting an HTTP 400 response code error when uploading a Product or Product Variant to Shopify where the Last API Result value looks like this:

{
“error”: “419: unexpected token at ‘{ \”id\”:1315190970547841, …
}

the issue here is most likely the presence of a comma in one of the number fields such as price, comparison price or weight. We’ve added a new custom function to v1.3 that simply substitutes out any commas in these fields like this:

Substitute ( number ; “,” ; “.” )

You can update the calculations formula for the ShopifyProductVariantJSON and ShopifyVariantJSON fields by changing the references to the price, comparison price and weight fields from this format:

BE_JSON_Encode ( “price” ; Price ) & “,” &

to this format

BE_JSON_Encode ( “price” ; ConvertComma ( Price ) ) & “,” &

If you are using v1.3 or later and FileMaker Pro v16 or later you don’t have to worry about these changes as FileMaker’s native JSON functions handle the presence of the commas automatically.

Does fmEcommerce Link (Shopify Edition) support Shopify Webhooks?

We currently have support for the Order Creation Webhook – this automatically creates a new Order in the fmEcommerce Link file whenever a new Order is created in Shopify. You can get further details and instructions on setting this up here.

Does fmEcommerce Link (Shopify Edition) support Shopify Metafields?

We currently support the downloading and uploading of Metafields for Products and Product Variants – this blog post has more information on working with Metafields. If you would like us to add support for Metafields elsewhere in the fmEcommerce Link solution please let us know.

Is there a list of changes in each version of fmEcommerce Link (Shopify Edition)?

Yes – to see what’s new with each update check out the fmEcommerce Link (Shopify Edition) version history log

If you have any questions about fmEcommerce Link (Shopify Edition) please contact us and we’ll get back to shortly.