Jump to content

Search the Community

Showing results for tags 'hierarchy'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Custom Function Library

Community Forums

  • Community Resources
    • Community Articles, Tips, & Techniques
    • FileMaker Marketplace Discussions
  • FileMaker Security Management
    • Security Concepts
    • Intellectual Property
  • FileMaker Server Administration
    • FileMaker Server 16
    • FileMaker Custom SSL Certificates
    • External Server Authentication
  • FileMaker Go & Mobile Strategies
    • FileMaker Go for iPhone & iPad
    • iBeacon Support
    • FileMaker IOS App SDK
  • FileMaker and the Internet
    • FileMaker REST API
    • FileMaker Cloud
    • FileMaker WebDirect
    • Custom Web Publishing
    • Other Internet Technologies
  • FileMaker Interface Features
    • Cards & Window Management
    • Interface Design Discussions
    • Layouts
    • Themes and Styles
    • Button, Popovers, Button Bars, SVG Icons
    • Tab and Slide Control Panels
    • Portals
    • Web Viewer
    • Conditional Formatting
    • Custom Menus
    • Value Lists
    • Tool Tips
  • FileMaker Schema & Logical Functions
    • Managing Scripts
    • Calculation Engine (Define Fields)
    • Custom Functions Discussions
    • FileMaker Query Language or FQL
    • Relationships
    • Charting
    • Remote Container Fields
    • Finding & Searching
    • Importing & Exporting
    • External Data Sources
    • Advanced & Developer Features
    • Reports, Printing & Publication
  • Brain Food
    • The Left Brain
    • Upgrading & Migration
    • Data Analysis
    • Development Standards
    • The Separation Model
    • Relational Database Theory
    • Damaged / Corrupt File Problems
    • OS Level Database Automation
    • Hardware & Networking
    • Bar Codes (Printer, Scanners, Software)
    • Accounting Solutions
  • FileMaker Discussions
    • FileMaker Pro 16
    • FileMaker Pro 15
    • Legacy FileMaker Platform Discussions
  • Geist Interactive Product Support Forums
    • Visit Geist Interactive
    • Visit Modular FileMaker
    • FMPerception
    • Generator
    • fmQBO
  • 360 Works Official Product Support Forums
    • 360 Works General Support
    • MirrorSync by 360Works
    • SuperContainer by 360 Works
    • ScriptMaster by 360 Works
    • FTPeek by 360 Works
    • 360Works Email Plugin
    • DocuBin by 360 Works
    • Zulu – FileMaker, iCal & Google Calendar.
  • FM Forums Affiliate Sponsors
    • SyncServer Pro by LinearBlue
    • Open Source Frameworks
    • Monkey Bread Software (MBS Plugin)
    • FileMaker Plug-Ins
    • ISO FileMaker Magazine
    • User Group Central - Sponsored by FMPug.com
  • FM Starting Point - By Richard Carlton Consulting
    • Visit FM Starting Point
    • FM Starting Point - General Discussions
  • FileMaker Classifieds
    • FileMaker Product & Service Announcements
    • Professional FileMaker Training
    • Services for Hire
    • Services Wanted
    • Solutions Wanted
    • Tools Of The Trade
  • The Water Cooler
    • Member Lounge
    • Wants & Wishes
  • FM Forums Operations
    • FM Forums Feedback & Site News
    • Site Instructions
  • FileMaker Platform
  • Forum


There are no results to display.

There are no results to display.


  • Samples
  • Solutions
  • White Papers
  • Plug-Ins
  • FMGo

Found 4 results

  1. Hierarchical Portal Filtering using FileMaker Pro 15 By Andy Persons Way back in 1996/97, I developed my original hierarchical portal filtering technique using FileMaker Pro 3. Twenty years later, we decided to take another look and update it for FileMaker Pro 15. Several alternate approaches have been developed in the interim for the hierarchical portal filtering technique (including a “lite” approach by my colleague Doug West). After reviewing them, we believe the original approach still has merit as one option to consider. Hierarchy Lite Advantages The Lite approach on the hierarchical portal filtering technique focuses on ease of implementation. It works to abstract the hierarchy logic using features like global variables and portal filtering, entailing fewer schema changes and requiring fewer changes after pasting scripts and fields. Download Doug West’s version of Hierarchy Lite Demo Hierarchy Classic Advantages The Classic approach to the hierarchical portal filtering technique uses a multikey in a global primary key field to filter records. This requires more work to implement and more schema changes, but can result in improved performance in certain circumstances such as high numbers of related records or WAN deployments. This is because records are filtered at the relational level rather than the portal filter level. Records that won’t be displayed simply aren’t downloaded in the first place rather than being downloaded and filtered after the fact. Leveraging New FileMaker Pro 15 Features We were also able to take advantage of several features that have been added since FileMaker Pro 3: Button Bars: the text for the Expand All/Collapse All button toggle takes advantage of calculated Button Bars Script Triggers: Indented arrows use repeating calculation fields with OnEnter script triggers to simulate “repeating buttons” CSS: allows us to hide the In Focus formatting of the repeating field to preserve the button-like behavior Download Revised Version Hierarchy Advanced 2.0 Features (coming soon) This refreshing of the original technique also sets the stage for more advanced features that we’ll be releasing in subsequent demos: Dynamic sorting by any field Drag-and-drop sorting and reassignment Stay tuned for Pt2 and Pt3! **This article is provided for free and as-is, use, enjoy, learn, and experiment at your own risk – but have fun! eXcelisys does not offer any free support or free assistance with any of the contents of this blog post. If you would like help or assistance, please consider retaining eXcelisys’ FileMaker Pro consulting & development services. About eXcelisys, Inc.: Founded in 2001, eXcelisys (www.excelisys.com) is an FBA Platinum Partner and FileMaker Certified developer organization. eXcelisys specializes in designing, developing, customizing, supporting, consulting, migrating, upgrading, fixing, and integrating of database solutions for Desktop, Mobile, and Web applications. Our core technology competencies are FileMaker Pro, FileMaker Go, and MySQL for database frameworks, along with FileMaker WebDirect, WordPress, MySQL, PHP, CodeIgniter, PostgreSQL, Joomla, Drupal, Magento, CSS, HTML5, and Javascript for web sites and web applications. Aside from providing eXcellent customer service, our goals are to use these technologies to intuitively automate your organization’s data solution needs seamlessly and flawlessly across the web, mobile, and desktop platforms. Contact eXcelisys today for a free estimate and consultation about making your business more efficient through intuitive and effective software automation. 866-592-9235 | info@excelisys.com
  2. Specific search script

    Hi every body I have ancestor database "test file" attached . I need a script that gives me theses search results: If I search for a single name, I want to find the records where the last field is the "single name" If I search for two names "Smith George", I want to find only records with the last two fields having the two names "Smith as the son and George as the father" If I search for three names "Smith George John", I want to find only records with the last three fields having the three names "Smith as the son and George as the father and John as the grandfather" Search parameters------------Output (result) John-------------------------------2 results : REC3 (George, Smith, John) and REC6. Smith George ------------------ 2 results : REC2 (George, Smith) and REC9. Smith George John ----------- 1 result : REC9. Thank you all test file.fp7
  3. Hi, I would like some advise on how to setup a database containing a (biology) taxonomy. I'll explain the idea. I will have a main table with information about a species and the taxonomy linked to this information. It's the taxonomy part that I'm not sure about what is the best way op setting it up. It contain species, genus, family and so on. (About 10 rank levels) After searching on the web I have the following ideas. 1. I make one table containing: ID, name, rank, parentID Then creating 10 (for each taxon rank) table occurrences relating parentID to ID. 2. Create 10 tables, one for each taxonomy rank with: ID, name, parentID and relate these also by parentID > ID. 3. I haven't figured out yet how this would workand what the advantage is, but I read about a join table used for a taxonomy ? So one table with name and rank and one with id and parentid ? One thing is that somethimes I will have a level in the taxonomy missing, for example, there will be a species name, and the next one will be a family name, so genus will not be used. This isn't a problem with option 1 as the parentID will be there. For option 2 that means I'll have to make an empty record (but with ID and parentID) to not break the chain. What option would you advise me to use ? Or suggesting another better option. ;-) I also want to make a single form to add a new species with the connecting taxon as easy as possible. Will these different options have a big influence on this or does it require a fair ammount of scripting anyway ? I hope you can help me selecting the best setup for my database.
  4. I think I'm constructing a Rube Goldberg-esque solution to my problem. Here's the application domain. I have a table of records that correspond to patent applications, which are commonly referred to as matters. A matter can claim (but does not have to) immediate priority to one and only one other matter. However, more than one matter can claim priority to the same matter, and a matter that has matter(s) which claim priority to it can itself claim priority to a matter. When a matter claims priority to another matter, this means that the former matter is of lower priority than the latter matter. I realize this is confusing, so here's a concrete example that I've been using for testing purposes. Say there are seven matters A, B, C, D, E, F, G. B and C claim priority to A, and are thus of lower priority than A. D and E claim priority to B, and are thus of lower priority than B and A. F and G claim priority to E, and are thus of lower priority than E, B, and A. For what it's worth, I created another table called priority, which lists two matters, the matter claiming priority, and the matter to which it claims priority. So, in the example, there are six records in this new table, one for each priority relationship. In hindsight, this is perhaps not needed, since in my main matter table, I could simply have a matter refer to another matter to which it claims priority. Now, the problem. Per the concrete example listed above, the result of matters claiming priority to other matters effectively results in a hierarchical tree. I want to list all the matters that are in the same tree -- that is, all the matters in any priority chain. So, regardless if I start at matter A, B, C, D, E, F, or G, I end up with the same list of matters. Here's how I've done this. I have a first script that finds the highest priority matter in the tree. So, if you started at A, you're OK, because A is the highest priority. But if you start from E, say, it would find B as being of higher priority, and then finally find A as being of highest priority. That is, regardless of whether you start at A, B, C, D, E, F, or G, you always end up at A. Then, this script calls a second script that recursively calls itself. The second script has a parameter that is a current matter. It locates any matters that claim priority to the current matter. If there are any such matters, for each of these matters the script calls itself again, to determine whether there are any matters that claim priority to these matters. This recursion continues until it locates all matters that do not have any other matter claiming priority to them. This indeed works as expected. Once we get to A in the first script, the call to the second script passing A finds B and C. For each of B and C, the second script calls itself. When the second script is operating on B as the current matter, it finds D and E, and when operating on E as the current matter, it finds F and G. What I don't like about this approach is that there is a *LOT* of searching going on. But it does work. The idea is that once I get all the matters in a family -- i.e., all of A, B, C, D, E, F, and G -- I can list these applications in a layout, and long-term, call some (external) tree building tool appropriately to create a visual representation. Critically, though, a user is just going to specify at most one priority relationship for any given matter, that the given matter claims priority to (and thus is of lower priority than) another matter. From these priority relationships, then, I need to figure out the family of matters.

Important Information

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