The parameter page is fully functional, the code in the parameter page has been cleaned up, the server and request handler files were cleaned up, i.e. removed old unused functions and old commented out code. Next step is to move the delete button from the grid to the header and have it delete the selected item. I will also implement the memory store for the group and product pages.
The parameter page delete button has been removed from the grid and placed above the grid.  The grid seems to work flawlessly. I also changed the way it interacts with the server.  When a new item is added to the db, the db returns the added item, I take the returned item and put it in the store. The remove function uses the Object id to remove a parameter now, which is better than referring to other fields.  The more I implement the store, the more code I seem to be able to remove.  It is getting close to where I can picture the grids modularly.  I could create a grid class as a wrapper of the dojo grid with my own functions.  Then I'll just use that class for each of my grids.  I didn't complete any of the tasks assigned yet today and they will surely take most if not all of tomorrow.
The Parameter page has been cleaned and redocumented.  Most of the unused and debug code has been removed.  The user can again get the properties of parameters from the grid to insert into the definition text box.  This is done by selecting a property from the grid and clicking the 'Get Property' Button or by double clicking the property in the Grid.
Parameter app overhaul completed.  All grids now operate on memory stores.  The pages are uniform and server communication is fluid.  The addition of the memory stores simplified server communication.  Note that the Family page requests the entire database on load and stores the data in a global store.  Then for each grid, data is queried from the global db store.  The group and individual pages are not yet implementing this feature.  They still do numerous requests from the server.  Further testing is needed.
All pages now implement using a global store that possesses all of the db collection data.  Each page has a feature to display the definition and its parsed output by hovering over a computed field.  When a PI that is referenced by PGs or PFs is removed from the DB, that referenced PI is simply dismissed in the PGs or PFs that reference it.  The only interaction with the server is when the full collection is requested, then when any item is added or removed from the server.  Testing to come.
small parsing changes made.  If a property that is s acquired is null, it places an empty string in the output.  This will happen if the user attempts to acquire a unit field and the unit field for that PI was never defined.  The unit field is no longer required.  There are parameters like 'Cells in Series' that don't have units, it's simply defined by a quantity.
small bug fixes, the selected fields arrays of the PIs were needed on the group page.
The definition parsing of math equations has been adjusted to try one more evaluation at the end, just in case there is another lingering equation. It seems to work pretty well.  The user can double click the grid and get values from the grid.  If they want to do some math, they just need to separate elements by ';'.