On the CD-ROM: In the Stack Select Dupe folder.
Primary Database: Solution.fp5, layout TWO.
The Problem:A customer makes and sells all kinds of pumps. On any given invoice, a customer orders ten pumps at a time, on average. For each pump, there are 30 fields worth of customer-specific data that needs to be collected to customize each pump to suit the customer’s needs (some pumps pump sulfuric acid; some pump poop).
How to enter this data into a FileMaker database? Well, most in-house developers create the invoice form layout and then just make a huge portal with gigantic rows, each of which is made to accommodate 40-plus fields! Your life really starts to suck as a data entry clerk, especially with large orders, as you scan the portals, field labels, and fields, trying to sort through the information.
The Solution: A better way to do this is to use a screen with a portal, through which you create, duplicate, and delete line items. Data is entered by creating or selecting an item in the portal, which then populates fields on the form view outside the portal in an organized way. (Please see Layout Two of the sample database to get an idea of what we’re talking about.) Now, all you have to do is press the New Item button, and a new item, highlighted in your list, appears. Then you type in the fields, as many as can fit on the whole screen, outside the portal without all kinds of crazy scrolling up and down a portal or right and left on a list view.
Setting It Up
Now, create some relationships in the Invoice database:
Now you can put a simple portal on your form view using the “by Invoice ID” relationship, showing about ten rows. Put just the related Item [name] field in the portal and disallow entry to it; also, make it transparent.
That’s it! Now your users are ready to start adding items in an organized, pleasant-to-look-at screen. The only drawback with this method of creating line items in Invoices or Purchase Orders is that you can’t see all the items on one layout at the same time.
You can always create another display list layout, though. Also, if you don’t rely on on-screen buttons for navigation through these databases, a user could be looking at invoice 1001 with the line items for invoice 3001. When you fill in “g Line Item ID” in the Invoice database (the match field that tells you which line item to view to the right), it stays set until it is reset by your “Select Item” button, even if the user switches records using the book on the status bar, the keyboard, or the mouse wheel. This will confuse and befuddle people. Plan for it!
|
|
File Maker Related Tutorials |
|
---|---|
Management Information systems Tutorial | Software Engineering Tutorial |
Excel Data Analysis Tutorial | Unix makefile Tutorial |
File Maker Related Interview Questions |
|
---|---|
Management Information systems Interview Questions | Software Engineering Interview Questions |
File net Interview Questions | Data analyst Interview Questions |
Hadoop Distributed File System (HDFS) Interview Questions | Linux File Systems Interview Questions |
Excel Data Analysis Interview Questions | Asp Dot Net Database Interview Questions |
File Maker Related Practice Tests |
|
---|---|
Management Information systems Practice Tests | Software Engineering Practice Tests |
File net Practice Tests |
All rights reserved © 2020 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.