all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Yellow
|
|
|||
|
|||
|
|
|
Notes:
|
|
Multi-corp, multi-location, daily/weekly report: 1. Most of the info is on the po_invoice_line_items table that we need. That table is currently one of the biggest and fastest growing tables in the entire database. I would love to split it in to it’s own table on a per corp basis. 2. The new table would need to be created via code and get a dynamic name. Say: po_invoice_lines_117 where 117 would be the corp id number. 3. If you split tables it does a couple things… both good and bad… 1. The application should run faster with less to join and less to filter. (Thousands of records compared with millions of records.) 2. Cross-corp or multi-corp becomes a little bit harder. 3. This switch may lead to watcher tables that could contain all corps on one table with grouped data. 4. The underlying SQL would have at least one more dynamic variable (slightly more complicated) but would be very easy and straight forward. 4. We are headed towards location specific watchers and grouped totals. That would speed things up tremendously. 5. We need to add possible three to five (or more) columns to the existing tables. They are: (found in scan in photo gallery) 6. If we switch to separate tables… it will require some clean-up reports, new code, and some changes to be cascaded throughout the system. However, in the long run… this will make the entire application run smoother. 7. What if we did the migration all in one clean-up process. 1. Select a corp… 2. Create a new table… 3. Run through all PO’s per corp… 4. Run through all invoices per corp… 5. Back to the top and start over 8. We need to check code and make sure to update histories, and subs of subs, and all inv sub (connected to payments) line items… Any other connected tables. 9. Update the corp web service calls from the add_edit_corp_action page. See the corp-wide settings page for valid code. Small bug. 10. Before posting files and going live… make sure and double check flow and reports locally. Lots of new changes. Test, test, test! 11. Test for the existence of the dynamic table before starting a cart or a PO. 12. Include the table setup in the add new corp pages. 13. On invoices… I set the po_received flag to 1. I thought that could help with ordered status and/or ghost invoices. Kind of an extra play flag. |