i have made a various version for several languages that means i create 6 tables and corresponding line item tables to store the data separately.
my first thought is to combine all the tables into 1 so it is much easy to handle the summary report.
welcome to any approach. Thank you. i am using filemaker 15.
Definitely use a single table!
If you create a Language table, you can give each customer and/or invoice a foreign language key, then reference the appropriate vocabulary from a third table, where you can store words or entire phrases. With the correct setup, you can also easily have multi-language Product/Services names.
Ideally, you also only need a single layout for invoices and reports.
Try to think of the UI elements that you need in your layouts as another kind of data.
thank you, i am thinking of how to summarise the amount of each items of an invoice. My idea is creating a calculation field to calculate all items of an invoice. A summary field to calculate total amount of invoice with same client.
When i create a summary layout which is based on invoice line item table, the summary field works perfectly, but when i change the layout into basing on invoice table. The summary field could not work.
if i would like to create a report like
date invoice number total of each invoice settlement
That means i could not use summary field? i should use SQL to get the result? Also, how could i calculate the subtotal of all invoices of same clients. Thank you
summaries and reports are to be created in the line items table, not in the invoices table.
Thank you, is there any ways to create a reports based on invoices table.
Basically the idea is to summarize data in the table where the data is.
So if you want to see how many items of each type you sold, you'll do that in the lineitems table.
If you want to know things related to invoices, like breakdown of invoices per customer state, then you'll do it in the invoices table.
If you want a report with one row for each invoice with total(s) from that invoice in the row, you can get that on a layout based on either table. In either case, your summary fields would be defined in the line items table.
i set it in this way, but the calculation result of the summary field is not correct.
1 of 1 people found this helpful
To repeat, define the summary field as a field in the line items table.
If you have more than one occurrence of line items in your relationship graph, you must also select the correct occurrence when adding this line items field to your invoices layout.