If your number of navigation (or general menu) items is both static and large, then you're going to have issues with keeping the solution well updated. One of the biggest downsides of any complex FileMaker solution is the growing number of layouts and layout elements you'll have to manage. Filtering with JavaScript/JSON is one of the most powerful ways to present data in both an efficient and faster way.įinding your FileMaker solution is feeling slower as time goes by? You need the content covered in this video!
#Baseelements plugin file modified how to
To this end, you must learn how to replicate the native portal filtering feature. In most cases, your portal is only going to show a fraction of the number of fields found in its table. In this video, I show how portal filters really work and how to address the issue of a portal used for a very simple selection process. Without careful consideration of the user interface, and how features are presented, it's easy to create a solution which starts to lag over time. Most commonly, it's the result of cumulative features compounding to make your solution slower and slower. There is, however, a point where you start to solve so many problems that your solution starts to slow down and you find yourself wondering why.
#Baseelements plugin file modified software
Need to make your portal filters faster? This video will likely have the answer.ĭeveloping software in FileMaker can be such a joy when you're able to solve so many problems so quickly. The trick is knowing how to make it happen with the tools we have available within FileMaker. You can optimize that portal filter such that the fewest number of CPU cycles are required in order to show a user's desired results. You ask yourself "Is there something I can do to make this faster?" and you find this video about Fast Filtering Portals. Your once wonderful complex filter, which was working just fine on the 1,000 records, now chokes to death on the 10,000 records in the real world. Until you hear feedback like "It takes forever to simply see a list of people to pick from."Īs you scratch your head wondering why things got slow, it's likely because you didn't think about what's happening on every record of that simple little portal. It's fast and efficient and you're guessing users will just love using it. When you first develop your FileMaker solution you're typically dealing with sample and/or test data. You may even find out that your primary key fields are actually able to index more than they really should! In this video I break down exactly how you can see what is going on with each specific field index and what the true difference is between a value index and a word index.
an unindexed one becomes somewhat obvious - the search may be slower than expected - it's the fact that every field, by default, can optionally enable its index that makes things interesting with regards to file size and, to a certain degree, some efficiency. So, when it comes to field indexing, you might not know the default settings could potentially cause your solution to become bigger than it should - without any benefit to performance. This is because working in FileMaker is like picking up a blank canvas and having someone say "Go for it! Paint something."Įssentially, you need to know what the tools are, how you use them, what can be accomplished and how certain decisions might affect you. When starting out with FileMaker, there's rarely the situation where you receive any "before you get started" advice.
0 kommentar(er)
