![]() |
VOOZH | about |
Claris FileMaker is a low-code database application development tool that enables users to create custom apps for managing and organizing data. It combines a powerful relational database engine with an intuitive interface, allowing both technical and non-technical users to design and deploy applications across desktop, web, and mobile platforms.
In this article, we'll explore how to use the CData ODBC Driver for Adobe Commerce and FileMaker scripting to connect to Adobe Commerce data.
If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.
Adobe Commerce uses the OAuth 1 authentication standard. To connect to the Adobe Commerce REST API, obtain values for the OAuthClientId, OAuthClientSecret, and CallbackURL connection properties by registering an app with your Adobe Commerce system. See the "Getting Started" section in the help documentation for a guide to obtaining the OAuth values and connecting.
You will also need to provide the URL to your Adobe Commerce system. The URL depends on whether you are using the Adobe Commerce REST API as a customer or administrator.
Customer: To use Adobe Commerce as a customer, make sure you have created a customer account in the Adobe Commerce homepage. To do so, click Account -> Register. You can then set the URL connection property to the endpoint of your Adobe Commerce system.
Administrator: To access Adobe Commerce as an administrator, set CustomAdminPath instead. This value can be obtained in the Advanced settings in the Admin menu, which can be accessed by selecting System -> Configuration -> Advanced -> Admin -> Admin Base URL.
If the Use Custom Admin Path setting on this page is set to YES, the value is inside the Custom Admin Path text box; otherwise, set the CustomAdminPath connection property to the default value, which is "admin".
When you configure the DSN, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.
In this section, we walk through the steps to connect live Adobe Commerce data to FileMaker using the CData ODBC Driver for Adobe Commerce and the Script function. During the initial import, FileMaker brings in all data from the external data source. From the second import onward, it updates only the data that has changed in the external source (a differential update). You can also replace the data in the current record order and schedule these differential updates for automated syncing.
You can download and install the latest version of FileMaker Pro for your Mac/Windows/Linux systems from this link.
Scripting in FileMaker automates complex tasks and workflows by running a sequence of actions with a single command. By using scripting to integrate with Adobe Commerce, you can automatically connect to, import, update, and replace Adobe Commerce data within your FileMaker applications, streamlining data management and improving efficiency.
In this section, we'll use scripts to import Adobe Commerce data into FileMaker by following these steps:
After importing the Adobe Commerce data into FileMaker, use scripts to update or replace any changes made in Adobe Commerce by following this process:
Download a free 30-day trial of CData ODBC Driver for Adobe Commerce to integrate Adobe Commerce data into Claris FileMaker and work with Adobe Commerce data in your FileMaker applications.
Reach out to our Support Team if you have any questions.
Download a free trial of the Adobe Commerce ODBC Driver to get started:
Download NowLearn more:
π Adobe Commerce IconThe Adobe Commerce ODBC Driver is a powerful tool that allows you to connect with live Adobe Commerce data, directly from any applications that support ODBC connectivity.
Access Adobe Commerce like you would a database - read, write, and update Customers, Inventory, Products, Orders, etc. through a standard ODBC Driver interface.