![]() I'll discuss that stack briefly, but cover it in depth in a future blog post. You can use it to specify how each related record ("portal row") should be displayed. The FM Publisher Portal stack is used to publish related records. When publishing multiple records, you can choose to filter and/or sort the records. You can publish data from a single record or multiple records. The FM Publisher Base stack is used to connect to a FileMaker database, specify what records you want to publish, and how the records should be displayed. In the database, I've setup an account that has read-only access, and it can connect to the database via the FileMaker Data API ("fmrest").įM Publisher consists of two stacks: A "base" stack and a "portal" stack. The database is hosted using FileMaker Server. Here's what that database looks like, with a few sample products loaded. I created it using FileMaker's "Inventory" starter solution. The database that I used for this blog post is a simple inventory database. I'm now referring to it as "FM Publisher." ![]() I've recently received a few inquiries about the project, so I thought I'd take a few minutes to show some of the progress that I've made on it.įor clarity and consistency with some of the other stacks that I'm working on (including Air Publisher, the Airtable database publishing stack that I released in early May), I've renamed the stack. I announced the project on the RapidWeaver Forums a few months ago. My goal is to make it as easy as possible to create database-driven Web sites and applications that look nice, are fast, secure, and reliable. ![]() For a few months now, I've been working on a RapidWeaver stack that can be used to publish data that's stored in FileMaker databases.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |