Jump to content


Geist Interactive
  • Posts

  • Joined

  • Last visited

  • Days Won


jbrown last won the day on November 1 2019

jbrown had the most liked content!


FileMaker Experience

  • Skill Level
  • FM Application

Platform Environment

  • OS Platform

FileMaker Partner

  • Certification
  • Membership
    FileMaker TechNet
    FileMaker Business Alliance
    FIleMaker Platinum Member

Recent Profile Visitors

1,637 profile views

jbrown's Achievements


Apprentice (3/14)

  • First Post
  • Collaborator
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges



  1. HI. Have you looked at the Kanban board as a possible use for your task list? That add-on has an auto-refresh feature. It pulls data from a table and it will auto-add anything added to the table from many different users.
  2. It solves the problem of collecting lots of nested data, as is in the example. It's not necessary for everyone, but it is a technique. I don't think there's any difficulty in code split: You're gathering data using scripts, pulling data from the fields. JSON is a type of data you can collect. There's no problem in maintaining this because it's set, just like any other calculation field. I agree: unnecessary fields. But these are the only two fields (asJSON, and ListOFJSON) that I'm okay with, calculation and 'unnecessary-wise'. I don't use text functions: JSONSetElement() is a JSON-creation function. So I use that The above is a technique I've used. It's a good way to start. It's a good way to get the feel of this. Overall, however I agree with your idea to keep the data collection in a script. Alignment with this idea doesn't dismiss other ideas.
  3. Question: From where is your data coming? I assume an PO table, PO Lines table, and a Products table, where they are related. Is that correct? Here's how I might do this if this is all data from related tables: 1. Create a calc field in the Products table that creates an object out of ProductCode, ProductDescription, and Guid. It would simply look like this: { "ProductCode": "ALIEN", "ProductDescription": "Alien Artifact", "Guid": "c92823f0-a5af-4e66-91a7-d2c66c25f885" } 2. Create a calc field in the PO Lines table that creates its JSON object with the relevant fields, including the "Product" key that pulls the above calc field into the Product key: JSONSetElement (""; "Product" ; ProductTable::asJSON ; JSONObject ) 3. IN POLines table, create a summary field that generates a ListOf the JSON object calc field, created in step 2. This will just create a list, but i can transform it into an array easily. From the context of one PO record, the script will generate this JSON object. It gathers the PO properties into the object. And it grabs the PO Lines Summary field (created in step 3). It takes this POLines summary field and translates it to an array: Set Variable [ $POLinesArray ; "[" & Substitute (POLines::ListOfSummary) ; "¶" ; ",") & "]") Set variable [$yourJSON ; JSONSetElement("PurchaseOrderLines" ; $POLinesAsArray; JSONArray)] This does add extra schema to your tables. But it's a clean way to get what you need.
  4. Oh Awesome! Glad you figured it out. I actually didn't know that about the add-on. Great discovery.
  5. Howdy. you have to enable file access: File > Manage > Security > Advanced Settings > File Access. Either disable "require full access" (not recommended), or give access to the Generator file.
  6. Everyone here has an interesting FileMaker Origin Story. Sometimes we stumble into the platform, and sometimes we make a deliberate choice. We all know the ending of our stories, but what happened at the beginning? We at Geist Interactive are interested in FileMaker developers' origin stories. We're collecting stories into a series of episodes on The Context Podcacst. Here's the trailer: https://share.transistor.fm/s/d8ad250b Feel free to share your story too. We'd love to hear your story. Reach out at info@geistinteractive.com or send me a message. We'll set up a time to share your story. Please consider it: no matter your experience level, we want to hear them. Thanks Jeremy
  7. WOuld you ever consider not using a list view and detail view in custom apps? Alexis Allen talks with us today about that very idea. Instead of a design that highlights the data structure, build a system and design it so that it emphasizes the workflows. Check out the episode here https://share.transistor.fm/s/0e15cab6
  8. Connecting FIleMaker to outside services is just a given nowadays, and the process is relatively easy to do. Logan Cornelius, today's guest, and his company picked FileMaker for this very reason. Listen to his journey from a FileMaker newbie to connecting his app to 12 different services. https://share.transistor.fm/s/d0465327
  9. Ever since card windows have come out, people are using that UI tool to show a window as a sort of fly-in menu for all layouts. This 'menu' layout has the buttons and nav tools that are global. It's a one-stop-layout for your navigation. This gives you more pixels for your data as the menu is off screen until a user calls it up. Card windows are such that one layout can be called by a button on many different layouts.
  10. Kevin Frank of FileMakerHacks joins us to talk hacking FileMaker and learning FileMaker. We talk about how the site got started and what a FileMaker hack is. He gives us a bunch of great tips. It was our honor to talk with Kevin. He's got a lot to say. Cajoling FileMaker with Kevin Frank. Episode 11
  11. In this week's episode of The Context Podcast, Todd and I talk what I see are the concepts of FileMaker. We discuss ideas such as Transactions, security, inputting data, APIs, and web viewer widgets (of course). It's our belief that one can focus their attention on the concepts of FileMaker and can gain a strong understanding of the platform. Yes, experience matters, but quality time in the concepts give us an overall mental model of what FileMaker can do and how to solve problems in FileMaker. As a former teacher (and as a person who's learning React) , I see the value in getting to the heart of the matter by learning the concepts. Specific techniques and functions and best practices are there to support a concept, so teaching, for example, the virtual list technique or fast summaries, is a good specific skill within the idea of "Reporting on Data". Check it out. Leave us a rating and a review and subscribe, if you would. It's found on Apple Podcasts or wherever you get your podcasts. Thanks
  12. We at Geist Interactive have released a new podcast (well new in the last eight weeks): The Context Podcast. Our podcast is focused on higher-level discussions of the FileMaker platform. We discuss (and embrace) innovation and technology inside and outside of FileMaker. We talk with guests from all around the community about their thoughts on whatever topic is on deck. We also try to ask the guest their thoughts on the context of certain techniques we use in our projects. So far we've released the following episodes: All About the Context: @Todd Geist and @Jeremy B All About join::table: with the folks from join::table (the titles get a bit better from this point forward) FileMaker Milestones and Person Connections: @Todd Geist @Wim Decorte The Security Talk: @Josh Ormond The Context of JavaScript and its Future: Carson Lind A Talk with Women Innovating Together FMPerception and FMComparsion with @Dave Ramsey What do Users Care About with @bigtom Check these out. Subscribe to the podcast on Apple Podcasts or wherever you get your podcasts. And we'd appreciate a review. Let us know how it sounds and what you think of the discssions and guests and host. FINALLY: If you are interested in joining us for an episode and talk about something you're doing in FileMaker, let @Jeremy B know here or at support@geistinteractive.com
  13. Yeah. I had to do this to get the dates in the right order. There's no guarantee the keys will be sorted how I want them to be. If I had done 2017 11 Nov it'd be okay, and the items would stay in the right order. The other option is to do an array, since arrays can be any order. I was working on adjusting it. That said, the re-loop add milliseconds, so I didn't see the actual harm in looping again.
  14. Howdy. Your idea of setting each possible x-axis to 0 and then later updating it is a great idea. I took that and turned it into a JSON object where the key is "2017 Nov" and the value, to start is 0. My version of the script uses your basic look. I updated each value from 0 to the correct summary value, using your great method of the fast summaries (which I have just recently learned). I then had to create the $x and the $y by looping again through the possible dates and extracting the value from the key. Take a look. It's the "GatherData" script. Since charts need all possible axis points, I would usually recommend a summary table to run and add a record for 2018 Mar even if the amount is 0. But the JSON object is a good substitute, especially using the (amazing) fast summaries method. Inspections_JSON.fmp12
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.