all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Blue
|
|
||||||
|
||||||
|
|
|
Notes:
|
|
-The receive invoice page needs some pagination. I ran it the other day and it had tons of invoices show up. -I learned something again that I already knew. However, re-learning it will hopefully make it stick. We added a number of new columns to the dynamic PO/invoice line items table. What a pain to validate and cross validate between the main and the line items. It doubled the amount of work required. Basically, we have duplicated data on the main and line item (on purpose) to help with look-ups and searches. The normal process is the main holds the data (the 1 one) and the line items only contain an id to look-up the data on the main. This is a perfect 1-many relationship. If you duplicate the data, the process gets more complicated and you have to make sure that the main still controls the line items. Before: (invoices – line items/1-many), (line items – parts/ many-1) – normal 1-many. Now: the normal options still exists but there is also a new option (invoices – line items/ 1-1 and line items – parts/1-1). This new option is not recommended unless you have a reason and this relationship is just for searching. Here are the values that we added to the PO/invoice table: - The main is on the invoice table (customer_id) - New calc total (extended_tax_total) - The main is on the parts table (inventory_type_id) - The main is on the invoice table (invoice_type_id) - The main is on either the PO or invoice tables (main_paid_date) - The main is on either the PO or invoice tables (main_paid_switch) - The main is on the parts table (part_category_id) - The main is on the PO table (po_received) - The main is on the PO table (po-type-id) - The main is on the parts table (unit_of_measurement_id) -The take away is – only duplicate data if you have a reason, otherwise leave it as a 1-many relationship. |