Andrew Winters 2/16/2015 1:34:49 PM
@Slava - Here is my scenario: I have a "Contacts" table that is master to multiple other tables -- "Phone Calls," "Events," "Documents," etc. This works well as the user can open a contact and view all the activity per that contact by type. However, each record in these slave tables can also be a billing event. I would like the user to be able to create a bill with a view that selects a contact and a time period. This view will list each billable event by contact all mixed together so that it can be sorted by date, and modified right from that screen. It can then be printed or emailed to the client as a bill with the total time spent during the inputted time period.
I have experimented with a couple of alternatives but none have been entirely satisfactory. One is to lump all the slave tables into only one table and choose type as a column. Form behavior will then open only the fields relevant to that type. This is clunky though and requires the user to take extra time with every new record inputting the type and waiting for the form behavior to load. The other alternative, that I am working on now, is to leave the slave tables in place and add another table called "Billing." Any record opened in one table will use rules to open a "Billing" entry that will be a slave to the original record, using lookup to transmit the information. I now will have all the information in one table and can view the altogether. The downside, though, is the records is this new table can't be edited directly. So if the user is a preparing a bill, and wants to make a tweak, she has to work back to the original record to make the change.
Hopefully this is clear. Any comments are appreciated.