Filemaker pro 15 calculation fill full#

Otherwise you can 'transfer' the value from Symptoms::Description to Equipment::Description in one of two ways:ġ) Make a calculated field (or a text field, calculated value- you will have to choose whether or not to 'change' values once the field is populated) that is set equal to Symptoms::Description.Ģ) Check the value 'Look Up Value' and choose Symptoms::Description (I am in v9 right now, so I think this resides in the Inspector for v11). You can either use the actual Symptom::Description field (if and only if these descriptions will never change). Caution here: keep them very short and values aligned, or the user will have difficulty reading all the values.įinally, the Symptom description. **You can create a calculated text field that combines two or more short fields in your symptoms table and display the calculated field in the drop-down. You can display up to two fields (there is a 'trick' to display more below**) in the dropdown, while only the SymptomsID is indeed populated in the Equipment table. Check that box and choose the Symptoms table. The first item in the value list is to base its contents on another table. To make all these fields global: Select a field and, from, click Option. To render FusionCharts, create some basic fields such as chartType, containerid, chartWidth, chartHeight, dataFormat and dataSource and set their type to text. The Specify Calculation dialog box opens. The next step is to create a value list to populate the drop-down. Name the first field, say indexHTML and set its type to Calculation.

The next step is to create the drop-down list (in Inspector). So, if the descriptions will never change that delete it from the Equipment table.

Filemaker pro 15 calculation fill full#

In this example both the product ID and price should be copied to the invoice table because if prices ever change you don't want that reflected back into old invoices that were paid in full (at the old price).

The best example I can give you is a product information table (including product pricing) that is used for invoicing. Having the description copy over from the Symptoms table to the Equipment table is redundant (and not necessary) UNLESS the description will ever change. First of all, do you have a relationship from Equipment::SymptomsCode = Symptoms::SymptomCode? (I assume the answer is 'yes')