Sean sent me a text and wanted to jump on the GoToMeeting channel to go over a possible problem with pagination on the parts homepage. It looks like adding in the new snow owl datatables, new updates and changes launched last night, that the pagination messes up bulk add to cart options on the other pages (beyond the first page of multiple pages of search results). Basically, the datatables allow you to change the sort order and even limit certain fields showing up. If they change anything, it can put a parent item on one page and the subs on the next page. The code looks for the parent item stuff, if a sub is selected. Basically, if both the parent and the subs were on the same page, it worked. If they, the users, through different searches, filters, or pagination (going to the next page) they could make it break if the parent and the sub items were not on the same page together. This also happened if there were so many subs that the package that they wanted was on a different page. Anyways, small little complication and small little bug. We found a number of work arounds, but that requires training and education or experimentation.

After I finished with Sean, I got a call from Cory and then we jumped on the GoToMeeting session. Cory was relating some of the tech support questions and complaints that she was receiving. They, our clients, wanted more info than what we were showing them. We tried to trim some of the reports down and make it easier on the eyes. Our clients, depending on what they were doing, really needed all of the data and sub attributes and RFID tag data. Kinda interesting.

Anyways, we may need to go back and provide more options. Long story made short, we really need real client feedback and input. It is invaluable and muchly needed. As a side note, it keeps coming back to settings and even settings at different levels. We need corp or world level decisions, category level decisions, and even user or page level decisions. It keeps coming up and would really help to provide a solution or multiple solutions where the users are in full control of what they want to see and use and even how things act and play through. That is one of the things that we want to add in on the fracture project - full control of what they see, what columns, show/hide, sort order, naming, aliases, etc. Almost to full custom without making everything fully custom. Just base it off of data driven decisions or layered settings, permissions, and templates. That would be awesome!