Search The Adilas.biz Developer's Notebook
Time Period:
Daily (enter the day you want to see)
Monthly
Custom Date Range to
Template Filter:
Color Code:
General Text Filter:

(use a plus "+" sign to separate search terms. ex: jack+jill+hill)
Sort Value:
 
Adilas.biz Developer's Notebook Report - All to All - (735)
Showing 150 of 735
Page 1 of 5 :: Go to page ::
Photos
Time Id Color Title/Caption Start Date   Notes
No po photos available. Click to view time details.
Shop 10912 Meeting with Steve 3/19/2024  

Working with Steve and Suzi. They are planning a demo site for a dog care (nails, baths, grooming services) business. Going over processes, routes, settings, processes, etc. It ended up being a small planning and consulting type session. Suzi does a great job and is very organized. Once we figure out the flow, we plan on passing that info over to Chuck (designer) to let him work his magic to help design a custom skin or mock-up.

One of the things that we may end up doing is adding a button to the element of time to allow a pet to be assigned. We are handling all of the one-to-many pet to owner details in flex grid tie ins. That's working pretty slick. We just need to populate that data around a bit more to help it show up correctly.

Another thing that we may need to do is a popup builder to show services that can be added to an invoice and also pushed over to an element of time to help the attendants to know what is scheduled, needed, and what was done per appointment. We went over some options.

After Suzi left, Steve and I jumped back in and went over other stuff. We talked about merchant processing. We went over some database updates that Steve is working on for invoicing time and sub timecards (job costing stuff). As a side note, Steve was mentioning that adilas is starting to sell some bookkeeping services along with the main system or main product. That's awesome. All part of what we want the adilas marketplace to do, speaking towards the future.

Steve also requested that we start working on the known issues report to help Mike out. This is a list of things that we have identified where things could go off the rails. Things like duplicates, certain dates that are out of order, mismatch between main and line items, sub inventory issues, etc. We have a page called known issues where we are listing all of these possible gotchas (data problems). It would be really cool to start working on some small reports to show those pieces that may have issues.

 
No po photos available. Click to view time details.
Shop 10874 Meeting with Cory 2/12/2024  

Started out doing some emails and recording some notes. Then meeting with Cory and Shari O. Looking at a small convert to PDF error on data 1. Other systems seemed to be doing fine. Just a problem on data 1. We also looked at a possible error out in statement land and math dealing with tips. Also in statement land, we had a request to apply a data filter to what was going to be on the statements based on amounts owed (paid or pending invoices).

We then spent some time looking at payroll settings and checking code on bit bucket (code differences between old and new code). We couldn't find anything that really stuck out. We then went and tried it on a play site, and it worked great. Cory is going to check the settings for the company in question. Also dealing with payroll, Cory and I jumped into a couple of state websites and pulled new tax and withholding tables and formulas for a couple of states. We need to update those values inside of adilas.

Lastly, we went over some priorities and talked about other projects. I've got the top 3 priorities written down in my notes on my computer. They are checking some older bad data for a report dealing with sub inventory, helping Bryan with the custom project to connect PO's to elements of time, and updating some state withholding formulas. We also know that a custom data import is coming towards the end of the week. Busy times.

 
No po photos available. Click to view time details.
Shop 10878 General 2/10/2024  

Email to Wayne about ways to improve or fix the tables for storing sub inventory attributes and parent attributes. See attached for a copy of the email. It has some light plans on how we could change the columns on the custom_text table (and other custom attribute storage tables - numeric, text, date, and json).

Fixed the error messages and moved the unique id/error code to lower on the error message. Trying to make it look better. Wayne just added the unique id/error code a couple of days ago.

Started to work on an advanced search page that shows parent items, parent attributes, and sub inventory attributes, all on the same report. Bryan originally made the report. Just going over things and lightly cleaning things up. Refining some of the logic.

 
No po photos available. Click to view time details.
Shop 10854 Meeting with Steve and Alan 2/8/2024  

I joined the meeting late, but Alan and Steve were going over SG&A costs when I got there. They have a client that is wanting to virtually plug the SG&A numbers. Steve was talking about how that is playing with fire and not good accounting. After that, Alan gave a small demo of his production and advanced recipe/build process for sub inventory. It looked great and had lots of heavy client-side JavaScript stuff going on.

We covered a bunch of topics. Here are some small notes that I picked up from the discussion. No specific order.

- Steve and Alan were discussing settings and adding more settings for production and manufacturing.

- Steve was asking for input on direction, on the sales side of things.

- Alan was proposing some industry specific skins to help with sales.

- Alan was also saying that we should circle back around and build out more reports or even dashboard level pages to show all of quick data, counts, and totals. He was saying, we should stick to our name - Adilas - All data is live and searchable - stay true to that slogan. Along with that, we were talking about some places that still need some help and a little bit of loving. Sub inventory was a big topic along with other histories.

- Steve mentioned that he is working on some job costing options and reports. Tying in expenses, invoices, deposits, PO's, and time cards to elements of time (the job or projects).

- Small observation - both SG&A costs and job costing are dealing with deeper tracking of sub pieces and components that make up a bigger thing or item. Kinda interesting. That's some deep terrain and more than just simple inventory tracking. It's a mix of operations being tied into accounting.

- There have been more requests for more charts, graphs, and eye candy type stuff. At one point, we really wanted to do some graphical homepages to show and highlight some of that data. We have all of the data. It just isn't presented in an eye candy and easy format to see and look at.

- Alan is thinking that people (our clients and users) are going to be looking for more and more efficient ways of doing things and tracking things. There seems to be a draw or trend towards efficiency.

- We spent some time talking about AI stuff (artificial intelligence). That is a big buzz word right now. What if we redid some of our homepages (made them more graphical) and helped to show trends and month over month, year over year tends and patters. That could be really cool!

- We talked about the history homepage and how it shows a great overview of what was done or worked on throughout the day. That is some great information and a great daily summary of what happened in the system. Steve was showing that piece to a perspective client and they were super impressed.

- Back to AI stuff. We may use some verbiage like, we do such and such, similar to how AI works, without actually saying that we are using true AI. We already do a lot of that type of stuff. We feed data in, we then train the system to do certain things with it. As we go along, we can see areas that we could work on and turn our interface into a more AI oriented type product. We're not that far off, even right now.

- More talk about comparing patterns, comparing trends, and showing business intelligence (BI) level stuff.

- Mike, would like us to work more on the backend accounting pieces to help round out the system. Mike is a CPA that Steve has been working with for years.

- We could gain a lot, even on the virtual AI level, if we started to build out reports that show the known issues. We have a whole page that lists places and scenarios where things can get off the tracks or in the ditch (virtually). Date problems, number mismatches, disconnects, cart before the horse stuff, etc. That would be super cool to get those pieces built into the system.

- We circled back to sub inventory and possible ways of fixing things up there. We would love to add part id's, part category id's, and other key attribute id's to help the retrieval be faster and smoother. We can get the data in, it's the getting it back out that makes it a little bit harder (current database relationship structure). Anyways, some talks about ways to sure things up and fix some of the underlying pillars in the system.

- Quite a bit of discussion about Biotrack and Metrc (state compliance systems). We spend a lot of time and money trying to keep these connections up to date and working correctly. It's a moving target. We also want to pass on some of the costs to our clients and users.

- Our clients have some great ideas and tend to tell us what they are wanting and/or needing. That is awesome! We just need to figure out how to charge them for those upgrades. Basically, who is going to pay for the changes? Sometimes that can get tricky - either way, it's still part of the game we play.

- Most of our clients want real-time data going back and forth (live - not batched or staged).

- Alan and Steve were talking about ways to simplify the current API connections.

- Light talks about what some of the other developers were working on.

- We would love to be able to bill for real usage and what features our clients are using.

- We keep seeing costs increase. This is costs to us, costs to our clients, and even costs that 3rd parties are pushing and/or passing on. Everything seems to be in a state of upward flux. Along with this conversation, there were talks about some of the 3rd parties limiting throughput and/or limiting the number of API socket requests without a price increase.

- We talked about changing some of the file names. Some of the pages started out as a cannabis related page. We are now making those things more general so that we can use them (the pages and features) for our other clients.

- Going where the money is (based on client requests).

- Steve wants us to quote/estimate some new code for a client. Alan was recommending that we break things into phases and stages. Good discussion on this topic.

- Steve is doing some high-end business consulting for some of our clients. Helping them make decisions and plan for the future.

- The last topic of the day was thinking and finding ways to harvest the services (service byproducts) that our clients want or need (adilas marketplace stuff). If we help our current clients, that is an avenue of funding that comes from inside vs having to get new clients. Basically, help them get what they want. Steve put it this way - make your choice and then build up that choice (meaning software choice and pushing that software further along).

 
No po photos available. Click to view time details.
Shop 10870 Meeting with a client 2/7/2024  

Meeting with the Cannapages guys over GoToMeeting. We started out by debugging an API call. We tried a few things. I then had to login to the client's site, flip some switches, and then try it again. They are pulling menu info, but we had to turn on some ecommerce settings to let the pages (API sockets) play through.

They also expressed a desire to get two more API endpoints for pulling sub inventory attributes (list of values) and parent attributes (list of values). They then take that data and loop over it to populate their menu forms. I sent an email out to Cory with an update.

 
No po photos available. Click to view time details.
Shop 10840 Meeting with Wayne 1/29/2024  

We have a client who wants to use the main adilas ecommerce site and do their own SEO (search engine optimization) and web stuff. Super advanced black box and dynamic page building for our clients and their web addresses. Basically, taking what we already have and adding a reverse look-up based on a SEO parent attribute. Then taking that dynamic data and building a special page to help with the SEO for the client. Light database talks and going over options. Drawing and going over sub inventory and parent attributes. Talking about possible bug on our local boxes for https and port numbers (test is different than the live sites).

 
No po photos available. Click to view time details.
Shop 10819 Meeting with Bryan 1/23/2024  

This never happened. We were going to talk about the advanced sub inventory search and simulating some bad data.

 
No po photos available. Click to view time details.
Shop 10810 Client meeting - API questions 1/15/2024  

Meeting with Mike from Cannapages (3rd party vendor) to see what they were missing on the API endpoint side of things. We found two main attribute lists (parent attributes and sub inventory attributes) that were missing. They can look-up the data and values, but they were missing the master list of what to loop over. We built a quick couple of pages (web forms) and pushed them up to data 7. We will build out the API sockets that go with these. That takes more time. This was just a quick band-aid. They should be good to go for tonight.

 
No po photos available. Click to view time details.
Shop 10793 Meeting with Cory 1/15/2024  

Meeting with Cory and Shari O. to go over projects and questions. Shari O. had a request for being able to sell stock/units and special fees and presets (pack or specific fees or collected values for each sale). We currently allow for 5 preset items to go along with the sale of a stock/unit. She was requesting 10 (increase it by 5). We talked about options, and I gave them a rough quote what I thought it would take. If the client was tech savvy enough, they could recipes. That is unlimited and could be easily configured to add multiple (unlimited) items to a sale (into the shopping cart) from a single button or click. Anyways, just a free option that already exists.

We spent some time talking about payroll and the need for other states, more HR (human resources) options, and deeper payroll/HR functionality. That would be awesome, and we'd love to add that in. It just depends on who is paying for it.

The other main topic was going over some new reports that have been requested. Both for sub inventory and more accounting level stuff.

 
No po photos available. Click to view time details.
Shop 10802 Internal tech support 1/11/2024  

Emails and light tech support for Cory. She needed some backend database values for a client who is using the API to do sub inventory reports. Reaching out to Alan to setup a time to meet and chat. He had reached out to me.

 
No po photos available. Click to view time details.
Shop 10797 Emails 1/10/2024  

Going over emails. There were a couple different chains that needed some help and loving. One was a chain dealing with one company's data and sub inventory reporting. The other was an email chain about elements of time and online scheduling functionality. I spent quite a bit of time there. I reviewed a video, took some notes, recorded some notes on element of time # 2249 inside of adilas. I then tied element of time # 2249 (progress on some of the time settings and online scheduling) to the original campground GUI interface document (element of time # 1532). I also uploaded an email with tons of good feedback, ideas, and even a requirements list for what a client/user said that it would take to get adilas up and fully competitive in the campground and hospitality industry. Really good stuff.

 
No po photos available. Click to view time details.
Shop 10795 Meeting with Bryan 1/9/2024  

Going over plans and research with Bryan. He would like to work on a new horizontal time view page. Instead of having people down the sides and times across the top (what we currently have), he would like to run locations down the side and days or dates across the top. Sounds great. We have some other ideas on elements of time # 8004 for more ideas on horizontal and vertical time or date views.

We also went over some feedback from Kelly and Cory on a report that was showing some data errors for sub inventory. Recording notes.

 
No po photos available. Click to view time details.
Shop 10740 Meeting with Cory 12/18/2023  

Jumped on a meeting with Cory and Shari O. Going over yearend payroll stuff and tax forms. We then got into a discussion on average costing and a thing called internal cost corrections (ICC). We have some of our older clients that came on (started using our systems) before we had sub inventory. Some of them are wanting us to add in either average costing options or be able to virtually update the COGS to match-up what has come in/out of the system on a per item basis. The best solution would be to get them to buy into and/or use sub inventory or parent/child inventory. Anyways, we were talking about some options.

 
No po photos available. Click to view time details.
Shop 10646 check code 11/13/2023  

Bryan and I spent some time working on a small fix for some of his Authorize.net code. We pushed up some changes. We then flipped over and did some more work on the data disconnect on data 8 for a client and their sub inventory reports. We went in and ran a number of test queries, made some actual code changes and pushed up the new code. Bryan sent some emails out to let some of the power users know and to go in and try it out.

 
No po photos available. Click to view time details.
Shop 10637 Meeting with Bryan 11/10/2023  

Meeting with Bryan. We spent the whole time looking at sub inventory data on data 8 for a single corporation. We are trying to look under the covers and see if we can see why two reports are giving different numbers. We ran query after query checking the data. We thought that it was dealing with our inner joins and left joins. We discovered some stuff dealing with how the relationships are made. Some of them are just plain one-to-one. Some are one-to-many, and some don't even exist. That makes it a little bit tougher to follow and get consistent info.

The crux of the problem seems to be dealing with the relationship between po/invoice lines items and sub inventory packages or sub ids. Anyways, we documented a bunch of the queries that we were running to keep track of our findings. Brandon has those queries on his local computer in a file.

 
No po photos available. Click to view time details.
Shop 10635 check code 11/9/2023  

Meeting with Bryan. Made a few small changes to fix a bug. Spent the rest of the time looking at data and trying to figure out why or what is going on for a data disconnect for a corp on data 8. We ran lots of behind the scenes queries to check po/invoice lines, parts, time sub inventory, and fiddled with different joins and filters.

After our work session, I was on a phone call with Eric talking about tips and a new data flow process that is coming down the pipeline. We went over a few questions and talked about some of the cause and effect trickle down as we change things. We made some plans to reconnect and work on it on Monday.

Spent half an hour combing data and looking at live data for a client. They sent us a CSV file with customer info and loyalty points on it. The data is kinda messy. We'll have to do some major gymnastics to really make it work. Light prep work.

 
No po photos available. Click to view time details.
Shop 10581 General 10/17/2023  

Emails and looking over some code that Eric was working on. His code was dealing with USAePay (merchant gateway) and showing options for switching between EMV/Chip readers and swipe/manual entry on credit cards. We have needs for both of those avenues.

Got a text from Cory asking me to jump on a Zoom meeting. We ended up adding in some special history logging on part category and sub inventory settings. We looked around for any bulk or global tools that may have affected our clients sub inventory template settings. We added the new code, tested, and pushed up code.

 
No po photos available. Click to view time details.
Shop 10576 check code 10/16/2023  

Working with Bryan on saving large files as CSV files. We were talking about session variables inside of the CFC's (ColdFusion components) and best practices. Bryan is going to rework some stuff and get back with me.

On the phone with Eric. We were going over 2 main topics. One was his new code for both EMV/Chip reader credit card transactions and normal swipe or manual entry credit card transactions. He has a branch that he wants me to look over. The other major topic was dealing with an import for a client that had customer info and customer loyalty points from a different system.

After working with Eric, I tried to track down a possible bug with scanning a sub inventory package or sub inventory number. It ended up being a setting that prompts for a specific sub weight. I turned it off and the sub barcode scanning worked great. We wanted it to skip that extra step. Just had to flip the right setting. No code changes took place. I reported back to Steve, Cory, and Dustin.

 
No po photos available. Click to view time details.
Shop 10565 Working on the scan cart 10/7/2023  

Recording notes from yesterday. Merged in some new code for the mini scan cart settings. The new link builder is done on the settings page. I also spent some time working on the popovers (bigger tool tips) for the cart. I converted all of the sub inventory attributes into a small popover that is hidden by default. It you mouse over it (hover), the icon, it will show all of the correct data. I'm hoping that will help make it look even more simple (layout wise). Pushed up new code.

 
No po photos available. Click to view time details.
Shop 10564 Working on the scan cart 10/6/2023  

Finished up the link builder mini app on the mini scan cart settings page. Started working on some larger tool tips for the sub inventory attributes on the mini scan cart.

 
No po photos available. Click to view time details.
Shop 10545 Pushing up code 9/26/2023  

Meeting with Bryan. We did some code review on some advanced sub inventory searches. Merged and pushed up code to data 8 for testing. We had to force a cap on the number of records that we would allow to be returned. It was timing out, if we left it too open.

 
No po photos available. Click to view time details.
Shop 10541 Working with Bryan 9/25/2023  

Working with Bryan on sub inventory reports. We took an existing report and worked backwards to figure out a better join and better query. We needed some grouped data, but it had to come from a specific table with specific criteria. We ended up changing out the SQL and the left join options. Deep database query stuff. By the time we were done, I think it looked pretty good.

After meeting with Bryan, I got an email from the Bear 100 data team. They would like to meet before the race this weekend. I sent them off an invite to an after-hours meeting on Wednesday. They have a request for me to help build a test page for their CSV files. They have some new CSV formats and they want a place to try them out before they go live or do any real database interactions. Sounds fun.

 
No po photos available. Click to view time details.
Shop 10518 Brandon and Cory projects 9/25/2023  

Zoom meeting with Cory. My main two projects this week are the new shopping cart and the Bear 100. We also talked about the public API and 3rd party solutions using either the public API or a special 3rd party API socket channel. We spent some time talking about the discount engine and figuring out a plan to launch the new code while still leaving the old code somewhat in place. We may have to go backwards and retrofit the old code to handle the new custom date ranges. We'll get it all figured out.

We looked at some sub inventory reports and sub reports based off of sub id numbers and other sub reports based off of the RFID tag number. Shari O. had a few questions at the end of the meeting. She was mostly just listening in to say on top of what is going on and happening. Cory got to show her a little bit of the new shopping cart. It seems like we are mostly on top of things right now. No huge out of control fires. I left the meeting and Cory and Shari O. were still talking about emails and clients. Good stuff.

 
No po photos available. Click to view time details.
Shop 10526 Meeting with Bryan 9/19/2023  

Meeting with Bryan. Looking over some new merchant processing code and logic. We made a few changes to the add cart payment page and merged and pushed up code on data 0 for some testing, after we had tested locally. After that, we spent some time going over data, steps, and processes for looking at quantities on sub inventory pages and reports. Small work session.

 
No po photos available. Click to view time details.
Shop 10458 Working with Bryan 8/24/2023  

Meeting with Bryan. He had some questions dealing with sub inventory and doing queries to pull back records. We ended up getting pretty detailed and looking at debugging info and then refining queries from there. Lots of sub inventory type stuff. That is a deep, deep, puzzle that needs some loving.

 
No po photos available. Click to view time details.
Shop 10380 Bryan part query and API 8/8/2023  

Working with Bryan on layout and style guide stuff. Code sign-off, merged, and pushed up some code. As we were working, I noticed a few things that we could do better on...

- We need to make sure that we don't have polluted data, especially on the testing and demo sites. We use them for so many different things and don't finish all of the processes. We end up with polluted data or incorrect data.

- We need more histories on things like sub inventory, parent attributes, corp-wide settings, and other high-level places. We have tons of histories on invoices, customers, deposits, parts/items, etc. We just need to add those other histories to the list. This would be a good thing for the fracture project.

- If we have a big mess, say in a demo site, and it needs to be changed - it sure would be nice if we had some bulk clean-up tools or system admin tools that were super high level but could help clean-up or change data in bulk. We may not want these tools available for normal users (could be a problem).

- Full visibility and full searchability - everything needs search options, exports, reports, and histories.

After Bryan and I finished up on some of the code sign-off and reports that we were working on, we switched gears and started talking about some location-based grouping of data. We ran out of time, but I gave him some small things that will help, and he was going to go in and play with those suggestions.

 
No po photos available. Click to view time details.
Shop 10379 Bryan report questions 8/8/2023  

Working with Bryan. We looked at some code and made a few tweaks to some of his reports and pages. We then switched gears over to sub inventory with location filters. Once you add locations into the mix, it complicates things. It goes from a one-to-one relation to a one-to-many relation. That then requires grouping, dynamic filters, and dealing with scale. Lots of talk about dynamics, deeper groupings, and how to sub filter grouped results. We also talked about getting good data and small control set to make sure we are getting what we want (known data in order to get known output).

 
No po photos available. Click to view time details.
Shop 10302 Cory and Brandon touch base on projects 7/10/2023  

Meeting with Cory. She had a question about using the find and replace functionality for a client. We actually did the find and replace and it worked slick. It did a deep flip flop and full find and replace including histories, line items, sub inventory, etc.

Next, we spent some time looking at some data questions. Looking into a payment search question and then into employee timecards and timeclocks. We used some existing tools and also did some queries behind the scenes to look at raw data.

On the phone with Bryan to go over tables, joins, and options for pulling in sub inventory. It can get pretty deep, if you are starting from an existing query or even a brand new query.

 
No po photos available. Click to view time details.
Shop 10308 Bryan push code 7/6/2023  

Meeting with Bryan to push up 3 different code branches. Light refinements on some of the reports and pages. We worked on PO's, sub inventory, alternate logos for invoices, quotes, and statements. We also did some PDF export stuff and more sub inventory availability options on some of the reports. Pushed up code to specific servers for testing.

 
No po photos available. Click to view time details.
Shop 10291 Merge and deploy updates for SpringBig time zone issue 6/29/2023  

Merging and pushing up code with Eric. After the initial work, we spent some time talking about data modeling. Here are some of my notes.

- Eric would love to do some more data modeling and taking things into consideration and making a plan. He used to do this for other companies that he has worked with and for. Great resource. We could really use his help with adilas lite or fracture. This was like a mini database and data modeling lesson of sorts. I was loving it and scribbling down notes as quickly as I could. Fun stuff.

- We talked about flex grid tie-ins, flex attributes, and parent attributes. Basically, things that he sees that we do that might be built out into more efficient tools and features. Maybe rework some of this and/or combine some of the features.

- What really connects to other things (natural relationships) or what things are forced together (forced or special relationships)? We may want to look at use cases and try to pull out the natural relationships. Then build your application according to those natural relationships. You may still need to allow the forced or special relationships, but those become the edge cases vs the norm.

- If something happens over and over again, this should be part of the core system. Currently, we do use a lot of flex grid tie-ins to help with some of these special cases. As a side note, some of these one-off features are becoming more normal and should have their own logic and tables vs putting everything into the flex grid tie-ins. Great tool for getting things started but eventually, you may need to build out specific tables, logic, and pages. Make it more normalized and more efficient.

- As a note, what does the flex grid do? It allows for one-to-one connections, one-to-many connections, add log notes to anything, tying things together (main id's to sub id's or main id's to other main id's), and it also allows for up to 30 custom fields. Once again, it can be on a one-to-one basis or used and setup as a one-to-many relationship. Here is a help file that has more info on the flex grid tie-ins.

- As a note, the flex grid tie-ins have been the big brother to the things we are trying to build called flex attributes or real in-line database extensions or real in-line extensions for short. Here is a small, older graphic link, of what we are trying to do.

- We talked about the bus to motorcycle project (datasource project or world building project). We are headed to a new model where the corportion id numbers (corp_id) will be left out per database. Each company will have its own database and thus may not need the corp id number. This deals with table names, joins, and data that gets stored in the database.

- Back to the flex attributes and a possible option to build them right into the main entities or high level tables (for the 12 main players or wherever we see fit to put them). This option has some pros and cons. We'll have to work this out. Currently, I'm really leaning towards something similar to what we did for the current flex attributes or parent attributes. Let them build and setup any custom fields that they need. Dynamic relational model. Just for fun, here is the progression - flex grid tie-ins (2009), sub inventory attributes (2015), parent attributes (2016/2017), flex attributes (2020).

- Lots of talk about data modeling and being able to take off the corp_id. Including on the end of corp-specific tables - for example: invoices_53, invoice_payments_53, time_sub_inventory_53, and a slew of others.

- Maybe break the pili or po invoice line items into two different pieces. It was joined together to help with inventory counts over time and across multiple locations. Anyways, we may look at separating those tables into multiple pieces. Super important, make sure to remember and include locations. If just a single location, we could do the architecture differently. However, with multiple locations, it gets a little bit more complicated or tricky. There are tons of other possible options.

- The payee table should be broken up as well. Currently, if a person or entitiy is tied to an expense/receipt, a PO, an inventory item, it lives in the payee table. Payees consist of users, employees, vendors, and special customers that had to get paid out of the system (a copy and convert process). Anyways, we may want to break that table up into users, vendors, and special customers (something like that).

- We talked about a concept called "attribution" and data normalization levels. There are two main types of data models. You have the logical data model and the physical data model. Entities and entities have attributes. Eventually, those entities and attributes get translated into tables, columns, and fields in a database. Often, most attributes become their own database column or field.

- Attributes are different than types.

- We talked about fields like "flag_for_1099", "password", etc. Those are attributes for certain entities. However, does a vendor need a password field, most likely not. Each field or attribute needs to go with the entity that it belongs with. We, at adilas, tend to mix and blend some of the attributes between different entities. In some ways that is fine, but it requires explanations, instructions, and training. It's not as easy to follow without someone to guide you along. Anyways, some good conversations about data normalization stuff. What goes with what and why does it fit like that?

- Make the names readable and logical where possible. We do a pretty good job on that, but there is some randomness in there as well. Along with that, we jumped into talking about a section called special accounts. We are planning on using that for gift cards, loyalty points, in-store credit, vendor credits, punch cards, and other special account transactions where we almost need a bank account style with a rolling number and being able to add/subtract using individual transactions or actions. Anyways, we have a few fields in there called dev_flag_1, dev_flag_2, and dev_flag_3. We use those flexible fields to help with certain parts of the process. In a way, we didn't know what we were going to need, so we added in some flex fields. Well, now, those flex fields have rules and hold certain data that could be its own column or field. However, because we didn't know what would be needed, the fields are somewhat mixed, depending on what is stored there and what kind or type of transaction record is being stored (loyalty points vs gift cards or whatever).

- The conversion trickled over into human reference fields vs computer identifiers, ids, or computer reference fields. They are different and play different roles.

- As you think things out, eventually you have to transform or go through a transformation from logical models to physical models. Eric kept saying that we should be shooting for the third normal form (data modeling and database modeling). Figure out the whole business world (plan it out as best you can) and then build out what you need, based on what you see and/or know.

- We talked about aggregates and data warehousing. I mentioned that I would like to build out tables for yearly per location, quarterly per location, monthly per location, weekly per location, and daily per location. We would also have the underlying transactions or transactional database tables (raw data that holds all of the data). The other tables would be what we transform the transactions into (a form of aggregates or business intelligence).

- Along with aggregates, Eric was saying that sometimes you can watch the database and see what tables, queries, and reports cost the most (data, traffic, or processing time/energy/frequency). You then build out aggregates based on those findings and/or known needs. For us, we've been doing this for long enough, we know a few places that could really help with speed, server load, and provide great BI or business intelligence levels.

- Our system has to go clear out to the full accounting level. That changes how we do certain things. That is awesome! Our sort of end goal is perfect accounting, aggregates, per day, per location, and per category. Some of those (category levels) vary but they have mostly been defined in the current system. That is huge. We have a plan, we have a path. We just want to refine it. Eventually year over year reporting, monthly by month comparisons, real-time data - all data is live and searchable (adilas).

- Snapshots, aggregates, different preset and controlled data levels. We may need current data (tables without any dates - assumption of current counts, values, sums, totals, averages, maxes, mins, etc.) as well as dated or historical data (tables with dates to allow previous or prior lookups and date driven lookbacks).

- What about enterprise mappings and cross-corp stuff? We need to plan that out as well.

- We also need to consider servers, speed, reliability, backups, redundancies, and how deep we going?

- Lastly, Eric could help with a ground up data model. We could pick a topic, break it down, and do a number of smaller sessions vs a big push. That would be too much. Anyways, great meeting and Eric could be a great resource for planning, checking out our decisions, and planning out the best course of action. Good stuff!

 
No po photos available. Click to view time details.
Shop 10077 Steve, Cory, Brandon-Catch up on projects and updates 5/29/2023  

Going over lots of requests for new and enhanced reports. Small errors and fixing a few things. Cory had a small list. Lots of talk about flex attributes and the need to build them out on all 12 main application player groups. Currently, we have them on customers and elements of time. It seems like the next one that is warming up is PO's. We have clients that are wanting to be able to add new and flexible data points to PO's (purchase orders). Of course, once they get added, they for sure want to be able to search by those new flex attributes. They also want them to show up on all the correct spots, forms, searches, reports, and exports. Not a problem, it just takes a goal and some time.

It seems that across the board, our users, on a global level, are wanting more and more control of their reports and exports. This inclues settings, preset and saved favorites, show/hide certain fields or columns, able to rename fields, set and remember the search criteria or filters, and be able to pull down any and all data (reports or exports).

Cory and I were talking about "visibility vs searchability". Our users want "visibility" first, then they want the "searchability". Basically, our users want to see the data and then be able to limit it and/or filter it down from the results that they got. From a coding side, it is easier to filter (control what will show) vs showing everything and then filtering after all of the data is shown and/or pushed out to the user (way more traffic, memory, and bandwidth). On the coding side, we would much rather have you know what you want, then we only have to serve up those records. Sort of a flip flop on who wants what and which way they approach their data and report results.

We have a report that the users want to control multiple parts of an object (say PO's or purchase orders) all from one export and/or report. Granted, the PO has multiple one-to-many relationships, table joins, and records that need to be matched up and presented. Imagine a report search page that has show/hide checkboxes for all of the main PO data (location, vendor, total amounts, PO types, dates, notes, ties to external invoices, etc. - 20 some fields). They then want all of the show/hide checkboxes to show/hide columns for all of the line item details (quantities, costs, prices, items, descriptions, etc. - tons of new fields - 60+ fields). Next, they want any sub inventory information (sub reference id numbers, barcodes, units of measure, special sub attributes, RFID tags, etc. - tons of other fields - another 15-20+ fields). Without going too crazy, they also want any new flex attributes (extra data points or in-line database extensions), parent attributes (inventory level controls for parent items), and other data. I didn't count, but it could be well over 100+ fields that they want to be able to pull, show/hide, filter, and organize. It gets into some advanced settings and big reports with lots of dynamic logic. Not that it is hard to do any of that, it just gets more difficult when you are mixing so many things or parts of the object together.

Cory wants us to start with the "visibility" of the data. As a side note, we may have to off load some of the processing for these bigger reports. I want to be careful about building on possible already tippy code or projects. We have to make sure that everything is stable. After this conversation, Cory and I lightly talked about budgets. We also looked over some code and did some quotes for clients. There are many challenges when trying to mix and bled and mix viewing with searching huge datasets.

Lastly, we talked about fair compensation. We are heavily underpaid and not showing our true value. That gets complicated as well. It's an interesting mix and an interesting game.

 
No po photos available. Click to view time details.
Shop 10163 Next project 5/24/2023   Work session with Bryan and I going over some light debugging on a project. We then switched over and spent the rest of the session talking about a new report and new sub inventory report. We are going to be calling it the super sub invoice line items search or report. That's a mouth full. Anyways, we did record about 38 minutes of the session, see attached.
 
No po photos available. Click to view time details.
Shop 10078 Steve, Cory, Brandon-Catch up on projects and updates 5/22/2023  

On with Cory and Kelly going over new requests for sub inventory reports. Kelly had created some spreadsheets and we were going over those pieces. Great review and we are ready to hand this project over to the developer. We switched topics and started talking about sales tax aggregates and creating manual switches to help force an update.

Cory and I were doing some planning for a server meeting and some decision making. We talked about doing some R&D on the new frameworks that Wayne is working on and almost doing a mini scratch app to get all of the kinks worked out. After that, Cory and I went over a number of other small projects and plans.

 
No po photos available. Click to view time details.
Shop 10137 Brandon, Kelly, Steve and Cory sub reporting- how to move forward 5/18/2023  

Zoom meeting with Cory, Kelly, Steve, and I. Going over plans for sub inventory reporting. I took a number of notes. See below.

- Kelly did some prep work and had a small spreadsheet- Here is the link: https://docs.google.com/spreadsheets/d/1gI92xKVgBeDA1Qnd0N5ygrYYjLdisNA2KDYYqodrQeI/edit?usp=sharing

- Some of the report settings need to be at the user level vs the corp or global level- for example: the new advanced part search settings. They are controllable at the corp level but not at an individual user level. We are seeing a need for deeper levels of control, per user.

- She, Kelly, found a good report (that still needs some tweaking)- advanced invoice sub line search for all item categories. The current report shows and does some sub attribute grouping (text based off of the names).

- Kelly thinks that a limit of a 31-day month (whatever the range) would work for now. For both PO line items and invoice line items. If they want to pull info per item category, no date range limit. If they want everything or "all" we limit it to a month or 31 days.

- Ideally, she would like grouped output for PO's, invoices, and items. That's where subs play (currently).

- Steve is working on some sub inventory reports right now.

- We have a currently working model in the advanced invoice sub line search. If the part category of "All" is selected, the actual search page shows all possible sub attributes as filters. We then pass that list of combined attributes over to the results page. The results page then loops over the combined list and fills out what it can. We may be able to use some of these pieces.

- As a side note, we actually looked over some code for the working model to see how it was switching, grouping, and pulling the data. For now, we may take that code and push it over to other sections as a patch and/or band-aid of sorts.

- The sub reports need all of the main line item details plus the sub information. Currently, the sub reports are only showing the sub details. Kelly wants all of the data out of the system. Cory wants to be careful not to get in trouble if we add a bunch of new columns (past history with clients complaining - changing their reports or exports).

- The reports homepage is kinda messy- We may need to rework that page to make it look better.

- We need sub attribute information on its own, parent attribute information on its own, and mixed sub and parent attribute information together. Along with this... We need these same reports for PO's, invoices, and items in inventory. We need all of these pieces. Consistency across those reports.

- Kelly is sort of stuck- helping out the clients. She is pulling tons of reports and piecing them together. She is looking for some time savings and better reporting, out of the system or out of the box vs having to pull things and piece them together.

- Up next, once we have the good reporting that we need, we can build in bulk update tools where you can see it, fix it, repull the report. Export it as needed. We need the visual representation of the data first (good reporting). The other features and tools will come later.

- Steve, Dustin, and Alan are going to be working on some bulk tools for subs.

- Be able to export beginning inventory, ending inventory, and what is in between. That's the goal.

- Kelly likes the super invoice line item search/report. Could we add on a bit there? That might be nice. We talked about creating a super sub invoice line item search (same as above with subs). Maybe a link to that new page from the bottom of the advanced invoice search page (maybe at the top as well).

- At the end of the meeting, Kelly was asking what we needed to get going. She is going to build out a spreadsheet with columns and instructions per column for us to use as a reference. That should really help. We will pass this on to the correct developer to help them know what is wanted and needed.

 
No po photos available. Click to view time details.
Shop 10150 Research 5/18/2023  

Research on sub inventory attributes and changes to sub inventory - over time. Started working on a document to chronicle the timeline and what we have learned over the years. Here is a link to show some of the entries that I was looking at.

 
No po photos available. Click to view time details.
Shop 10146 Recording Notes 5/17/2023  

Recording notes. Tons of ideas on sub inventory. See entries from 5/10/23.

 
No po photos available. Click to view time details.
Shop 10075 AZ Sub attributes 5/15/2023  

On a Zoom meeting with Kelly, Cory, Steve and I. We were going over a number of different topics. We started out on expense/receipts and logic on limited expense types per vendor. Kelly was saying that we should only limit things if we know enough information to actually limit things. There was an error where a vendor had been assigned to a single expense type, but then that expense type got made inactive. She couldn't get into the expense/receipt. We had her go to the vendor and remove the limit by expense type value and everything worked fine.

We then switched over to talking about sub inventory and sub inventory attributes (sub attributes). We spent tons of time and I took a bunch of notes. Here are my notes:

- Kelly went through things to find the gaps

- Parents and children are so separate - you have to know what goes where

- She started on the grouped inventory report (just shows counts from the parents).

-- She was hoping that those quantities and costs would be able to show the same values.

-- Investigating and auditing - Going deep

- Cost of sold adjustments - 2 sides on an invoice... one positive and one negative. ICC - internal cost corrections (future project) - cleaning up the dust - bulk tools are needed.

- On big reports, we need to look at the size, and maybe do backend data pulling and then showing data.

- She has to go to the usage on each one to look at what is going on.

- Accurate inventory values - this is a big lift

- She needs an extended cost per - cost * qty = extended. We just show the cost and the quantity, not the extended cost.

- Clients are saying that their reporting is way off.

- Disconnects between PO line items - parents and subs

- She was using Excel pivot tables to get super close details to what we were showing.

- Cost changes, rounding errors, some parents and some subs, negatives, etc.

- In order to find all of the possible problems, you have to get so deep in the usage and details.

- How do you help clients fix items, quantities, costs, and usage, etc.

- When auditing subs... it would really help to show which ones have which costs

- Part status - active and allow sub only - could be both.

- The knowledge level to do an audit.

- Multiple tabs open and pulling data at one time.

- Level of trust... - I could pull more data but is it even what I'm looking for?

- Pagination of the data - say 40 pages - I need it all summed up - with what was what... in/outs, cost changes, etc.

- In Excel, she had to do find and replace, build special comparisons, standardize the data, etc.

- She had to figure out what was off and then go in deeper. Basically, she would love to see the known issues or sub sets of the data. Maybe even comparing things and helping them find the issues.

- Some of the dates... in the past - you can't even fix something - How do you fix it without adjusting things going forward.

- It would be nice if there were alerts, notices, or somehow finding those problem children.

- It becomes so complicated that they skip it. It is very manual on the fully deep audit.

- Locking things down - ice-down dates - being able to lock/hide things. We need this on all of the main players.

- If there is a difference between po line items and subs, we could show the problems... all at once. Similar to the bank balance helper report.

- Read them and weep numbers - too bold

- Our basic user's comprehension is not very deep.

- There is a need for oversight, maintenance, etc.

- Helping all our users to know what the problems are. It seems like it is coming down to known issues and disconnects.

- The cost field is so important... we allow that to be changed. Kelly was saying, the cost runs downhill.

- We talked about the balance sheet homepage and that it should run a number of checks before it does it stuff, and/or we need to let people know that there is a possible problem (or problems).

- Talking about some other check fields (aggregated values) that could be held on the main to show problems, disconnects, or whatever.

- On E/R's and deposits, we allow posting and locking. Most of our PO's and invoices can lock lines, but never get to the posted level.

- We rely so much on PO's. We don't have a ton of control over them.

- People are looking for the easy button - things keep evolving and users are expecting the system to help them along that journey.

- More guardrails

- Huge need for aggregates, counts, sums, averages, maxes, mins, and other values. This is a huge need. Bigger than we can say... We are very good at getting all of the data (transactional level). We need the aggerate levels. We have so much data. We need to get it summed up and other aggerate levels.

- Controls - at all levels

- We have seen users create more issues trying to correct other issues... Tons of cause-and-effect relationships.

- Inventory that goes into the negative. Ideally, this shouldn't happen. If it does, we need to show it.

- Visibility - start here - helping our users see what is going on.

- Parent/child issues - looking for disconnects.

/////////////////////////

Switching over to sub attributes

- Kelly has a client that has sub inventory and existing categories and wants to re-categorize the inventory. Category to category moves, in sub inventory. This totally creates a disconnect.

- People want to consolidate their categories or break things into smaller categories. We didn't know that people would be flipping the categories. That's a higher level of flipping but it has cause and effect drop-down effect.

- Currently, all sub attributes are tracked on (or off of) the column number (not the sort order or name, literally just the column number), not the id number. This can make things go off the rails.

- Is there a quick solution? Personally, I think this is going to take some time.

- One of the biggest problems is - we can't get the reporting out that we are needed. Because of this, they start altering things to solve their need. That can cascade potential problems. They want quick reports, quick exports, etc.

- We need to be able to cross over categories.

- We think that we need a master list for sub templates. In Kelly's words, maybe build above it. Along with that, we may need to build on both sides, build above it (master list) or build below it (custom cross category mapping).

- Build and break - build and break - part of the cycle

- Steve was talking... what about the next version of sub inventory. What would this look like?

- What about bulk tools?

- Kelly's goal was to show the different sides of what we are learning.

- Software has to evolve! What is the next step?

- From Steve - It keeps feeling like our users are wanting the software to go to the AI (artificial intelligence) level.

 
No po photos available. Click to view time details.
Shop 10133 Brandon, Kelly and Cory discuss sub reporting 5/11/2023  

Zoom meeting with Cory, Steve, and Kelly. We were talking about sub inventory. Subs are great but do require more work and effort. Getting info in, out, reporting, and bulk updates and bulk tools. When we started, we didn't even know what was needed. As things unroll and unfold, we are beginning to see a bigger picture. That is awesome!

We have mountains and mountains of data. Now what?

As the meeting progresses, we spent some time talking about the challenges to sub inventory. Here are some of my notes:

- Sub inventory attributes and being category specific

- Settings all over the place - configuration

- What about changes, updates, and flipping categories (after the fact)?

- Possible mapping of categories, sub attributes, etc. Talking about mapping by id numbers and not names or column numbers.

- We need a sub inventory history section. Tables are already built, but they have not been tied in.

- Some of our clients want so much control

- Sub attributes, parent attributes, flex attributes, flex grid tie-ins, and other different levels or layers

- Master list of sub attributes and then repurpose those per category. This could be tied in with the mapping options listed up higher. Either start from the top (master list) and go down (what sub attributes are needed per category) or list out each attribute per category (current model) and then tie and/or map them back to a master type list. We may have to go in both directions. Just some thoughts.

- Kelly likes how parent attributes can be bridged over categories. Having said that, we need to be able to search by sub attributes, parent attributes, and flex attributes.

- Certain clients want to pull data without the category specific reliance. Basically, once we catch the data, we have to be able to let it be searched, pulled, filtered, shown, and exported. It's all part of the puzzle. Being able to get at and use the data. That's a huge key. Just being silly - ADILAS - all data is live and searchable

- Maybe upping the permission level to add/edit sub inventory or sub inventory templates or sub attributes. Once again, we need some histories of who is doing what in the system.

- Steve was talking about - 1. Capturing the data. 2. Then being able to get it back out (in any form - CSV, Excel, PDF, printable, web). and 3. Being able to play in bulk and deal with automation options. Those are some of the goals (small summary).

- We have people who are wanting to add certain sub attributes on the fly, as part of a sub process or sub phase. This gets into sub locations, sub phases, and sub processes and/or steps. Currently, we only show the subs at certain steps and make them go back to certain places to add/edit or update that data. There is a lot of manual work involved. How cool would it be if we could help them and let them setup their own processes, phases, and sub processes. Mini concepts of the data assembly line.

- There is a need for bulk update tools, easy flow processes, and being able to setup their own data flow based off of the subs or steps within a process.

- The use of templates to help control other actions, defaults, rules, and assignments. Having that example and/or template really helps answer a number of questions.

- We went back to the main need of being able to pull data out of the system (quickly and easily) - all data is live and searchable - We really need this and keep going with what we already have.

- Kelly and Steve working on advanced reporting and moving beyond a band-aid. What about going back and correcting the plumbing from the get go. Planning for the future.

- Need for more controls, handrails, and ability to scale.

- Build and break, build and break. Well, it's time to fix it again! it's breaking!

- What if we re-imagined it??? What would it look like? What things do we need to consider if we were to rebuild this out?

- Kelly was recommending that we get into a real life system to see the challenges. We made some plans to meet with Kelly again see the tools that she uses, how she uses them, and what is still lacking and/or needed.

///////////////////

This is more for me, but what are the next steps in the planning process for new phases, data assembly line stuff, and where do we want this to go? Help lead and guide it! Keep pushing for more bulk tools, bulk options, and bulk tools to add, edit, update, change, pull data in, pull data out, etc. We can do a bunch of things on a one-by-one basis, let's keep pushing that to the next level. Yee haw!

 
No po photos available. Click to view time details.
Shop 10123 Brandon troubleshooting 5/10/2023  

Cory and I going over projects and assignments. Sub inventory reporting and getting into system wide aggregates. We also spent some time talking about supporting our team members.

 
Click to view time photos.
Shop 10085 Adilas Time 5/4/2023  

Great morning meeting. Eric and Sean started out and were touching base and coordinating on a big demo and a big feature release. They were planning release times, testing times, and fall back plans if needed. I thought that it was really good. They were also talking about different servers and plans per server, based on the demo and the extra functionality. For the demo, they may script it and use an outline (direct links) and/or screenshots of the two different pieces, in case we don't get everything all merged together before the demo.

Sean and I switched gears and were talking about SG&A costs and using expense/receipts (E/R's) vs PO's and capitalized inventory. Sean kept waking up last night and wrote down a number of ideas on a Word document (see attached). We went over the Word doc and drew pictures, made notes, and talked about options. It was just Sean and I, but we beat it up pretty good. See attached for some of the notes.

Here are a few of the notes, beyond what Sean had pitched (once again, see attached).

- E/R's is where it all starts. Maybe just keep it there vs going clear out to PO and capitalized inventory levels.

- E/R's already have a normal date and a due date. The difference between the two is already a built in date range - how long to track the life cycle of each E/R.

- In Sean's notes, he was talking about to the exact minute, second, etc. We will be sticking with a daily value to keep it more simple. Most likely, it will be scheduled at a certain time so that we get consistent results, it can handle weekends, holidays, and becomes a built-in procedure.

- I liked his idea of flagging each SG&A vendor with a special flag. That will help us treat expenses from that vendor in a different way.

- If we run it through the E/R side of things, it will be very minimal effort and input from the user. Most of it will be done and distributed behind the scenes.

- Inventory still in place, keeps get hanger costs. Once it sales, that hanger cost stops and it gets recorded. Otherwise, it is sort of in a state of flux.

- If we get to the tightest level that we are thinking, it will add value for owners and managers to see what it costs over time to keep bigger on hand inventories. Being able to see past what is on the shelf and what that costs. Pros and cons to different inventory stocking models.

- If we hang (add hanger costs) to an E/R, we could reference (key word reference) the PO, invoice, item, sub item (sub inventory), etc. It doesn't add any weight to the current flow, it would just be a reference to those other pieces and/or items.

//////////

After Sean left, John and I were talking about some server stuff. I mentioned to John about getting him a higher percentage of adilas (as a co-owner) than what he currently has. He's playing an important role and doing server stuff, backend code, as well as frontend design stuff. I think that he is doing a good job. We will just keep refining things and playing well with others.

We ended up talking about servers, moving hardware to a new section within the Hostek environment. We also talked about internal developer training that is coming up, subjects, topics, and ideas. We really want the developers to virtually own or have ownership of and for their projects.

 
No po photos available. Click to view time details.
Shop 10109 Kelly, Brandon and Cory talk about high level report settings 5/2/2023  

Zoom meeting with Cory and Kelly. The whole thing was dealing with inventory reporting and an advanced report builder concepts. Kelly wants to throw-out a wider net and see what we can catch. Instead of going super deep to financials, she wants us just to focus on the invoices and PO's. Basically, an inventory and CRM (customer relationship management) mix. Leave the accounting alone right now (for these reports). Just help our clients get their data in and out quickly. Basically, it's operations stuff.

One of the goals is to show, teach, and allow our clients to use a mix of vendors, customers, invoices, PO's, inventory items, sub inventory, parent attributes, and location information as needed. All of these things interact on both the sales and customer relationship (CRM) levels.

Here are some my notes from the meeting:

- Talking about building a report building engine. This deals with groupings, filters, show/hide columns, sort orders, etc.

- Kelly was talking about getting to the meta data of the database data (going deeper). What is related, how does it work, what can I get out of it - including mixing things that a company and/or individual is looking for? Even things that we can't think of and/or thing about. Extracting those data analytics and details out of the system. Lots of value there.

- Be able to export to CSV, PDF, and web formats (normal HTML or data tables).

- Ideas about display options - Nested groupings, even pulling and storing data in temp tables, data dumps, and then querying that data. ETL - extract, transform, and load - manipulate the data however we need to. Leave the raw data alone, just tweak out other pieces or tables.

- Show all of the tables and their fields. Preset a few things so that the defaults are showing (not everything is checked by default).

- Use the data tables, be able to save the reports, see new reports from the saved favorites, all kinds of advanced report building options.

- Put this new advanced report builder engine under its own new permission.

- Thinking about vertical tabs (for a layout view). The tables or basic system players would be the left most side (left vertical tabs), the right side would show other settings per table. For example: Say the tabs down the left were things like vendors, customers, invoices, PO's, parts/items, etc. Then when you click on the different tabs, it would show which fields belong to what table (on the top of the page) and then the filters and grouping options would be below that. When you are done, you click to view the report. You could also save a new report name, set the sorting or sort order, and who can see it (assigned to who or just a assigned to all option).

- Help educate the users on the database structure. This could be a great side agenda item for this advanced report builder engine.

- Kelly was asking - Is this new advanced report builder a value add-on? How do we monetize it? We decided that for now, we'll just roll it in and try to sell it as a feature of the whole or bigger picture.

- We talked about sub inventory attribute mappings and creating groups (things or attributes that can cross over categories). This is a form of layering for the sub attributes. Basically, each item category can have any number of sub attributes. We then go in and allow a user to setup groups or which sub attributes are buddies or tied to other sub attributes in different item categories. Making small or mini family groups for the sub attributes. Just an idea to help with reporting and consistency.

- We won't build this in yet, but we have to think about things on an enterprise level. If we build this advanced report builder engine on the corporation or basic world level (where we need to start), it won't be long and some of our bigger multiple world level clients will want an enterprise level solution for the advanced report builder engine. We know that is coming!

- Along with the enterprise level, we know that some of our clients really want the business intelligence (BI) level of reporting and aggregation. It's a known need. That's a whole other plan and topic.

- There may be versions and phases of this report builder engine.

- I was asking about big reports and possible timeout issues. We may need to show sample data and then build out the bigger (in needed) reports and then let our clients know that they are done or finished. Some of these reports could potentially be millions and millions of records. As a note, I know that Wayne was working on something similar to this a few months back. I'll check with him on ideas for timing, flow, and notifications.

- We may want to build in options for details (default level) and/or aggregates groups, sums, counts, etc.

- If you are wanting to get more money from people, it really helps if the people that you are dealing with want the same things (that you want). It creates a common want and need.

- In a nutshell, this project would be mixing and blending all (maybe not all) of our existing advanced search features into one bigger master report builder. Because this project could get so big, we may end up playing around and building a mini version and/or a prototype of sorts.

- We talked about timelines and even ways of distracting our clients to buy some time. All of this takes time and resources to plan, build, and deploy.

- As an addition - it would be really cool if we had some presets (pre-maid selections and choices) to help people get started. That would make the building process simpler. We could show some defaults and then let them modify that vs building from scratch every time. This idea came from Aspen (my daughter) who was listening to the meeting while working on other stuff.

 
No po photos available. Click to view time details.
Shop 10072 Working on SG&A costs 4/26/2023  

Working on the SG&A costs settings for the shopping cart. Quick phone call with Alan to go over the logic for auto pulling sub inventory behind the scenes. He had worked on a project for transitional invoices that did some of that sub inventory package manipulation stuff.

 
No po photos available. Click to view time details.
Shop 9990 Steve, Cory, Brandon-Catch up on projects and updates 4/24/2023  

Cory and I going over different projects. One of the new things that needs to be done is some new code to help with emailing invoices as PDF's. Currently, we send emails with links to web based invoices out in ecommerce. We have a client that has to get their emails as a PDF invoice. Anyways, we talked about needs for that project and being able to automatically email clients who owe us money with the PDF invoice, be able to save it, attach it, and also do a clean-up routine for keeping things tight on the server. We talked about some new settings to make all of that happen.

Along with our conversation, we were talking about being able to do these things asynchronously so that the user doesn't have to wait. Also, as a side note, if we did this, our client would be happy and Shari O. would have an easier time. She does all of our billing stuff.

We flipped over to recipe/builds and a custom report that mixes elements of time, recipe/builds, flex attributes, and inventory planning. We made a small bug fix for the USAePay EMV chip transaction stuff. After that, we spent the rest of our meeting going over custom report requests. It's amazing what people want to search by, group by, and what things they want to mix and blend onto a single report.

As we were talking, Cory had the idea of building a big robust report builder that allowed for all kinds of stuff. Basically, a smorgasbord with options, filters, and such. We then put that power in the hands of our users and let them go at it. In rough terms, it will be let them pick and choose, save it, run it. That would be really cool. We also talked about linking and mapping things internally for sub inventory, kinda like family groups for sub inventory attributes. What are they paired with, how are they related, etc.?

The last subject was dealing with mapping, relationships, groupings, and aggregates. Everybody wants all of the data (details) but they don't want to have to wade through it (sums, counts, maxes, mins, averages, etc.). Those are the aggregates. Everybody wants sales data, inventory, and sub inventory data.

 
No po photos available. Click to view time details.
Shop 10011 Adilas Time 4/24/2023  

Spent the morning with Steve brainstorming on SG&A costs (sales, general and administrative costs - ways of accounting for expenses as inventory). We decided to start with hidden line items on the invoice level. Playing with the law of deferring to other pieces that have more information. We do that all the time.

Here are some of our notes:

Meeting with Steve

- Mike said that we need to break things down into the smallest pieces (units of 1)

- Steve and I were talking about 5 decimals of accuracy.

- We will need some rounding error buckets.

- Like an item on a shelf, it will collect dust. We just track that dust.

- Vendors, Part Categories, Parent Line Items, Sub Inventory Items, and SG&A costs over time

- Deferring and going back up the chain

- If we go with hidden line items on an invoice. That could get heavy over time.

- We could also just use a whole other table that just references the invoice number. It’s tied to the invoice but not physically hanging on that invoice. Just a sub table that could be traced back to the invoice but doesn’t hurt any other pieces of the existing invoice.

- Folding it in (meaning the costs), and to what level

- Steve and I were talking about some of the math… sales, costs, expenses, etc.

- Steve already has an SG&A homepage. He/we could add some other settings.

- Here is Mike’s formula – monthly sales? Total SG&A? What is still in inventory?

- Steve is thinking about adding in some new settings – maybe total monthly sales, estimated SG&A per month, how many days are you open per month, what is the parent item that we will be adding as a hidden line item? On/off switch for SG&A costs with hidden lines.

- Figure out the fraction or percentage of the total. Use that number.

- There are a number of variables. Eventually, we could pull in that data, but for now, we may want to set some simple fields and fake it a bit.

- We need to build it out and automate it. Add the hidden line item to all invoices behind the scenes. We can’t add SG&A to transfer invoices.

- On adding in subs… we may need some logic to help us roll over between packages.

 
No po photos available. Click to view time details.
Shop 10059 Bug fixes and data clean-up 4/18/2023  

Small data fix for Kelly on data 34. Had to fix some sub inventory attributes for a PO that had been voided but had sub inventory on it. We did some back and forth via text message and we got it all figured out.

After that Cory had me look at a custom PO label that needed to be fixed/tweaked for a client. The barcode was missing a small piece and thus not scanning the number that we wanted for the sub inventory package. The number was right, it was just missing the "~" for the sub package or sub id number. For example: Say it was sub id ~34, the barcode was only scanning as 34. On the phone with Cory, made the small fix, and pushed up new code. Also sent the update to John and Steve to push into master. My local box is still kinda broken.

 
No po photos available. Click to view time details.
Shop 10048 Working on sub inventory reports 4/5/2023  

More sub inventory stuff for Kelly. Worked on the advanced sub item searches for PO line items. Lots of work and changes to exports to Excel. Pushed up new code and did some testing. Let both Cory and Kelly know about the changes.

 
No po photos available. Click to view time details.
Shop 10047 Working on sub inventory reports 4/5/2023  

Working on the sub inventory availability filters for advanced item searches and data exports.

 
No po photos available. Click to view time details.
Shop 10037 Data clean-up for a client 4/4/2023  

Back on the data clean-up project. Actually writing the update code. Finished up all but the subs. Came back later and got all of the sub inventory updates done as well. Two different sessions. One from 5:15 pm to 7:00 pm and the other from 8:30 pm to 9:15 pm. Total of 2.5 hours for these two sessions.

 
No po photos available. Click to view time details.
Shop 10005 Adilas Time 4/4/2023  

Steve and I were going over sub inventory attributes. We got into all kinds of attributes. We talked about sub inventory attributes, parent attributes, and flex attributes. Currently, each section or attribute does a specific thing. There is a growing need for more or better sub attributes and parent attributes. Easier to get things into the database for storage and easier to pull the data back out. I mentioned to Steve that we would really like to add a few fields and values to the current sub inventory attributes. They are things like: part category id, app type id, main id (tied to the part_id), and sub inventory attribute id numbers. We have some of those columns but there has not been a project to standardize things yet. It's still on the wish list.

Quite a bit of talk about new corp-specific tables and data storage. Evolution... everything is evolutionary... look and feel, logic, business flow, and even sales (how we sell our products and services). We will keep working on making it easier and easier to use. SG&A costs (selling general and administrative costs) and going clear out to the financials. To the client, it is just data storage. To us, we have to make it all flow and work together as a system. Sometimes that's a challenge.

As recap - for sub inventory attributes or sub attributes:

1. Add the part category id as a look-up value (this would be a new column)
2. Add the main part id as a look-up value (we could use the column called main_id to hold the part_id - it would work perfect)
3. Add in the correct app type id as a look-up value (we already have this column but don't use it for sub inventory attributes - we just need to use it and tie it in better)
4. Add in the associated sub inventory attribute id number as a look-up value (this would either be a new column and/or repurpose an existing column that is not being used in the custom_text, custom_dates, and custom_numerics tables).
5. If we do change things here, we may want to go through these tables and rename fields and values. It was originally created for a specific project and then used over and over again for other semi related projects. Now that we know what it will be used for... we should take the time to future proof it a bit.

If we could add these fields and/or data points into the sub inventory attributes, it would be so much better for getting the data back out of the system. Currently, things are tied to the sub inventory id or sub reference id. We then look that up to figure out the part id and then use the part id to look-up the part category id. It would duplicate a little bit of data but it would make it so much easier to find things and quickly reference things. Currently, we have to join multiple tables and go virtually up and down the chain to find everything that we need. I would recommend that we do a special project, add the above, do some clean-up and then move forward. That would really help. Just my two cents.

 
No po photos available. Click to view time details.
Shop 9926 Adilas Time 3/30/2023  

WordPress was down and this caused our main website to be down. I contacted Chuck via text, then a phone call. Sent emails to Wayne with some instructions and suggestions from Chuck. Trying to get things figured out. Luckily, you could bypass the main website and do a direct login by changing the URL (web path) to the login page.

Jumped on the GoToMeeting session and was having audio problems. Cory had some questions about the adilas label builder and getting images pulled in. Kelly needs some sub inventory reports. Some of that gets pretty dynamic and pretty deep. After that, John and I talked about our WordPress site and getting our stuff off of an outside content management software package, WordPress. We couldn't get ahold of either Wayne or Chuck to get help. We need to get some documentation from both or have John help with that documentation. Our eventual goal is working towards standardizing and using best practices for all of our developers. Constant processing of pivoting, updating, and changing to fit and fill our needs.

Chuck was able to meet with me and I jumped back on the GoToMeeting session. John jumped back on as well. We were trying to fix the WordPress stuff for our site. Chuck was helping John try to navigate to a certain file folder and make some changes. We kept running into issues. Cory jumped on and we made a quick fix for her on a cross corp invoice to PO transaction (special cross corp page). Once we finished that up, back on with John going over plans and what not.

 
No po photos available. Click to view time details.
Shop 9996 Working on known issues list 3/29/2023  

Recording notes and working on a list of known issues. See top_secret/secure/known_issues.cfm for more information.

For fun, here is a list of some of the items listed on that page. This list originally was started in 2009. Small list of what are known problems. Some of these things are real problems and some are just warnings. Lots of things have changed since then. It may need to be updated, added to, and some of the items removed, that have been patched, fixed, and/or finished.


  1. Invoice pmts on account with something different than 0.00 value.

  2. Receipt pmts on account with something different than 0.00 value.

  3. Reimbursements (rei's) with a bank assigned on the receipt pmt.

  4. Invoices with mismatch between main and line items.

  5. Deposits with mismatch between main and line items.

  6. Receipts with mismatch between main and line items.

  7. PO's with mismatch between main and line items.

  8. Non verified payments (outstanding deposits and checks).

  9. Duplicates ???

  10. Dates prior to the corp start date or prior to the bank start date. See bank_balance_helper.cfm page.

  11. Dates in the future. see bank_balance_helper.cfm page.

  12. Internal invoices that are not marked as paid.

  13. Receipt payments that are verified but the main is not verified.

  14. Difference between invoices and stock numbers. Created a number of flags to show disconnect.

  15. When paying back splits and rei's - what about both (main and subs) being assigned to income statement expense types? This could double things up on the income statement. Defaulted special multi build (rei and splits) to b.s. items for expense types. Still possible problem on original e/r that may get assigned to the balance sheet.

  16. Update PO's not tied to a balance sheet item (say a loss account or something).

  17. Lien payoff line items on invoice with a 0 cost. The cost and the price should be the same otherwise it puffs up the profit. Did run a report at one time to fix this. Also added code to the cart to match cost and price for lien payoff stuff.

  18. PO payments that have the wrong date and thus the po_paid date is wrong. The system was using the current date as the payment date even if the payment was actually made in the past. Small disconnect between actual payment date (e/r payment date and PO paid date).

  19. Check auto dates that are actually used in I.S. reports or B.S. reports. Need a way to manually change the auto dates if really being used. Check the unit payments, PO payments, other system made payments. The system seems to be ok, the problem is with dates and being able to either set the date when using or edit the date if defaulted to today's date.

  20. Blank expense/receipts (payee_id = 1).

  21. Voided items but part of it is still in play or not fully voided. Need to get to a voided list quickly.

  22. Denied check requests on payables page.

  23. Sales tax problem with work in progress invoices. They don't show up on sales tax reports until they get flipped back to a customer invoice. The problem is that the date (main invoice date - if not moved forward) will not show up on the next month’s tax reports. If this happens, the invoice will fall through the cracks and not be counted for sales tax. Possible option for sales tax, Steve thought that it might be cool to have a point and click interface that we physically pay taxes on certain invoices. That way, they never fall through the cracks and we only pay taxes once we collect the monies. This would also help with a system-maintained b.s. item for accrued sales tax. As an update, Eric was working on a sales tax aggregate project to automate this.

  24. Along with sales tax problems, how do we show this on the balance sheet? We need to show collected, paid, and owed values. Once again, Eric has been working on this in his sales tax aggerate project.

  25. Payroll has similar problems with regards to what has been paid on, what is still needed, and how do we show this info on the financials.

  26. See idea in note book about showing all daily transactions. This is different than a history transaction record. This is what really hit in and out on this day in time according to the system. This is not a known issue but may help with finding issues. Daily monitoring of each account per location, per day, per account or category. This would be awesome.

  27. Check for master/slave relationships between date changes. For instance main invoice date compared with invoice line items dates. PO main date with PO line items date.

  28. Known issue with PO dates. Do we run off the main PO date or the PO received date? Need to standardize. Leaning towards PO received date.

  29. Known issue with location based payables. Both expense/receipts and deposits have the location on the line items not the main. This means that monies could potentially get split between stores which would alter bank balances if only part of the money went in/out of the bank. Known problem here. Solution might be that banks are what they are (full monies in/out) and all sub lines and types are location specific. This could give a false indication as to how much money was available for each location.

  30. What about transition invoices that have the main invoice date overlapping the transition (wip/qti) invoice date range. They don't show up anywhere other than on the main invoice homepage which doesn't tie to anything. Added a small fix on view_transition_dates.cfm page. Still need to check for possible mismatches.

  31. Disconnect between sold date on units and invoice date. This is a disconnect that is unmonitored and will only show up if pulling a sold report (units) and an invoice report for the same time frame.

  32. When backing up the main bank start date, there is a problem with expense payments and deposits that have a date before the main start date and a verified date after the main date. The payment or deposit date is not counted but the verified date is. I had the same problem with Leanna in Poncha and with Drew Middlemiss doing his first bank statement. What a pain. See the bank_balance_helper.cfm report (5/16/09) for small fix. Still a known problem with a starting bank balance not being 0.00.

  33. Advanced pmt on invoices (pre-paid). They hit the bank because they were deposited but they also need to show up as a liability to offset the deposit or cash going up. This should be a system maintained item.

  34. What about deposit types of other income that are assigned to invoices (double counted)? The default is an invoice hits the p&l and only deposit line items that are under other income and revenue adjustments hit or the p&l.

  35. What about bad debt? Do we want to create a system maintained items for this?

  36. What about deposits that are made before pmts are posted to invoices. This is not backward compatible.

  37. Know disconnect between PO dates. The main PO date is currently used as the main search date. The PO received date is the main b.s. date. We are thinking that the main date may become somewhat of a request date or a age player only. The main date will become the received date with the received flag.

  38. If a check request gets approved and assigned to a bank but never written out (bank never sees it), there seems to be a problem. There is also a problem with older check requests and the dates that are set in the background. They are uneditable once the request changes into a normal e/r.

  39. Known issue with i.s. (income statement) deposit types. If used, without an invoice, they don't show up on the income statement. They may also be double booked if on an invoice and also recorded as other income or revenue adjustment.

  40. What about payments made on a PO before it was received. This could happen with a request PO or a basic PO that has not yet been received.

  41. What about inactive (status) on parts and subs. If we have details (activity) but something is inactive, that could cause problems.

  42. Levels of inventory - this could deal with parents, subs, and usage details. We may need to check costs, quantities, dates, etc. Sub inventory was added way after 2009 (original date of this report). We may want to spend a whole session just going over sub inventory levels and possible pit falls.

  43. Steve, Kelly, Molly, and others have lists of balance sheet challenges and other known issues. Check with them and get their lists.

  44. Ecommerce and what plays into the real mix from there - invoices, taxes, costs, prices, discounts, payments, quantities, elements of time, etc. Good questions? Some of this is already figured out, it just needs a little bit of loving.

  45. What about aggregates (somewhat new for us and just barely getting rolled out) and making sure things match up. Category (could be whatever), by day, by location - are there update processes that may be ran to keep things up to date. Manual updates, API sockets, watchers and feeders.

  46. What about backorders? Steve did a whole section on backorders but I'm not sure if we tied in everything to the balance sheet and P&L. Anyways, may need to circle back around.

  47. What about banks that get turned on/off (active/inactive). If we go back in time, we need to know if they were playing.

  48. Same is turn with location. If they get turned on/off (active/inactive), we need to know when they were playing. We may need a start and end date and then be able to pull things accordingly, even if the current state or status is inactive.

  49. What about cost of goods sold on unlimited or special line items? They should be a $0.00 cost because they are unlimited (like a labor or a service). If a cost is needed, it needs to be allocated through an expense to the COGS section or distributed in a thing called SG&A costs. SG&A (selling, general and administrative expenses - aka accounting for general costs by attributing them to a single unit and thus incorporating the true costs into an item). Basically, you take a normal expense like the electric bill or rent and build it into the individual cost of each unit by unitizing the expenses and virtually spreading a bigger general cost to smaller pieces. Sometimes that type of process (SG&A) is required for certain manufacturing and/or production type products. Basically, they (the IRS) don't allow you to expense off the whole expense (rent, insurance, waste, electric, etc.) as a bulk item. It has to be distributed to each smaller piece. If you do real SG&A, it helps assimilate those costs in smaller percentages and thus passing on a truer look at real costs of goods sold.

  50. Anything that is currently marked inactive but may have played a role at some point. This could be locations, banks, part categories, items, vendors, customers, etc. Often, if we make them inactive, they don't get pulled (but maybe we need them at some time in the past).

  51. Other special account options such as in-store credits, vendor credits, punch cards, etc. We already have loyalty points and gift cards that use special accounts. Maybe expand on this and allow for custom options or other digital payment accounts or payment solutions.

  52. I'd love to map out all of the existing balance sheet and P&L values. Make it more widely known and really put it out there. Right now, it all happens behind the scenes and is kinda like a magic box. I'd love to get it all mapped out and presented to the public. We'll get feedback, refinement, and maybe even some other really good ideas. That's my vote, let's get it all out there in the public eye and public realm.

 
No po photos available. Click to view time details.
Shop 9981 Brandon and Cory projects 3/27/2023  

Cory had a list of project that she wanted to go over. We both reviewed a small video from Kelly dealing with needs to be able to search sub inventory status and sub inventory availability. Basically, some new filters may need to be added to some of the advanced reports.

 
No po photos available. Click to view time details.
Shop 9923 Adilas Time 3/27/2023  

Cory and Steve were going over labels and sub inventory stuff. Mike Roundtree joined in and was asking about Herbo payment solutions and options for demos. I mentioned to him, if needed, we could help him out by using special accounts, inside of adilas. We will check to see what is already built out and then go from there. Anyways, he has some needs and ideas. We'll see where it goes.

Next, Mike was talking with Sean and Steve about ecommerce, multiple locations, using a single system for multiple different tasks, and making plans for a new demo site for somebody in Hawaii. Shari O. will spin up the new site, Sean will help fill things in, Cory will help Sean where needed. Fun to see them all making plans and coordinating. We also pulled in Bryan briefly to talk about the Herbo (eXPO) payment solutions and what has been automated and integrated. The demo is out a few weeks.

Shari O. had some questions on a bulk inventory update that needed to be done for a client. She and I made a plan and she will be kicking me over an email to get it in writing.

 
No po photos available. Click to view time details.
Shop 9982 Data clean-up for a client 3/21/2023  

Various different things. Small data fix for a client and their costs of goods sold. Flipped a bunch of costs to $0.00 for unlimited items. They had a cost associated with those items and it was throwing off the balance sheet. Part way through, I noticed that some of the items on my list were actually real inventory items tied to sub inventory. I stopped and made some notes. I called and left a message for Cory.

Did some emails, light tech support, text messages, and finally heard back from Cory. I jumped back on the data clean-up project and only modified the unlimited items. Light backend database updates and changes for a client. Little clean-up project. Sent an email out to Cory and Shari O. with notes on what I ended up doing.

 
No po photos available. Click to view time details.
Shop 9977 Brandon and Cory discuss projects/bugs 3/20/2023  

Prep work and checking out a reported bug/issue on the time-picker. It actually wasn't a bug, it was just forcing the users to play clear out to the minutes and seconds, based on some settings.

Cory joined and we spent some time catching up and talking about projects and issues. We talked about it and we will take off the time-picker for most of the pages that allow for user time inputs (files like add new timecard, clock in/out for users, edit timecards, customer logs, follow-ups, and both main and sub entries for elements of time). We did a search and it only looked like a few (20+) pages that need to be edited.

As we were talking, Cory gave me a few other small projects that need to be done and finished. She will send me some emails with more details, but it sounds like a data clean-up for a client that had the wrong cost of goods based on manual changes. There is also a request to add a few new search filters to a sub inventory PO based advanced search. We went over a few other projects and requests as well. Cory and I finished up around 11:30 am.

I then started working on the project to remove the time-picker from certain files. I uploaded new code to all servers and let Cory and Shari O. know about the update. Small work session.

 
No po photos available. Click to view time details.
Shop 9858 Add in a status flag for EOT's 2/2/2023  

More work on adding in the sub special status filter to the advanced time sub flags and tags search. I had to alter the search page, the results page, the backend logic, and the export to excel pages. After that, I switched over to adding in a fix to help prompt users to setup sub inventory templates when attempting to add/edit sub inventory. If everything is setup, it just flows through. If it's not all setup, it lightly prompts, with a message and a link, on how to set it up correctly. Light little bit of loving for that sub inventory functionality. Merged and pushed up files.

 
No po photos available. Click to view time details.
Shop 9842 Quote potential projects and troubleshoot with Cory 1/25/2023  

John, Shari O., Cory and I were on the meeting, at least at first. The three of them were chatting about mobile responsive webpages and options and costs. We know what we want, and our clients know what they want, but there is a huge cost barrier to really do it correctly. We have an internal website/system with thousands of pages, and each one is different. That's a challenge and would cost multiple hundreds of thousands of dollars. Even if you had the best team in the world, it would still cost up in that neighborhood. Big project.

Cory and I jumped in and did a small quote session and were going over requests and new projects. One of the new projects really wants to have us speed up access and reporting for sub inventory stuff. We would love to do that and are willing to share a cost with the client. Cory and I chatted about options and things that would help us get the data quicker and more standardly for certain reports. We also went over a number of other projects and upcoming feature enhancements.

 
No po photos available. Click to view time details.
Shop 9546 Adilas Time 11/14/2022  

Steve and Sean were on going over new custom label settings that Steve was working on. He is doing tons on the labels and tying in everything to dynamic page settings. He had a few questions about version control (Git stuff). We got him all squared away and headed in a good direction. Next, we chatted about upcoming online scheduling settings and where to go next with those pieces. Bryan and I are making some good progress. I was doing some drawings and showing the guys where we are headed and what some of Bryan's new setting will do for unique calendar events and being able to book those from online or ecommerce.

Steve was talking with a lady and virtually gave her a small demo just by talking to her over the dinner table (concepts and principles). The lady loved the concepts of what we are trying to do and how it could help make things better and smoother. Basically, I think that people do like what we are doing, they just expect it to be done and ready to pull off the shelf (walmart style) where it looks nice, has a set price, and you can just pick it up. We will keep heading in that direction, but the reality is, it takes time and money, tons of settings, permissions, and even custom pieces. We are really going in a great direction. Keep going!

Shari O. and Danny joined the meeting. We did some light sub inventory training with them. Sean was chiming in as well. We've got some great team members. That is awesome. Hopefully we can all keep learning together along the way.

 
No po photos available. Click to view time details.
Shop 9595 Working on 3rd party error logs 11/10/2022  

Two different sessions. One from 4:45 pm to 5:45 pm and the other from 7:45 pm to 8:45 pm. Both were dealing with the same thing.

More work on the 3rd party error logs. Working on the add/edit sub inventory template section. The add new sub inventory template was pretty easy. The update method got a little bit harder as we needed to monitor what changes. This particular thing (piece of data) gets submitted in bulk and we only wanted to record changes if something really changed. We had to do some comparing between old and new and then flagging what had changed. Finished up this round and pushed up files into the master branch.

 
No po photos available. Click to view time details.
Shop 9590 Debugging session 11/5/2022  

Hours of emails, tech support, and other stuff. Emails to Wayne, Cory, Kelly, etc. Going over validation stuff, routines, logic, fixing small bugs, and looking into sub inventory data and attribute mappings. On a Zoom session with Kelly, Wayne, Dustin, and I. Looking over code and testing things. Kelly even pulled a client onto the meeting to get some approvals and have her do some live testing. Pretty deep session.

As a side note, if all is going well, the value of the systems admin person doesn't seem that important but when all things go crazy and he/she helps to get it back in check, the value of that person is huge. They are often overlooked when seas are calm and the wind is not blowing (which means that they are doing a good job). Lots of unseen efforts. Thanks Wayne!

 
No po photos available. Click to view time details.
Shop 9521 Server meeting 11/2/2022  

Today's server meeting started out pretty normal and ended up in a small work session and trying to figure out how to modify some code for sub inventory. We started out and John reported on his yearend tax forms (W-2's and 1099's). We got a small report on the changes to the email server that Wayne is working on. We are excited to see if we can gain some more control and/or options there. We then switched over to the bug in the sub inventory stuff. This doesn't happen all of the time, but when it does, it throws an error.

Anyways, we spent the next hour or so going over different levels of pre-validation, in-line validation, and post-validation. Sometimes the problems can be stopped before they ever get going, some can be stopped once an error or 0 record count is hit, and some need to be soft or conditional errors that don't do something but allow for other things to still take place. For example, the soft errors may need to happen in a complex loop or nested loop. You may not want to just stop on a dime. You may want the loop to finish and then show problems or gracefully roll past any problems or issues.

Anyways, it got pretty deep. We will end up going in and looking at each page and decide what the best option will be. There is no quick solution for this issue. We may have to check and change code in hundreds of pages. Each one has a different task or function or flow. The quick answer is to just change it at the method level, but this same method is used in tons of places and in different ways. We will just have to chip away at it and/or watch the logs and only fix the pages that show up on the error logs. Once again, it only happens every once in a while and not all pages that use this method have problems. We have to track this one down using manual processes and time reading over the code before the method calls, during the call, and after the call.

To sum it up, it all deals with general error handling and making it more consistent. We are in a state of constant refinement. We will just keep working to make it better and better and smoother and smoother. I will note that we never would have found this error if it weren't for Wayne's monitoring and error logs. Basically, it allows us to look under the covers and catch things that a normal user would never report to us.

After everybody else left, Cory was talking about testing and making sure that we are only pushing up good code. Wayne told her that we push up code everyday, multiple times a day. That is totally true. She only knows about it if it goes bad or has an error or bug in it. Anyways, we'll have to keep pushing on things and we'll find some good balance points between testing, pushing, and progression. Making headway... yee haw!

 
No po photos available. Click to view time details.
Shop 9561 Working on bugs with Wayne 10/31/2022  

Multi-hour session with Wayne on the GoToMeeting session. We were debugging things out in the adilas API sockets and dealing with sub inventory queries. We went through a number of emails that had been going back and forth. We also got into some database and query analytics and doing analysis of our queries. Trying to get things faster and smoother. Small work session.

There are pros and cons to this, but this was a direct quote from Wayne during our conversation. "Our flexibility is one of our biggest assets." We have a number of clients that use the system completely different, even within the same industry. That is awesome, but it can also bite us. Just part of the game.

 
No po photos available. Click to view time details.
Shop 9512 Bug fixes 10/21/2022  

Small bug fixes. Added some dumps on the developer's update tables page. Trying to find the error. Small tweak to the sub inventory template error on the production recipe/build page. Pushed up files.

 
No po photos available. Click to view time details.
Shop 9434 Adilas Time 10/20/2022  

Danny was on the morning meeting this morning. The topic was videos and marketing. Danny is working on some quick tips and then some deep dives, dealing with different videos. We spent quite a bit of time talking about how best to get the word out. We also talked about themes - do we want to be more serious business or mix and bled and get a more playful theme. We kinda like the more playful theme.

Once the videos are done, we need a way to spread that information and link to those videos from various places within the system or within the site. One of the hardest things with adilas is how quickly things change. It is super hard to keep up and keep our users up to date on what is changing and happening. Often we will build something new and no one knows about it. That same topic "spreading the knowledge or know how" has been and is becoming more of an issue.

Sean and Steve were talking about recipes and production stuff. Sean was trying to figure things out and we finally figured out that one of the categories was missing some sub inventory attributes. We talked about making the error message a better error to help direct the users to what was needed.

We also spent some time talking about look and feel and being consistent. We kinda have a half-painted house right now - switching from classic to snow owl themes (all look and feel stuff). The last topic of the meeting was talking about setting up time with the developers and getting a full rundown on new functionality and doing some of the deep dives or developer level demos.

 
No po photos available. Click to view time details.
Shop 9506 check and push code 10/19/2022  

Looking at some small bug fixes with Bryan. These are small things from our post-it note project (stuff that I haven't been able to get to and it just existed on post-it notes on my desk). Anyways, we merged and pushed up some small changes for sub inventory templates and limiting which merchant accounts to show out in ecommerce. Merged in files and pushed up code (4 pages with changes). Smallish stuff.

 
No po photos available. Click to view time details.
Shop 9500 Sticky Notes projects 10/18/2022  

Zoom session with Bryan to go over a few post-it notes that have been sitting on my desk for a little while and just need to get finished. We recorded part of the session. See attached. The three main things that we tried to cover were merchant processing and valid options for ecommerce. Some of the merchant integrations that we have are very hardware specific, and thus not a good fit for ecommerce transactions. While we were in there looking around, we spent some time talking about our old PayPal integration. It needs some updating and some loving. The last one was dealing with some settings on sub inventory templates.

There is a 20 minute video attached to this element of time, if you want to see what we went over.

 
No po photos available. Click to view time details.
Shop 9455 Weekly server meeting 10/11/2022  

During the server meeting, Cory and Wayne were reporting on different issues, problem, questions, and talking about changes to sub inventory. Wayne is working on some new changes to help speed things up there. Wayne was also volunteering to help Alan with some elements of time (flow) stuff for production processes.

One of the big topics was the email server. It's kinda old and has been acting up lately. It's turning into one of our top priorities.

We spent some time talking about servers and specs. We have certain pages, like the balance sheet, that cause heavy loads. We really want to get into some preset sums, counts, maxes, mins, and averages - basically, we need aggregated data. We have great transactional data, we just need to keep moving up the chain and create the aggregated data that is date specific. That will allow us to go both forwards and backwards. That is very important, to be able to easily go backwards as well. Making this change to aggregated data will be huge for us in the future. We really need this as part of our fracture project.

We have a project called the inventory snapshot - mini aggregate project that Eric was working on. Once he finishes with his gift card project, we are going to have him jump back on the inventory snapshot project to help with quick inventory quantities.

The last thing that we went over was between John and I. We are working on a smooth hand-off of the discount engine project. Coordinating times and making plans. That is coming along well.

 
No po photos available. Click to view time details.
Shop 9459 check and push code 10/10/2022  

Meeting with Bryan and Cory to go over the updates on the sub inventory counts and popup modal in the cart if trying to oversell an item. We were really close. We pushed up some code and did some testing and then had to tweak it just a little bit. Cory ended up bailing out and just Bryan and I finished up the detail stuff. We got it fixed, pushed, merged, and live in the master branch. Small work session.

 
No po photos available. Click to view time details.
Shop 9478 Working with Bryan 10/10/2022  

Code review with Bryan. Working on an additional popup modal for a shopping cart message for overselling sub inventory items. Working through the cart logic with complex data objects dealing with structs and arrays of structures.

Did some prep work for a later client meeting for 710 Labs and Hoodie Analytics (15 minutes). Created a new page that pulls data by invoice number vs a date range.

 
No po photos available. Click to view time details.
Shop 9255 Weekly server meeting 9/27/2022  

As part of the server meeting, Wayne was reporting on progress and status of his wife - health issues. We spent quite a bit of time looking over a number of requests that Cory had. I sent Wayne a zip file for all of the existing email stuff (code and assets). The email server is being more of a topic lately. We will need to do something there soon.

We also spent some time talking about the content server and the disk size of what we are storing for clients. It is getting quite large. We talked about the accumulative sized and storage costs over time. Looking into other options, costs, prices, and other servers to help handle the current and future content loads.

We got into database stuff and talking about sub inventory stuff. Tons of bulk tools are wanted and needed. Another topic that we got into was dealing with training and lack of training. This was dealing with existing features inside of adilas and/or different 3rd party plugins and libraries. This topic led us into talking about maintenance and doing the right thing. That's a constant battle. Another huge vote for maintenance and education. Two huge concepts that may end up being better than new features. Something to remember as we keep heading towards the fracture model and project (maintenance and training/education).

 
No po photos available. Click to view time details.
Shop 9331 Steve, Cory, Brandon-Catch up on projects and updates 9/12/2022  

Cory had a list of questions and things that she wanted to go over. She asked about how the top 15 customers were figured out on the some of the dispensary homepages. We went into the code and looked around. We went over invoice due dates, how to allow customer/client terms to show up on invoices, and other projects.

The next major topic was parent attributes and parent attribute sorts. We talked a lot about reworking all of the sub inventory pages and our virtual wish list with regards to sub inventory and parent attributes. It is super flexible and very needed. It currently works but could use some enhancements, polishing, and refinement. Never ending process.

Along those line, there has been requests for better bulk tools for both parent attributes and sub attributes, better reports and advanced searches, and ways to speed things up and make it even smoother.

Cory and I went over some quotes and talking about the need for better project management for our internal projects. We are really good at doing just in time project management but some of our project really need some more base level requirement and expectations out of the gates. Sometimes we hand our developers a simple one liner and then they take off. They just need a little bit more instruction and direction in writing vs just talking and verbal. If good notes weren't taken, things fall through the cracks.

 
No po photos available. Click to view time details.
Shop 9332 Steve, Cory, Brandon-Catch up on projects and updates 9/6/2022  

Steve and Cory were talking about looking up projects in bit bucket (code repository stuff). Being able to check on commits and branches. They were then talking about different industries and how they are financing some of their developments. Lots of games that people play and how do we fit into that mix. While Steve was still on with us, Cory was reporting in on some meetings that she had had with Kelly dealing with the adilas label builder and sub inventory attributes. Both of those subjects seem to be heating up a bit.

Our current goal is to focus and try to get some small victories (projects being done and across the finish line). Cory and I spent some time going over projects. We talked about the need to test everything. Even small stuff. We have had it bite us before. Next, Cory and I looked into a possible bug in some settings. We looked and looked and couldn't see anything quickly. We may have to jump in deeper, when we get a chance.

Shari O. popped in and had some questions about getting a new internal email server. Our current solution has been giving us some problems lately. We don't change any code on our side and it works great, all of the sudden it will be down, and without any changes on our side, it all of the sudden starts working again. Kinda crazy. Shari O. calls it the gremlins or email gremlins. As a side note, later in the meeting she popped back in to let us know that it was working again. Random.

Wayne joined the meeting and got Cory and I up to speed on a few things that he is trying to work on. Performance tweaks.

Cory and I then started going over her list of possible projects, quotes, and estimates.

- Need quotes for inputting sub attribute data all at one time upon PO creation (start with build page)
- Bulk update sub attributes interface
- Mapping of EOT (elements of time) data to sub attributes (settings for cultivation and manufacturing)

Along the way, we were talking about options and settings that relate to the concepts of the data assembly line, recipe/builds, showing subs in the packaging and production pages, and managing recipe/build output better. Lot of talk about bulk edit tools for sub inventory attributes, batches, phasing, sub locations, and moving subs along a known path or virtual assembly line.

Dealing with the data assembly line concepts, I was telling Cory how we setup both rules and assignments for smart group buttons (tiered pricing buttons). I was mentioning that we could use something similar to help setup and do the mapping between elements of time, sub phases, sub locations, sub groups, and monitoring the progress of certain things. We need the rules (what or how to do things) and the assignments (who or what to connect or monitor). Using the two pieces in combo (rules and assignments) we could then have the computer and/or system help us monitor progression and progress. They are good at that, they just need instructions and the who, what, when, how, and why and they can do those jobs over and over again.

As we keep rolling more and more towards the concept of fracture (future adilas project) I would really like to keep working on the data assembly line concepts and using rules and assignments to get the correct flow and mapping in place. I see that as important as we keep going forward.

 
No po photos available. Click to view time details.
Shop 9379 More custom code 8/31/2022  

More work on the code for 710 Labs and the custom data extract that they are wanting with all sub inventory attributes and invoice line item data.

 
No po photos available. Click to view time details.
Shop 9378 Working on changes to a data export 8/31/2022  

Working on the 710 Labs custom data extract and data export. They wanted all of the sub inventory attributes to be passed back with every sale and line item. Working on the new code and writing new logic.

 
No po photos available. Click to view time details.
Shop 9340 Finish label maker quote 8/31/2022  

Meeting with Cory to go over the quote line items for the adilas label builder. We made a small Word document and added in all kinds of notes, verbage, and estimates on hours for each section. That document was sent to Cory via email and also uploaded inside of adilas for that label builder project. We also did some training on adding media/content to sub inventory items. Lastly, we went through some older notes and tried to make sure that we have/had all of the MVP requirements. Productive meeting and making good progress.

 
No po photos available. Click to view time details.
Shop 9333 Steve, Cory, Brandon-Catch up on projects and updates 8/29/2022  

Steve and Cory were talking about pages, packages, and sub inventory. Shari O. popped in and we ended up having some light budget talks. The four of us talked briefly about the state of adilas and where we are going. Lots of good things going but we do need to be careful. On a different note, many things are changing all around us - including code changes, settings, clients, needs, expectations, etc. It's a moving target.

Light talk about what is an MVP (minimal viable product) for what we are doing? Even though we have so much functionality, do we have all of the required pieces? There are still some things that we need, even for an MVP - although it be a large MVP.

Cory was asking questions about projects and what not.

 
No po photos available. Click to view time details.
Shop 9350 Working on a custom data extract 8/25/2022  

One of our clients wanted to see all of the sub inventory attributes on a custom data export. Doing some testing and prep work.

 
No po photos available. Click to view time details.
Shop 9222 Adilas Time 8/22/2022  

Talking about sales and follow-up calls and emails. Steve, Sean, and I were going over some emails that we got over the weekend. We decided that we would reach out to one of our clients, as another potential client wanted to ask some questions to some of our existing clients. Making plans and getting ideas from each other.

Cory joined the meeting and we broke into a small project overview and question session. She was out of the office most of last week and just had a pile of emails and questions for Steve and I. There were 3rd party solution needs, emails, small bugs, and new requests. It doesn't seem to slow down... and if it does, it isn't for very long.

Cory and Steve were going over the compare Metrc inventory page and talking about ideas to help shorten up that page. We have a client that is getting so many sub packages that it is causing problems (too much data). We talked about other possible bulk tools and ways to help them clean-up there data and/or be able to easily filter their records and results sets. Kinda funny and kinda not, but we build and break, build and break. Our clients keep pushing things to huge extreme levels. All you can do is build and break, build and break, try to respond and look forward as far as you can. It becomes an interesting game.

After that, Cory was bringing forward some new requests to be able to duplicate PO's with sub inventory packages. We have been able to duplicate PO's for years now, but not with sub inventory packages because those are all fully independent and have varying sub attributes and usually it's not a straightforward duplication process. It requires too many other questions, variables, and switches. Anyways, that is heating up and we may have to figure out a way to get that going.

 
No po photos available. Click to view time details.
Shop 9270 check and push code 7/28/2022  

Emails and research. Then working with Bryan on some table column spans and alignment issues. He showed me a number of scenarios and how things were looking and lining up. This was all dealing with invoice sub totals, taxes, and grand totals. The main switch was whether or not a line item and/or invoice had sub inventory and sub attributes being displayed. The code was looking good, so we merge it into the master code branch. Pushed it up to all servers.

 
No po photos available. Click to view time details.
Shop 9286 Clean-up and to do list stuff 7/27/2022  

Two different projects. One was expanding the max character length for customer and vendor searches. Took off the old max of 4 characters for the searches and opened up the fields to allow for unlimited characters, in the search field. Pushed up code and let Michael Webber from McCorvey's Pro Shop (bowling supplies) know about the new change. He had requested an increase there on those pages.

Fixing some data for Cory. 710 Labs had one sub inventory item that got double booked. Made a backend data change for the client. This took about 45 minutes to find it, change it, and make sure everything was good to go.

 
No po photos available. Click to view time details.
Shop 9188 Brandon, Steve and Cory discuss projects 7/21/2022  

Long meeting between Steve, Cory, and I. Cory was reporting on tons of different projects and getting our input and suggestions. We covered tons of different topics. Here are some of my notes (from 10 pages of post-it notes - didn't know it/we would cover so much). The original meeting was only setup for an hour. It went a wee bit over... :)

- Talking about tons of custom label options. More talks about what to do with Calvin's custom label builder. We've spent a lot of money there and want to really get a return on that investment.

- We talked about bringing projects more internally with our guys and breaking things into smaller and smaller pieces.

- On labels, we had a request to be able to do serialized labels (up or modify counts and counters based on batches or packages).

- Using tons of our existing tools and refining those pieces. We have a ton of tools in the shed (virtually).

- Lots and lots of talks about breaking up the bigger projects into multiple smaller pieces. Along with that, we need to be able to charge money for bigger estimates. Everything takes time and effort. Either that or be able to recoup the amount within the bid or estimate.

- If we are doing real custom work, we need to charge for that. Often, we end up taking a hit.

- The trend seems to be (globally) transactions and details going into aggregates and summaries. We have had so many 3rd party analytical companies wanting to use our API sockets to harvest and use our great data sets. We would like to do a bunch of that analytical work inhouse vs farming it out to a 3rd party. All of these 3rd parties are just working for individual companies, but you can see the trend happening. Our clients are really wanting to get to the business intelligence level (BI) for viewing their data, snapshots, counts, summaries, and other aggregated data or stats.

- We went over some pros and cons of using the adilas API sockets. Back and forth on monetizing those channels and also making sure that they don't get abused or flooded.

- Lots of talks about the item catalog and the image catalog. As we use more and more API sockets, we could really use bigger and bigger bulk tools to help with data standardization and speed of deployment. Lots of positives. We, as a company, could also sell more systems if we brought in the enterprise level (way up - cascading info down to lower systems). Good stuff.

- More bulk standard tools. This just adds to the votes for building out the value add-on core model with different levels. Just as a recap - the value add-on core model deals with 5 known levels. They are: 1. Transaction core (current adilas system), 2. Industry specific skin, tools, and features. 3. Any custom code on top of the main system. 4. BI - Business Intelligence levels (stats, sums, counts, averages, mins, maxes, aggregates), and 5. Enterprise levels - connecting multiple worlds in a hierarchical type system (roll ups, roll downs, transaction corps/worlds, aggregates and sum corps/worlds - also dealing with permissions and access). We really want this type of a system for our future fracture project. We already have a number of pieces to this project (all kinds of prototypes spread all around the system), it just isn't all put together. That would be so awesome, clean, powerful, and hopefully pretty!

- We spent some time talking about our clients. Sometimes they get pretty creative. That is both good and bad. If they get creative, and find errors or break things, we just fix them and keep going. Other times, they totally use certain tools in ways we never would have imagined and/or foreseen. That can get interesting.

- There have been some requests for bulk tools for updating sub attributes and bulk sub inventory tools.

- Cory kept asking - Who are we? We tend to build generally but then we have all of these industry specific demands that keep coming at us. It makes it really hard to know where to focus. We really need to decide who we are and then hopefully that or those choices will help guide us.

- Dealing with Metrc (state compliance systems), we've had the request to build out more individual user type functions. This is dealing with more employee/user type permissions and settings. Currently, most of our Metrc transactions are done on a corporation or world level. The new requests are to do the exact same things but break it down on a per person basis. That sounds awesome, but that could be hundreds of thousands of dollars in development. We would have to create the one-to-many relationship, make sure that they were valid, then sync up users and permissions between systems in order to play. Then, to further make it kinda crazy, you would have to check user permissions (remotely) then attempt the connection, then if it failed, figure out if there was a global (higher up) option that you could do so that it wouldn't break all of our code and processes. It could be a huge project. Lots of unknowns. As part of this project, we would also have to add more history tables, who did what, who changed what, who has permission to do what, and making sure that each individual keeps their keys and tokens updated. It sounds like a small nightmare.

- We seem to build in general and then use it specifically as needed. Custom code on top of our own standard package, tool, or feature.

- Going over the cost of building and building. One you have to build it, then you have to maintain it, and upgrade and support it. The costs keep increasing. This topic lead us back to questions about who are we and where should we be focusing?

- There is a growing need to use asynchronous type loading like AJAX or some way of breaking huge datasets into smaller pieces. It is totally common for us to need to show or export 10,000+ or even 100,000+ records at a time. The current process tries to take that whole thing as a single bite or single attempt. It's just too large and slows things down.

- Some time was spent talking about loyalty points and keeping track of the total liability. More talk about other reports that show sums, grouped values, look-back capable reports, and using ACV (actual cash value) for recording loyalty points. We do a bunch of that, just refining the process and making it even smoother.

- Need for messaging or using the message marketing features that we have already built. There is a growing need for push notification and two-way communications outside of the main app or website. The client portal is growing in needs and options. More mobile ready or full mobile pieces are going to be coming down the pipeline. Everything seems to be trending in that direction.

- Question - do we fill in the gaps on functionality or try to update the look and feel? It sure would be awesome if we could virtually turn things on/off based on the UI (user interface) and settings. We would love to set things up super simply and then let the users add on or take away from our smaller base level. A new mini version of the shopping cart is in great need of these fracture type level settings. Start small and simple and then let the users build on or configure things as needed. Hide anything that we can unless asked for. Then when it is done (using the tool or feature), it can be hidden again. Every page needs show/hide options on a per page or per section level. Totally customized.

- Along with the show/hide options talked about above, it would be so cool to show all of the options and then say - what do you want? You tell us. More fracture stuff (where we are headed). Mountains and iceberg analogy stuff (it still needs to be there, but what is shown and/or exposed).

- We talked about extra costs and prices for some of the other add-on tools and functions. Some of our stuff (tools and features) takes a major amount of work and effort. We would love to sell more training, consulting, automation, and other professional services.

- News and updates and the importance of keeping our users up to date and informed. This seems to be a constant need and keeps evolving. Content and making and creating new content (creation and maintenance).

- Lots of talks about prioritizing efforts for different persons (parties). Diving out responsibilities and sharing info across departments and across people (users).

- Using videos - the value of education and training. Selling our other services. Scheduling and setting up ongoing training efforts. We would love to make lots of polished smaller videos. Laying it all out for our clients (on demand education or just in time education). We could really use our website to toot our stuff for different business verticals. For example: Revamping our manufacturing site and pages. We can handle... (fill in the blank) for manufacturing or whatever. That is a deep pool (manufacturing and production type businesses). The trend seems to be leading us more in that direction.

 
No po photos available. Click to view time details.
Shop 9180 Changes to a custom data export 7/4/2022  

New upload with some code changes for 710 Labs and Hoodie Analytics. Small re-work and changed the logic on 4 fields for sub inventory. Pushed up new files and sent emails to both Wayne and the client.

 
No po photos available. Click to view time details.
Shop 9174 Working with Bryan 6/30/2022  

Meeting with Bryan over GoToMeeting. We started into some questions on automating discounts and then into sub inventory. Bryan had been working on a project to show sub attributes on save as PDF invoices. The sub attributes already existed in the other invoice views, it just wasn't on the save as PDF version. We merged in the code and pushed the files to all servers.

 
No po photos available. Click to view time details.
Shop 9071 Adilas Time 6/22/2022  

Sean and I were talking more about recipes and recipe/build processes. It would be so cool if we could add in a quick way to work with sub inventory (currently missing but on our wish list). Imagine if the cart could pick from the oldest open package by default (maybe a setting), then allow the person who is building the actual output (some sort of fulfillment) to make the final decision (which sub package something really came from). Sean also had the idea that we could run it like we do with quotes or sales from ecommerce. We allow the parent items to be set and then the subs added in real-time as the invoice gets fulfilled or generated. There may be other possible settings options as well. Great ideas. This would really help in certain industries and being able sell bulk subs or preset kits or invoice groups (specials, packages, etc.).

Going over emails. That seems to be a big part of my day. Cory joined the meeting and we touched base on some projects, servers, and clients. One of the underlying topics was "timing" and how important timing of certain things is/was. Good stuff.

 
No po photos available. Click to view time details.
Shop 9070 Adilas Time 6/9/2022  

Working over the new GoToMeeting interface with Steve. They are in the process of changing their interface. We were working on setting up a new dynamic look-up function for a single sub inventory attribute and its value. Small work session. Steve was building the new function and I was helping and directing him.

 
No po photos available. Click to view time details.
Shop 8978 Server meeting 5/31/2022  

Cory was asking for reports on different projects. Wayne joined and we jumped into the server stuff. He was requesting more specific errors to be reported via email. If the error reports are too generic (server 6 is down), that doesn't give him much to go off of. It would be better to say something like, server 6 is denying login access or something like that so he knows where to start. Anyways, he was requesting more details when reporting problems and server errors.

We talked about the database clean-up for data 0. Next, we got into looking over errors and slow pages and slow queries. The main problem child queries are all dealing with corporations with tons and tons of inventory, invoices, and sub inventory. There is just a lot of data there.

At the end, John gave a small report to us. He has been working with Dustin to help get Dustin up to speed with server stuff and pieces.

 
No po photos available. Click to view time details.
Shop 8869 Adilas Time 4/4/2022  

On the morning meeting, Marisa was showing us some sub inventory issues that need to be smoothed out dealing with sub inventory attributes and template settings. I was doing some emails. A question was brought up about New Mexico state payroll and state withholding. We used to have that state, we just need to circle back around and make sure that everything is updated and good to go.

Shari O. and I spent some time going over progress with USAePay and getting information from them. We have both made multiple calls to our contacts at Newtek and haven't really gotten the information that we need yet. Kinda frustrating, we just want info on account types and how to help our clients sign-up for what they need. If we can't the info that we need, we talked about going in a different direction. Both of us will keep trying, for the time being.

Switching subjects, Shari O. and I spent quite a bit of time talking about our transition from full 1099's for all of our guys and gals to the multi member LLC (partners and ownership) options. Eventually, we may need a hybrid type solution that allows for owners, 1099 folks, and even employees and W-2 folks. Still trying to figure things out there. As a note, Shari O. is recommending that we slowdown a bit and make sure that we have watched budgets, gotten documentation, and standard procedures in place before we jump too quickly. I showed her the adilas docs section, inside the adilas site, and she had never been there. If we do build out more internal flow and owner type handbooks, that is where it will go. It will be called our standard operating agreement or something to that nature.

Shari O. and I talked about budgets, watching and tweaking those budgets, and then making some decisions. Lots of talk about timelines and timeframes for some of the upcoming changes. Good stuff. I'm super glad that she cares and is willing to ask hard questions.

 
No po photos available. Click to view time details.
Shop 8782 Adilas Time 3/24/2022  

The morning meeting started out normally and then sort of morphed into a multi hour long meeting with no real stop or start between the different topics and sections. We started out and Sean was checking in and lightly going over some of the BioTrack API socket questions. We got into a discussion on promises made and client and user expectations and how deep we want to go into those areas. Some of our clients expect an easy button for every possible wish or desire. It just doesn't work like that. Yet those expectations are real and valid based on user requirements and user demands. That puts tons of pressure on us as a software system. There just is no physical way to make it do everything, for every person.

Wayne joined the meeting and the conversation moved over to slow queries, database indexes, record counts, volume of data, and all kinds of other topics. We spent some major time going over potential problems with our flexible "LIKE" searches on the parts homepage (flexible wildcard searches across multiple database fields and columns). We need the flexibility, and we have trained our people to rely on that, but because it is so open, it is causing issues when put under a huge data load (not thousands but millions or multiple millions of records). We can handle quite a bit with no problem. When you really overload it, it starts groaning and squeaking under intense pressure. Technically, that is called scale.

The amount of data that some of our clients are generating and recording is causing a volume or scale issue. We got into deep logic and how we could speed things up if we were able to use indexes, exact searches, and get rid of huge list look-ups (using the SQL IN clause) or super flexible text searches using like commands (SQL LIKE clauses with wildcards). Basically, when doing some of these functions, the databases skip the indexes and end up looping over millions and millions of records. We spent some time talking about a number of possible solutions.

We had a break where Wayne had to go pick up his kid from school. In the meantime, John and I were talking about some of his projects. He was showing me a bunch of stuff that he has on a Jira board for the discount engine. I was kinda getting overwhelmed and depressed. So much stuff to do and manage. Sometimes it feels like it is all over the place and it never ends.

Wayne got back and we flipped back over to database queries possible options to help speed things up and handle a huge scale or a huge load of data. We talked about a combo type approach where we have to include tweaks to the database, code changes, UI and UX (user interface and user experience) changes, and other backend management changes. It may end up being a combo type package or approach to fix some of these problems.

That topic and discussion lead us to talk about prior or earlier decisions that were made years ago. We talked about why certain things were decided upon and implemented. It is very interesting and the story keeps rolling out in front of us. What we have now is a combination of history, situations, decisions, and even future wants and needs. It all mixes together and makes a complex solution. Some of the why and what we did is super important.

Having said that, things keep changing and morphing. We talked about building things for a non-static environment. Dealing with scale (up or down). That lead us to possible daily or real time mini aggregates on quantities and other key points and factors. Basically, ways of summarizing data and getting to more of a business intelligence type level - quick counts, sums, totals, averages, mins, maxes, etc.

Talking about the aggregation processes lead to talks about database triggers, update routines, scheduling, clean-ups, automation, manual checks and overrides, and the list goes on. Along the way, we kept talking about how important the inventory pipeline and tracking the ins and outs is so critical to these values, stats, and numbers. Steve joined us and we got into update functions, methods, table row locking, more manual updates, and reconciliation options to make sure all is well. You basically need the transactions (what happens and when - this is the details or the historical record). You also need the sums or totals (these are the running or current aggregates). These two pieces, transactions and aggregates play different roles.

As part of our discussion, we were looking at one-to-many database table and column relationships and how things are handled currently. It gets deep quickly. We then started talking about breaking shared tables into corp-specific tables and building smaller corp-specific aggregation type tables. This lead us to a small discussion on sizes of tables and when ones are already broken down into corp-specific tables and which ones may be up for review.

On the mini aggregate tables (quick sums, counts, and totals) we could go different ways. Do we want a historical record of the aggregates or do we just want to keep current (now) sums, counts, and totals? If you add historical, you start adding dates and get new records every day (assuming things are changing) or if you skip the dates, then there are less records, things may be quicker for the current but could take longer if going back in time. Maybe both... one to hold the historical aggregates over time and one to hold the quick and dirty (real-time current look or roll call report).

The deeper we got, the more that settings and database options came into play. We have a future project called fracture in the planning. We need to be able to have and use settings on what our users and corporations (worlds) want to see and use. We have tons of data and tons of records. Okay, great, what do you, as a user or end user, want to see, show, display, sort, etc.? How does that need to be organized? It goes deep and gets into advanced settings, display options, and being able to save layout and configuration options per person, per page, per corporation. That all needs to be included in the fracture stuff, along with the other transactional and mini aggregate database options listed on this page.

Once you know where you want to go... You can get there (hopefully). If you plan on being the only one to get there, the trail doesn't have to be very good. If you plan on repeating the journey, the trail needs to be even better. If you want a bunch of people and/or companies to complete the journey, you will need a road, not a trail. All part of the process.

Going back to tables, we talked about two big corp-specific tables in the system that will need a buddy mini aggregate table (or more). The big transactional tables are the po/invoice line items and the time sub inventory tables. Those two tables (that are already corp-specific) will need helper tables to keep track of both transactional aggregates per date (semi historical summaries) and also current non-historical mini aggregates for the quick and current view (no dates). Another way of putting this is making location specific pre math calculations vs having to go and re-sum things up or count things based on complex look-ups. You virtually do the known math per item, per package, and per location before it is needed. Then those numbers and values are quickly ready and available as mini aggregates. If you need more details or the blow by blow, you just go back to the transactional tables or records (different tables).

Some of our current pain is in the sales and POS (point of sale) systems such as carts and inventory tracking. We can do it, but if it gets into hundreds of thousands or millions upon millions of records, you run into the scale factor and issues.

Just for our notes, a couple key pieces are corporations and locations. If everybody just had a single location, some of this would be really easy. If you have more than one location, the solution needs to scale and keep track of mini aggregates based off of corporation and locations. That is a huge key that often gets overlooked. Plan for multiple (unlimited) locations. Here are some possible columns that may be needed for some of these mini aggregate tables for mini aggregate quantities - auto id, corp id, store id, part id, sub reference id (sub id), part count, and maybe a date if doing historical.

Switching subjects again, we need to charge more to clients for harder tasks and functions. I had a friend that was talking about software. He said, you tend to get two different types. You get cheap software or custom software. Hardly ever do you get cheap custom software. Custom does cost time and money. That is the way it is.

After Wayne left, Steve and I stayed on for a bit to go over some other things. We talked about gift cards, coupons, and other upcoming projects. I showed him a PO rounding demo and what I have done so far. The next question was... how deep are we going to dive per subject? Lots of options.

 
No po photos available. Click to view time details.
Adi 2169 Alberta Compliance Report Changes 3/22/2022  

3/22/22 3:06:16 pmStart Work 3/22/22 3:43:31 pmLunchtime id 2169: meeting with Cory to discuss the perimeters of the project

 
0.63

3/22/22 4:59:39 pmStart Work 3/22/22 6:38:14 pmGoing Hometime id 2169: beginning the process of updating the table to reflect the new regulations on the canada retail report 

 
1.65

3/23/22 9:38:10 amStart Work 3/23/22 10:50:22 amOthertime id 2169: replaced the columns quantity sold - units and quantity sold - value with quantity sold instore - units and - value and added online versions as well 

 
1.21

3/23/22 10:50:33 amStart Work 3/23/22 12:44:36 pmOthertime id 2169: troubleshooting some internal server errors when trying to add sub inventory to the cart so that I could test the code changes. (and testing the code changes) 

 
1.91
 
No po photos available. Click to view time details.
Shop 8812 Fixing reports and small issues 3/1/2022  

Small fixes on a custom report for a client. Merging in some code for Chuck on the view parts page. Small fixes for RFID tags and sub attributes on the view parts page and the sub inventory tab. Started working on a fix for Marisa on ecommerce images and setting up default logic based on actual images, item defaults, and category default images.

 
No po photos available. Click to view time details.
Shop 8691 Projects 2/28/2022  

Working with Chuck. We merged in two branches. One for the view parts page and some changes on the sub inventory tab. The other one was for the customer queue. We pushed these things up to the dev testing server. After that, I spent some time checking on banks and doing quick phone calls.

 
No po photos available. Click to view time details.
Shop 8763 Working with Chuck 2/22/2022  

Chuck and I doing a small work session. We went over the font awesome stuff and launching version 6 on our site. He was sending out emails with updates and what not. We then rolled into doing some small fixes on the parts homepage and dealing with sub inventory display options. Merging in code from his code branches into the dev testing branch on the dev testing server. Made a bunch of other small fixes and pushed files up to the testing server.

 
No po photos available. Click to view time details.
Shop 8745 Fixing bugs 2/9/2022  

Working on the bug with sub inventory descriptions and passing hidden form fields with special characters. After I got that one done, I jumped on some research that Cory asked me to do. Originally, we thought that it was a small bug as well, but it ended up being a different interface and UI choice. The problem was the Kush cart was not showing the same amount of fields and data as the classic cart (internal shopping cart). After looking into it, the Kush cart never had those features. The user was flip flopping and wanted both carts to have the exact same layout. They weren't designed that way. The classic cart has tons of data and the Kush cart is a more streamlined version. Anyways, we figured out that it was not a bug, just completely different interfaces. I sent a note to Cory to let her know. I also contacted Marisa and Sean and they did some testing on the other bug fix and gave me feedback that all was well and ok.

 
No po photos available. Click to view time details.
Shop 8718 Meeting with Chuck 2/9/2022  

Chuck and I on a meeting. We were talking about our use of Font Awesome and some new releases that are coming out. We also talked about views and possible overages (charges) for how many font awesome icons we use. Millions of views, only in the first couple of days of February. Our plan is only set for a million views per month. anyways, just checking things out.

Next, we rolled into some new JavaScript validation that Chuck is working on. He is working on simplifying some our checks for max field lengths and showing how many more characters will be allowed for certain fields. After that, we rescheduled a work session for later today. That way I could get back to fixing the display bug (sub inventory descriptions).

 
No po photos available. Click to view time details.
Shop 8673 Adilas Time 2/9/2022  

This morning, when I joined, Sean and Marisa were on the meeting going over things. They showed me a display problem with products and descriptions with special characters. The descriptions were cutting off the descriptions depending on the special characters. If added by scanning the barcodes or id number, they went in fine. If just generically searched for the items and then added to the cart, there was a display problem. We determined that it was dealing with the special characters and encoding the data to handle the special characters. The primary issue seemed to be with custom sub inventory descriptions that had special characters.

After we determined what was needed, we also looked into some custom emails for invoices and quotes that get sent out of the system. We looked at some code, logged into backend email accounts, and did some testing. We got everything flowing and working. Not sure what the problem was.

John checked in briefly and then bailed out. I spent the rest of the time working on the sub inventory description issue.

As a side note, we are seeing a real need for both maintenance and education/training. Those two things combined are a huge part of what we do and hope to be able to do... The training needs to be for both external customers and internal users and staff. I want to put my vote in for both - maintenance and education.

 
No po photos available. Click to view time details.
Shop 8723 Dustin Progress Meeting 2/7/2022  

Dustin and I on a small work session. He had some questions and we worked through a number of changes and improvements. I spent some time explaining and diagraming (drawing and making connections) the sub inventory process and what data and tables are connected and how they are pulled together and related (database stuff and backend logic and relationships). Anyways, lots of drawing and small code samples.

 
No po photos available. Click to view time details.
Shop 8524 Adilas Time 1/4/2022  

Going through emails and such. Checking in with Danny on the structure for promissory notes and small business loans and investments. Small stand-up with Alan, Cory, and I on a side project. I got pulled into looking into a possible sub inventory export error dealing with multiple decimals. From everything that I was able to find, our code looked to be doing the correct thing. However, Microsoft Excel was reformatting some of the data and only showing 2 decimals by default. We had to do some manual formatting in Excel to get it right and show all five decimals. All of the data was there (our part of the export), it was just formatted incorrectly on the Excel side. Reported back to Cory about what I had found out.

 
No po photos available. Click to view time details.
Shop 8527 Adilas Time 12/29/2021  

Wayne was showing me some new query code changes. He is playing with some full text indexes and new searches that play with match and against vs our older like SQL queries. Wayne has pushed up some code to the developer's testing server so that we can play around with the changes. If all works out ok, we will add the full text indexes and new dynamic searches to customers, parts, and sub inventory. Those sections get hit really hard, every day, multiple times a day, per corporation. We'll start there.

Wayne is also working on some other deeper database admin scripts for the sales tax aggregate project that Eric was working on. We are trying to get things pushed up, while maintaining high security credentials. Before the standup meeting, I asked Wayne to show Alan what was going on and a small demo of the new changes. Making progress.

The guys joined and did a sprint review and a small show and tell for their current sprint. It is super close to being all the way done. You could tell that someone still needs to go through and do the last-minute tweaks and what not to basically sweep the floor and fully deploy it. On the positive side, you can tell that the sprints are going much smoother and faster. Other than the semi buggy demo, it really was looking good. Like I said, just a little bit for polish and finesse and it would be perfect. You could tell that the main pieces were there.

During the sprint review, some of the guys were showing some of their creativity and on the fly code building and custom functionality. That was fun and cool to see. The main look and feel was looking good. They are using tons of object oriented code with models, services, DAO's, classes, sub classes, etc.

Alan was showing and talking about some new integration tests and how he was using real database tests on a dummy database, but it was able to use real services, real DAO's, and real flow without hurting live or production databases. As part of that or those tests, he was also doing some clean-up functions during the testing, if he was making extra records for testing. Basically, things are getting better and better, smoother and smoother, and more real life like testing. This helps us look for real bugs and find them quicker and make things tighter and smoother.

We also talked about some of the next steps along the sprint path. Some of this was dealing with planning, testing, bug fixes, and all the way to full deployment. One of the current missing pieces is going through different scenarios and doing some deeper user level testing. We'll get that figured out and push things forward from there.

 
No po photos available. Click to view time details.
Shop 8539 Server meeting 12/28/2021  

Wayne, John, Steve, Cory, and I talking about servers and such. Wayne was showing us some potential time and CPU processor savings if we change the way we query for text-based values. In SQL (database language - structured query language), we use a lot of what are called "Like" statements. This allows us to search for partial matches and includes a number of wildcards to help the search results be more open. Anyways, Wayne was showing us that if we change some of our code and do full text indexing on certain fields, it may be much, much faster to get the same search results. We chatted about that and made a plan to experiment with it.

Some of our biggest tables that have flexible searching are customers, parts (general inventory items), and sub inventory tables. This includes customer look-ups, basic part searches, barcode searches, RFID tag searches, and tons of other flex search options. The goal is to speed up some of those flexible searches by 10 times and make things more snappy. As a note, the new searches would use SQL syntax that did the full text index (settings on the tables themselves) and then use SQL commands of match and against commands to line things up.

As a fun side note, Wayne is using Fusion Reactor to find slow pages and pages that get ran a lot. That data will help us find queries that we can tweak and speed up. Good stuff.

We are trying to get Eric's sales tax aggregate project merged and pushed up to master and then deployed on all servers. We will need Wayne's help for that. Some of Eric's code will require some deep backend database scripts. We'll work with Wayne and Eric to get those pieces pushed up.

After Wayne left, Cory and John were talking about the discount engine and trying to get Eric to help with part of the cart logic and wire-up stuff. The subject then switched to John asking and chatting with Steve, Cory, and I about the Jira boards. We plan on using that product for the time being but would really like to keep pushing on elements of time so that we could do even better project management inside of adilas. We have a bunch of the pieces. It just still needs some loving and may require some tweaks and changes. We want to head in that direction. Steve was mentioning a hybrid solution and working to get the adilas project management stuff, even more up to speed, to help us internally. We really want this functionality, but it just takes time and resources.

We talked about some of our developers being pulled in so many different directions. Almost like being pulled in half (just overloaded). Some good conversation here. As we were switching gears, John was asking and lightly pitching options for a small contribution type project, where his time would end up being translated into a form of investment, into the adilas company. We talked about a few options.

Steve really wants to find something that will help us all out and really provide a good positive ROI (return on investment). We want to keep pushing on more and more of the scheduling and project management (planning) type pieces. We see some great potential for good ROI there, in scheduling, appointments, rentals, reservations, and project management and tracking.

 
No po photos available. Click to view time details.
Shop 8414 Dev check-in - Alan and John 11/3/2021  

John and I did a quick check-in. Normally, Cory joins us but she was travelling today. John reported on the discount engine remake project. He is gaining traction and realizes that we have to tone it back a little bit compared to his dream of where he wanted to take it. The current project is just too big of a lift right now. We'll get back to it later on. The other thing that he reported on was some server stuff and John is taking more of a role in the code management and merging area. Especially for the new development environment and testing server. He has been put in charge of that.

Lots of emails. Marisa was chiming in on some marketing ideas. I also got some emails from Audrey and Marisa dealing with other marketing things, questions, budgets, and goals. Good stuff. I sent off a text to Steve to get a confirmation on some of the things that are going on. I want him to be involved with the decisions.

In between times, I was doing more research on the recipe/build process and getting deeper into the differences between build and sell (invoice based recipes) and build and hold (production or internal manufacturing PO's and inventory manipulation stuff). I'm seeing that I may need to add more options to help with sub inventory, multiple decimals, and yield multipliers. When we originally built this section, it was pretty simple. In the meantime, some of the needs are much more diverse and deeper. This whole thing is coming form a project to go back in and check some of the rounding errors for PO line items.

Without being too detailed, no rounding is needed if you have whole numbers times other simple whole numbers or simple decimals. It really gets funky if you have high quantities and costs that are clear out into the 5 decimal land. If you combine the two, the rounding error really starts to be more visible and important. Anyways, looking into what is needed to take those tools to the next level.

 
No po photos available. Click to view time details.
Shop 8298 Meeting with Chuck 10/6/2021  

Discussing with Chuck the new presentation gallery. We talked about a couple of small changes. We went over some payables and then moved into in-line validation and JavaScript validation on some of the existing projects he is working on. After that, we did some training for the parts homepage, sub inventory, and light shopping cart functionality. Chuck is going to be working on a redo (modernize or face lift for the general inventory or parts homepage). We got pretty deep into the differences between parent and child inventory and how things are tracked.

 
No po photos available. Click to view time details.
Shop 8158 Projects 9/9/2021  

Small validation fix for Cory and sub inventory. Spent the rest of the time recording notes.

 
Click to view time photos.
Shop 8183 Dev check-in - Alan and John 9/1/2021  

John joined the meeting first today. He, Cory, and I went over some of his projects and where he is at. He has pushed up a number of smaller branches in the past few days. One of them had a number of JavaScript changes to the discount engine. He reported on that and then we switched over to servers and system admin stuff. John wants to document things but he is concerned with security keeping the procedures and processes out of the hands of those who shouldn't have them. We talked about some options for distributing and securing those documents.

John also reported on chasing other smaller bugs and putting out small fires. Going back to the key person, systems admin docs, currently, lots of things are hinging on certain key players and their knowledge. We need to capture that knowledge and put it in writing, as best we can. We also need to keep those documents in the high admin's hands vs public knowledge. Anyways, we will start going through things and collecting what we can, while having the security thoughts in front of us. We'll find a good mix.

After John finished, Alan checked in and let us know where he is at with his projects. He is still working on the new sub inventory object model code out in ecommerce land. He still has a few things left with that project. It's been a big lift. Also, he was saying that he currently can't pull that new code inside adilas (out of ecommerce land and into the main secure adilas platform) due to some legacy issues. Not insurmountable, but at least a decent amount of work.

One of the blockades is the number of black boxes and custom code that exist out there. We need to figure out a way to bring in the new code into the legacy system. Alan has a few ideas, but we may end up having modes (new and old) and being able to flip flop between those modes.

Some of the new stuff is more object oriented vs in-line code that runs from page to page but requires a certain step by step process or chain of events. Some of Alan's new stuff deals with objects and inheritance, less hits to the database, and all around more efficient code. It's all part of the process. You have to start somewhere and eventually, things tend to morph and/or mature, in logic and processes. It's all part of the game.

Alan was showing us and talking about some crazy tax calcs and recalcs and how the models and objects handle those changes. One of Alan's goals in this project is to stabilize some of the pieces and isolate the variables. In the new models, he watches and monitors things like quantities, target prices, costs, price per, rounding errors, taxes, etc. Pretty deep.

I thought that it was interesting to hear Alan say that one of the barriers to him finishing the project was the number of black boxes or custom code pieces that are out there. We love doing custom code and it really helps our users, however, there is a cost to that and it tends to hit our developers and how easily they can roll out those new changes. Basically, easier for the users, but potentially harder for our developers. Lots of moving pieces.

Cory and Alan were talking about MVP models for the new sub inventory pieces. We could jump off into super deep waters, but we need to get the project done. We can always circle back around.

After talking about sub inventory for awhile, the topic switched to Metrc (state tracking and compliance system). That 3rd party integration is more than a fulltime job. Anyways, they were talking about importing inventory, comparing inventories between systems, and other required interactions. Lots of moving pieces, plus you have two separate systems that work completely independent and we are trying to keep them synced up together. It can be very challenging. If they change something, we have to follow suite and/or create a bridge to what new requirements are needed. If we make a change, we have to make sure that we aren't breaking anything that already exists.

After Alan was done talking to Cory, he left and just Cory and I were left on the meeting. We started talking about how long certain projects take, how deep they are, and how they tend to morph from what was originally created into something completely new and different. This lead to some discussions on the complexity of being a public or publicly demanded company (our clients have a say in what we do, when, how much, why, etc.). Sometimes I wish that we were just developing our own little software solution and then we could just sell it to the public. Instead, we are building, changing, refining, and trying to please our clients along the way. That is ideal, but it also adds all kinds of pressure and other variables.

Cory and I got talking about real costs and what it takes to please people. We had a client that came up with an idea, it sounded easy, but has turned into a huge 4 month project and has cost us over $30,000. Sure they want it, but did they pay for it? Sadly, no, we are stuck with the bill. We tend to do that a lot. That hurts and especially if you keep doing it. We love to build and can get sucked into that very easily. Having said that, we are getting better at asking for seed monies, billing out the clients, and sharing the load. Sometimes we just need to vent a little bit.

As we were talking, my mind started to think about how hard it would be to fully rewrite the entire application that we are building. Don't get me wrong, I'd love to and I think we could come away with some huge benefits but there is a cost. Some of those costs are real costs with money, resources, talent, time, etc. What about the things that are harder to see like stress, pressure, demands, wear and tear, burnout, changes in physical ability, mental ability, and other unseen costs. What if we just try to build on what we have? That's what we are doing right now. What if we just kept going and didn't try to redo everything? Just keep refining, polishing, and tweaking things as needed. Still a lot of work, but it may be a better solution (at least right now). I was thinking about fracture (future project) and where we want to go with that project and those pieces.

 
No po photos available. Click to view time details.
Shop 8013 Checking in with Developers - Alan and John 8/25/2021  

Cory and I touched base on a couple of projects. Alan and John then joined and gave us some reports. Alan reported on his sub inventory model and his unit testing. It was going good but it is currently breaking. He will check this out and push the ball forward. His sub inventory model is being worked on outside in the ecommerce area. Once we get it working good and smooth out there, we will bring it inside and replace some older code with the newer object model based code.

Alan then did some reporting on some Adobe ColdFusion training that he participated in. He had lots of notes. These are a few of the notes that I took from his notes (secondhand notes).

- On the Application.cfc's - using the request scope - great place to put actions that need to be done or checked on every page.

- Lots of info on the cfc's and how the onRequest methods and code works. Also notes on onApplicationStart, onApplicationEnd, onSessionStart, onSessionEnd, onRequestStart, etc. Places to put code that gets called and used over and over again.

- ORM - Object relational mapping

- Lots of new ways to auto create getters and setters.

- Being able to handle mapping in both directions - one-to-many and many-to-one - this was a way of using a cfc (component) as a super simple database type structure without really having the actual database. We may need to look into this one a little bit deeper (need some clarification and more info).

-  Error handling and using try/catch better - Currently, we mostly use a catch "any" to do our error handling. They were recommending that we use special try/catches with type database, type syntax, and then the general "any" catch.

- Security stuff and watching for spoofs and things coming from other or outside sites. There were ways of passing tokens, generated on our site, and then looking for those tokens on the action pages. There were also ways to flip flop and rotate session values. Basically, let them login, set session scope values, and then auto switch certain values just to make sure it was a valid request from our site. Lots of little security ideas and hack prevention stuff.

- They are recommending that we use a new pdf tag called cfhtmltopdf (cf html to pdf) vs the older tag cfpdf - faster rendering and more options to offload the work to another server.

- Setting properties and then getting those properties to create auto getters and setters.

We encouraged Alan to keep checking for new code, keep learning, and keep pioneering some of these new concepts and new code options. Good stuff.

After that, Cory and Alan were talking about ecommerce and subs and parent line items, rules for picking and fulfilling packages assignments, tiered pricing, etc. They got into some order of operations. Cory and Alan were also talking about other ecommerce needs and options.

John reported in. He has been busy moving and getting settled in. He has made a small proposal for the year end payroll and tax forms (W-2's and 1099's) that he would like to get approval on. We haven't had too many developers create their own proposal that want to get approval. Interesting. I think he is asking for more documentation for his projects vs what we normal give him. I think he is lightly asking for more guidance vs flying by the seat of his pants. Lastly, Cory went over some other projects with John that we need his help on. They are the discount engine and the adilas quick search stuff. Good meeting.

 
No po photos available. Click to view time details.
Shop 8108 General 8/11/2021  

Working on getting projects finished up and off my plate. Working on the custom data extract project for sub inventory for Emerald Fields. This sub inventory extract required some data flip flopping. We pulled a query, pulled a number of other supporting queries, built an array of structures (objects), looped over the data, manipulated and filtered the data, and then pushed the results back into a query object to show and display. Kinda like data gymnastics.

 
No po photos available. Click to view time details.
Shop 8040 Adilas Time 8/11/2021  

Danny, Sean, and John were on the morning meeting. We checked in and chatted for a bit. Danny and Sean were talking about email templates and using some of the new things that Danny has setup and created. After that, we all went on mute and just started working on our own projects. I went back to finishing up the custom data extraction project for Emerald Fields (a client). The project involves going and flip flopping between different data types to get a complex sub inventory report to pull and be formatted correctly.

 
No po photos available. Click to view time details.
Shop 8014 Checking in with Developers - Alan and John 8/4/2021  

Cory and Alan were chatting and touching base on some projects. Alan is working on the transitional invoices project and how to recalculate prices based on tiered pricing. Alan is also working on breaking things into different objects and different levels. Those may be objects that are specific to a subject or objects that exist within a certain playing field (like out in ecommerce land). He also reported on some changes to sub inventory and sub inventory objects and logic (new objects) out in ecommerce land. Lots of refactoring and experimenting. Once we figure things out, at different places, we roll back around and try to implement those pieces in other areas (like the internal shopping cart or within the secure environment).

Alan and Cory then went over some Metrc and delivery bases questions. Some of the discussion was dealing with options for auto processing certain pieces and/or values within the delivery API sockets and functions.

After Alan was done, we switched over to meeting with John and getting a report from him on his projects. Cory and John were chatting about updates and small tweaks that are still needed. We are getting closer on the payroll project for the holiday chooser and timecard flags and total time project for payroll. We still have a few details to work out and refine but getting much closer.

 
No po photos available. Click to view time details.
Shop 8043 Projects 8/2/2021  

Ended up backing out the code to show the flex grid output both above and below the customer logs for clients with multiple log notes and flex grid tie-ins. The ladies thought that it looked too busy. Good call. The new code was backed out and new files were pushed up to all servers.

Switched gears and ended up back on the massive custom sub inventory data extract for a client. Towards the end of the session, I had to help make a small fix for Danny on his new email templates. Light tweak and then we re-pushed his code up to all boxes.

 
No po photos available. Click to view time details.
Shop 8230 Sub inventory data extract 7/30/2021  

Working on the sub inventory custom data extract for Emerald Fields.

 
No po photos available. Click to view time details.
Shop 8075 Working on a custom data extract 7/29/2021  

Back on the sub inventory searches and custom data extract reports. Working with sub inventory attributes, packages, and data. Lots of planning out ideas and working through the process. Lots of scratch level planning. It gets pretty deep. Imagine thousands of parent items with multiple child or subs per parent. Then you have to check almost 60 sub attributes and do a text based match from 60 down to 7 attributes that need to be displayed. Major funnel type project of slimming things down for a custom data extract.

 
No po photos available. Click to view time details.
Shop 7935 Working on custom data extracts for a client 7/28/2021  

Custom data extracts and special queries for a client. Deep SQL queries and reading up on outer joins with aggregate functions. Helping John with some data for his local balance sheet. He has a project that deals with special formatting of columns and data totals on the balance sheet. After that, back on the advanced data extracts. Ended on the sub inventory extract. It got pretty deep with all of the sub attributes and custom mappings.

 
No po photos available. Click to view time details.
Shop 7998 Server meeting 7/27/2021  

Cory, Steve, and I on a meeting. Small show and tell - fusion of ideas - adilas is a giant puzzle.

We were checking in on projects. Cory had a small list of projects to follow-up on. We talked about image caching and possible ways to bypass things for part categories and product images (out in ecommerce). Those ones are viewed externally and our clients really want to be sure that they are up to date and what they think that they are set to. They, the images, really change, but the browser caching is messing with it. If they look at it, it appears to remain the same (behind the scenes it has the same name, so the browser thinks that it already has a copy of it - caching).

We also were looking into a possible bug on sub prices on sub inventory. Alan joined and they were looking into things.

 
No po photos available. Click to view time details.
Shop 7963 Alan and John project review 7/14/2021  

John, Alan, Cory, and I got on a small weekly update. John and Cory were touching base on projects and priorities. After that, Alan and Cory touched base on some projects. Alan is working on sub inventory, tiered pricing, and had a few questions about sales tax on subs and tiered pricing. Good reports from both of them (John and Alan).

After the other guys left, Cory and I spent some time going over projects, code sign-off procedures, next steps, and cause and effect chains if there are errors or issues. We touched base on the paypod project scope and also the custom data push for Emerald Fields and custom database tables that they need.

 
No po photos available. Click to view time details.
Shop 7960 Bryan, Brandon and Cory review Paypod 7/1/2021  

Originally, we were going to have meeting with the Paypod folks. Cory found notes from 4/29/21 meeting with Aaron Stone and Bryan has a recording from meeting. We will review and determine steps of project/strategize. Will wait to meet with Aaron until we have next round of questions.

Just Cory, Sean, and Brandon were on the meeting. Cory asked me to help chase down a small invoice line item but. We looked and looked, but couldn't find anything. Finally, Cory found it after looking everywhere else. It ended up being on some new code that was added for mini units and sub inventory stuff. It took both Cory and I to find it. I honestly would have missed it, if it were just left up to me on this one. I was checking everywhere else, but Cory found it and we got it fixed. Great catch on her behalf.

 
No po photos available. Click to view time details.
Shop 7968 sub search 6/30/2021  

Bryan joined the meeting and had a couple of questions. He needed some training on doing sub inventory searches and how to pull some of the sub info back out of the site. We then spent some time trying to find a small bug. We went over some balance sheet logic and info and did some training there. Hopefully, Bryan will take that info back to a client to help them get going in the right direction.

 
No po photos available. Click to view time details.
Shop 7913 Alan and John project review 6/30/2021  

Meeting with Alan and Cory. Alan is pretty deep into sub inventory settings out in ecommerce land. He and Cory were going over questions and going back and forth a bit. After Alan left, Cory and I worked on some small data table fixes for a printable vendor list. We also talked a little bit about cash flow and ideas for getting the funding that we need.

 
No po photos available. Click to view time details.
Shop 7830 Adilas Time 6/28/2021  

Danny and Steve were chatting and checking in on the message marketing options and what the next steps are going to be. We talked about a small little mini app that would be native to the client's phone or device that would ping the correct servers for the correct client id and any possible message marketing options. We talked about making it native for android and iOS (apple). We drew out some ideas and concepts.

Alan had some questions about sub inventory and adding new custom and automated logic out in ecommerce land. We went over all of the different fields and the data that we record and store per item (part number), per parent line item (invoice or quote or PO line item), all sub inventory values, and what options we have there. Alan was lightly proposing a change so that the main time sub inventory tables would just hold the packages (main lot, batch, or package info). We would then build another table to handle and track the sub inventory transactions in a new table. Currently, all of that is done in one table, but it expanding and somewhat bloating the table. Lots of talk about ideas and options and timing.

We are not planning on jumping on this project right this minute as we have some other fires and things that we are working on. When ready, we will circle back around and check things out. I also mentioned to Alan that we need to make these tables easy to get data into, easy to pull reports, totals, sums, and also be able to go (virtually) backwards in time based on dates. We also talked about histories and the need to add histories in for sub or child inventory. Quite a bit of talk about some future plans, including adding some more backward compatibility options and look-ups for the custom data tables (sub string, sub numbers, and sub dates). Currently, we can get the data into these tables pretty easy, but searching them requires lots of joins and virtual jumping around.

 
No po photos available. Click to view time details.
Shop 7911 Project review with Alan and John 6/24/2021  

Helping Steve with some looping logic and prefilling arrays to help match with his other math and pagination options.

John, Cory, and Alan checked in and gave reports. We ended up looking up an edit PO cost bug. It was recording an extended cost for the main parent item not the individual cost per item. We got it fixed and pushed up the new code. Small discussions about different projects, new settings, and sub inventory rules and logic.

Steve and Alan got into a discussion about web pricing, tiered pricing, and items out in ecommerce land. Lots of moving pieces.

 
No po photos available. Click to view time details.
Shop 7871 Work with Shannon 6/24/2021  

Met up with Shannon. I has been a few weeks. We did some catch-up and I reported on how the conference went and lessons learned. Good stuff. We then started back on info graphics and trying to harvest some of the existing pieces that we've already done. As Shannon and I talked, I was reminded of a few little things that are on post-it notes and in notebooks that needed to get finished. It was good just to get back in the mode.

I fixed a small error with the online glossary. It was flipping folders based on session values vs sticking with certain hardcoded values.

Cory joined the meeting and had some questions about sub inventory and PO line items. We looked at it and then texted Alan to see if he was working on anything in that area. We tried a few things and everything seemed to be working just fine. We ended up tasking Cory to see if she could get on with the client who was having an issue and see if we could duplicate and/or record what was going on. We couldn't find it in our tests and experiments.

 
No po photos available. Click to view time details.
Shop 7829 Adilas Time 6/23/2021  

Eric and I pushed code to end a custom loyalty points program for a client. After that, Sean and I looked into a possible problem with new sub inventory tables. We ended up getting Alan on the GoToMeeting session and going over things. It looks like the table creation code wasn't handling unsigned decimals correctly. We looked into it and Alan sent me a fix that I uploaded to all servers. He will go back and fix any other problems. This is all dealing with new tables, not existing tables.

 
No po photos available. Click to view time details.
Shop 7765 Adilas Conference & Training Event - Salida, CO 6/7/2021  

Multi-day conference in Salida, CO - birthplace of adilas.biz! If you spell Salida backwards, you get Adilas - All Data Is Live And Searchable

Small Recap:

The adilas team meets almost everyday via GoToMeeting and Zoom meetings (virtual online meetings). Having said that, we have not had an in person conference for almost 3 years. Our last major conference was in September of 2018. The live event was much needed.

The adilas team met up on Monday evening and did a small meet and greet - ice cream social. We then went over to the hotel and conference center. We setup up systems and did some testing. Crazy, but sad, the hotel was having major Internet problems. We setup some mobile hotspots, but it just wasn't enough.

Tuesday morning we started the conference but the Internet was super slow and was dropping the GoToMeeting session, audio, recording, and even basic site browsing was going super slow. We tried using the GoToMeeting options for the first two sessions. After that, we ended up just presenting to those who were on site. There were about 20 individuals there on site. Once we dropped the GoToMeeting piece, the whole attitude of the conference shifted. From my personal opinion, the change was for the better. Much better flavor and things started to flow much better.

We had more folks join us live on day two and day three of the conference. Great stuff. Those who were there were treated good and everybody was learning new things. As a huge shoutout, three ladies spent a ton of time on training content, slides, and presentations (including timing, samples, etc.)

Marisa got a bunch of shirts for adilas with the little blue dog avatar (ADI). The guys and gals looked great in the adilas shirts. As usual, Mrs. Shari O. took great care of us and had snacks and lunches for us each day.

///////////////

See attached for some of my notes... I will also put a few of them there below for searchability. My notes that are attached have a lot more details. I just wanted to capture some of the tweaks and user requests that we picked up from the conference. Not all of my notes are just what needs to be updated (for the record), most of my notes were dealing with what the guys and gals were presenting:

- Request - We should not allow new default payments as "show" they should be hidden by default - this is dealing with money types under more options under the corp admin page.

- Request - They wanted Venmo as a payment type

- Request - Remove the Flash option for my cart favorite buttons - under personal profile

- They went through all kinds of setup and settings - being consistent to get things out of the system later on

- Request - Adding in a date picker to the add/edit pages in elements of time. It is currently there, but if you have the HTML enabled SummerNote editor, there is a conflict between the two features. They both use a form of jQuery.

- Small side note on the presentations - Kelly was doing slides on a PowerPoint, Marisa was driving (clicking through adilas), and Danny was presenting - fun combo and good flow.

- Prototyping and then expanding those things

- Request - On the customer log notes, try to add in the date pickers and the SummerNote HTML editors (small conflict)

- Request - On the balance sheet quick search - be able to pull the balance sheet by that date, using the quick search. That would be pretty cool!

- We sure want to get back to a project called "known issues report" - Helping to find things that are known problems or disconnects

- Request - On sub inventory templates, it needs to default to active. Currently it defaults to inactive.

- Kelly and Steve did a great job showing some down the road cause and effect relationships for categories, inventory controls, and other sections in the inventory controls section. Great little session.

- Request - On the advanced part and parent attribute search - They may or may not want some of the inactive parent attributes on that report. In the Farm and Ranch demo site, there were tons of inactive parent attributes that were showing up. Small clean-up.

- Use of the word core - parent cores, child cores, etc.

- Request - On smart group buttons, the description modifier does not currently change the sub description. It only changes the parent description. It should change the sub as well.

- The power of being able to save your own reports

- Save time and money, adilas has a solution built-in (talking about ecommerce, but it could be anything)

- Request - On ecommerce, change some of the verbage on the photo image sizes - make them square (item pictures and item category pictures), if possible. Say something like 750 (_w) x 750 (_h) vs 750 x 553. Square works better on the web, helps make it all line up correctly.

- Request - On ecommerce, the parent attributes on ecommerce show all items with certain tags. We need those counters to filter what was/is really available - For example: Drinks(2) - but when clicked, only 1 (one) showed up. It would be better to show Drinks(1) and then show just that one. That shouldn't be too hard to fix. Maybe just look to see how those item counters and counts are calculated.

- Request - On login into ecommerce, it would be so awesome to have a new setting to say - Where can we take you after a valid login? My details, shop home, make a payment, etc. that would be cool! Basically, let the client/users dictate where to send their customers upon a valid login. Right now, they always just go to a single page and then have to click from there where they really want to go.

- Request - Build a customer marketing link builder page, this would be a page similar to the add/edit my cart favorite buttons (limited), but thte main feature would build a link, add to cart, set a discount, tract a campaign, add a coupon, auto login, etc. Build whatever link you needed, without knowing all of the techy stuff behind the scenes. Make the links so that they may be used in marketing messages, emails, texts, ect. The person who builds it, enters info into a form and the form (backend logic) builds the correct link for the client. Basically a special marketing or link builder tool.

- Request - Add some terms to the glossary such as: Modal, ADI (the blue dog avatar).

- Request - Make the "all help files" more flexible and be able to search the descriptions as well. Currently, it only searches titles for the help files.

- I can't wait until we can show the daily balance sheet over time - multiple day report running over or off of the aggregated totals

- Request - Look into the add new B.S.I. item process - We may need some more flexibility on the account and item groupings. Also, a request was made to allow for setting up the expense types and deposit types right from there as well. Basically, a one-stop shop for balance sheet setups.

- The value of education and being able to help set people and users up for success

- Understanding logic and cause and effects

- Idea - It sure would be cool if due dates could show up on a calendar type view - think of showing all kinds of stuff on a calendar type approach or view

- Request - New settings - Expense/receipts and locations on line items. Also, B.S.I. bump up or down values. More settings.

- Take time and read the page errors and info stuff - We are trying to help - Slow down just a bit

- There is a need for some cash flow and budgeting tools - This would be awesome - Maybe round 2 on the financials

- Request - Ice-down dates and being able to "post" on invoices and PO's - Posts only exist on deposits and expense/receipts

- Data visualization and customized dashboards - We haven't even scratched the surface yet - It's time!

- Request - On the media/content homepage and media/content advanced search pages - It would be nice to output or show the reports in Snow Owl data tables to help with exports and visual displays

- Following your interests and be yourself!

 
No po photos available. Click to view time details.
Shop 7747 Developer weekly update 5/19/2021  

Weekly meeting with Alan to go over projects and code stuff. Both Cory and Sean joined us on our meeting today. We started out with Alan reporting on his current projects and findings. He was working on a page and did a search and found a number of other similar pieces (say 500 ish). He is currently refactoring that part of the application and going to be replacing code so that it runs more efficiently. The code happens to be dealing with custom page settings. We use these custom settings to store both corporation specific settings as well as user defined settings for different pages and sections. We gave him the go ahead to do a little bit of maintenance and refactoring - prepping for the future. Maintenance sometimes isn't that fun, but it plays a key role in the life cycle of a system.

The last half of the meeting was turned over to Sean to show Alan, Cory, and I some of the new stuff that he and Steve have been working on. We logged into a client's site and Sean gave us a great demo and tour of the orders homepage, backorders, fulfilling orders, training amounts requested, remaining, filled, etc. Steve and Sean have been busy. Here are some other notes from the meeting.

- As new features are developed and released, we need to make sure that everybody knows about them - sometimes distributing that information is a big challenge.

- We build special quotes without having real inventory to back them up... Then as the real inventory comes in, we distribute and fill the correct orders. This is a whole new section of the application and Steve and Sean are out there pioneering things.

- The quotes just hold parent items or parent placeholders. Then as the invoices are created, the real parent/child relationships get put in place on the outbound invoices.

- The orders and backorders homepage has three main ways of viewing and sorting the data. It may be vied by quote (order), by item (what orders want what), or by customer (what other things are they still waiting for). Pretty cool!

- Lots of great demos and showing us flow, approval processes, pagination (next page of n), drill-down and filtering options.

- We are gaining some good traction by getting a client who wants something, doing some planning, putting a MVP (minimal viable product) out there, beating it up and refining it - with some hand holding, and then officially releasing it to the public as a new feature. Nice little process.

- Sean also went into some new pages and sections for mini units. This is serialized units that are within the realm of parent/child inventory. The parent is the primary placeholder. The sub inventory or child inventory are the new batches or packages. Then within the new batches or packages, the individual mini unit data is help and recorded. It also shows usage on where it came in, where it went out, etc. (PO's and invoices). The whole process has a tons of great new features.

- Lots of talk about relationships and one-to-one, one-to-many, and one-to-many-to-many. It can get deep, but sometimes that is needed. We play in bulk where possible and then record individual data (and maybe even hide it unless asked for). It makes it look simple, but the whole story is really all there, just nested and/or strategically buried or hidden.

- We spent a bit of time talking about the pains of trying to keep multiple sets of records and juggling multiple systems. We are trying to relieve this burden, but sometimes the transition process is difficult. We have found that clients are so busy, they almost always need a person or small team to help them transition and get the training that they need. Without this, they end up failing on the transitions (switching over).

- Sean did a great job. I was impressed with his demo and knowledge of the system. I can see him doing more and more of that type of thing. He gets in there and spends the time to learn things (tips, tricks, etc.). That makes a difference.

- The value of real live data and real live work flow testing. You have to have a client who will play along, but you gain a ton from that tight of an interaction and/or relationship.

 
No po photos available. Click to view time details.
Shop 7797 Alan Brandon Steve item catalog deep dive 5/17/2021  

Alan, Cory, Steve, and I on a recap and planning meeting. Alan was going over a recap of the enterprise models and the enterprise vendors. Our next goal is to get into enterprise items and enterprise parts.

We did some planning on the next steps. Moving into the enterprise levels for parts and core items in the system. We talked about locks, permissions, images, media/content, and sharing or using enterprise level catalogs. The upcoming needs will be enterprise level vendors (done), part categories, parent attributes, sub inventory attributes, core parts and items, etc.

Cory went in and showed Alan some pages with parent attributes. Light training.

We then had some small talks about reworking sub inventory options before we turn them into high level catalogs and enterprise level models. They need to be refined a little bit deeper on the transactional systems first. Our current priorities are: part categories, units of measure, core part values, photos, and media/content. The parent attributes and sub inventory attributes will need to wait for a bit.

Lots of talks about conserving data and conserving space on the database, based on these mappings and enterprise level tools. Lots of data normalization and control.

Steve and Alan talking about funding and what the future plans are - new markets, refining our product, and playing into new markets.

If we make these high level catalogs - what if a vendor could almost dictate to their distributors what they get and what they want? That would be so cool! Steve and Alan were dreaming about ideas and where things could go! It was fun to listen in and hear some of their ideas.

After Alan left, Steve and I chatted for a bit about our crew and future plans.

 
No po photos available. Click to view time details.
Adi 2016 High Q Kush Cart edits 5/13/2021  

Add customer type
Don't cross off price when there is no change in price due to discounts on other items
Add pink warning for not enough sub inventory

 
No po photos available. Click to view time details.
Shop 7744 Developer weekly update 5/12/2021  

Alan and Cory were on the meeting. The main topics were transitional invoices and new Metrc changes. We got into sub inventory assignments and moving things up and down the chain. We also talked about table locking and managing any possible duplicates (dups). It always comes back to accuracy vs speed.

Cory and Alan then spent some time going over the vender aggregates and permissions (vendor catalog). They were going over corporation switching, some small errors, and how much people are going to love some of the new enterprise level tools that are being built. Good stuff.

 
Click to view time photos.
Adi 2011 Misc Code Issues 4/22/2021  

2/14/23 uploaded the following files to data 1 and created a video.

basic_logo_header.cfm, show_printable_invoice.cfm, plain_logo_header.cfm, black_and_white_printable_invoice.cfm, black_and_white_printable_invoice_body.cfm, mini_invoice_body.cfm, print_limited_invoices_body.cfm, print_simple_invoices_body, print_sumary_invoices_body.cfm, mini_invoice.cfm, print_limited_invoices.cfm, print_simple_invoices.cfm, print_summary_invoices.cfm, printable_invoice.cfm, settings_printable_invoices.cfm, settings_printable_invoices_body.cfm.

12/15/22 money type eXPO to Herbo.  Created update_20221214.cfm and edited update_home.cfm.

11/21/22 1. Show-hide category overrule in show on web & 2. default vender type when adding po.  Edited the following pages: adilasWeb.cfc & add_edit_parts_body.cfm

11/1/22 completed adding hours column to grouped view of time home body (video).  Edited the following pages: time_home_body.cfm & requests_2.cfc

10/28/22 completed auto calculate time dropdown function on add_edit_time.cfm page (video). Edited the following pages.

add_edit_time_body.cfm

add_edit_time_action.cfm

10/27/22 completed Domain Name Replacement project.  A record of the pages changed is in the photo/scans and a link is here.

10/27/22 completed PayPal project.  View video of setup and function here. Edited the following pages:

corp_admin_settings_body.cfm

ecommerce_home.cfm

payment_gateways.cfm

payment_gateways_action.cfm


10/25/22 checked and pushed sub inventory default to active, add 2nd vendor dropdown to duplicate expense page and added currency switch to digitech code.  Made changes on the following pages:

duplicate_expense_receipt.cfm

duplicate_expense_receipt_action.cfm

sub_inventory_templates.cfm

sub_inventory_templates_action.cfm

digitech_payment.cfm

4/22/21: Catch all for misc code issues

 
No po photos available. Click to view time details.
Shop 7513 Adilas Time 4/19/2021  

Steve and I were looking at a data import template from Kelly. Trying to get her a good sample. She sent us some data and we sent it back with a few tweaks and requests.

After that, Steve and I looked at a new sub inventory report that he is building. It is dealing with both core part/item attributes and parent attributes (dynamic and able to cross over part categories). The report is looking good and Steve is making great progress on the report.

Part of our goal, everyday, is to keep kicking the ball (or the can) down the road - little by little. We call that progress.

Steve and Sean started going over some of the new mini unit stuff. We also did some follow-ups on sales leads, demos, and appointments.

 
No po photos available. Click to view time details.
Shop 7649 Deep dive on AWH reports-Kelly, Steve, Cory Brandon 4/12/2021  

Great meeting between Cory, Steve, Kelly, and I. The main topic for the meeting was talking about some advanced inventory (both parents and subs) search and export feature. The new report would bring together pieces from the main invoice tables, PO (purchase orders) table, parts (parent items) table, sub inventory, sub attributes, and parent attributes table.  This will end up being a combo type report - pick from viewable options, add filters and sorts, view report, get export, and be able to save the report for quick reference and usage.

Kelly had some great ideas as we were talking. Not all of these are directly from Kelly, but she was providing a bunch of these:

- Our clients, like to record the data and deep details about their inventory and their processes. However, once recorded, they need searchable and exportable access to all of the data, at every level. Basically, they want to get it back out (be able to use the data).

- Be able to point and click, name, and save the reports - under my favorites

- Lots of talk and ideas about parent attributes - how to help collect that data, how to show the data back in reporting, how to use it outside in ecommerce for marketing and stats.

- Talk about multiple or disconnected pages. All of the pieces are there, it could just use some more defined and simplified flow - workflow or data flow (interface and UI stuff).

- One-pagers - build in options for core part/item values, parent attributes, sub inventory attributes, all from one page and/or interface - our users are wanting more one-pagers.

- Kelly was saying - "The juice isn't worth the squeeze" - basically, the results are not worth the effort (at times). We need to find that balance point. More intuitive and more simple.

- Currently, they can do everything that they need to, but it requires some back and forth and even multiple touches (between add and edit) for certain pieces. The recommendation was to go clear back to the PO's and new item creation process. Maybe even allow for certain things to either be defaulted and/or hidden to make it more simple.

- Some of our conversations got into the next gen (next generation) of sub inventory and being able to allow sub attributes to flow across part/item categories. Parent attributes can flow over or across categories but sub attributes currently can not cross those boundaries. Kelly would like us to allow sub attributes to cross categories. Great idea, it may take some recoding and restructuring, but it could really be advantageous.

- Computer sprawl or digital sprawl - build, build, build - sometimes even without a full plan (like urban sprawl in certain neighborhoods).

- Training "if/then" statements is hard to do, especially if there are deep branching logic choices and consequences.

- Eventually we will want some great reporting for ecommerce and even activity out in the ecommerce land - not just buying but even browsing trends and client behavior and habits.

- Core attributes - currently, we sometimes call these the main attributes or main data fields. We will be using the term "core attributes" more and more to mean the main or primary fields or values for a certain group or section (12 main system players).

- We can use some of our existing code and snippets to build these new pieces. That will really help. We experiment all the time, let's harness some of that development.

- New term - web core or web core components

- Getting into marketing and customer trends and searching info (BI - business intelligence). Aggregating the data, even backend usage and stats (clicks, usage, page views, time spent per page, unique visits, and other demographic type stats). Everything is heading towards marketing and analytics.

- How can we speed up these processes? We know what is needed, we just need to figure out how to best wrap this or this whole thing (processes and procedures). That is one of the big challenges. The good things is, we've figured out a whole bunch of the smaller pieces already, let's just go to the next step.

- Breaking up these huge projects into smaller or bitesize pieces - that is big key to allowing multiple people and/or parties to play the game.

- Dealing with breaking things up, not only the projects, but maybe the UI (user interface) options. Things such as accordions (collapsible sub sections), show/hide pieces, tabs, dynamic - on the fly content and choices, cards, and other cool layout options.

- For this round, we are shooting for a mix between the advanced customer search reports and the save as my favorites (saving the reports).

- What about going back in time? Certain reports work really well for showing current (just in time) values and counts. What about being able to ask the system what was going on or what things looked like back in time (at a past date). Current (right now) vs going back to a date/time in the past. Playing with objects and data over time.

- We want to get to some futuristic or some predictive type reports in the future. Watching tends, alerts, and forecasting.

- The only way we can do it is to go step-by-step and take it slow. Sometimes we can only see just around the next corner, we can't see all the way to the end. One step at a time. That is ok!

- Towards the end, we got into some talks and conversations about building templates and virtual starting places for the next person who has to pick up the pieces and play the game.

- Steve and I will be working together to build and develop some of these pieces. Once we get things pioneered out to a certain level, we may get some others involved. Sometimes it is too hard to convey they whole vision. Sometimes, getting someone started so that they can see a little ways down the road really helps that process out.

- On data imports, it really helps us (the backend developers) if there are both human readable fields (text and verbage) and computer readable type fields (id numbers). Helping to prep for the next person down the line (who is who's customer).

 
No po photos available. Click to view time details.
Shop 7654 Review of Back Orders 4/1/2021  

Steve reported on a meeting that he had with a payment kiosk company. They were talking about both accepting payments and even doing possible pay outs (monies going out based on approved expenses). That could be pretty cool.

After that, Steve and I did a work session and did some review of adding sub inventory to the back order process. We worked our way through a checklist and actually doing the coding to go along with our hypothetical path (our prior mapping of the logic). Fun session.

 
No po photos available. Click to view time details.
Shop 7482 Adilas Time 4/1/2021  

We had a bunch of guys on the meeting this morning. Sean and Marisa were asking questions about using sub inventory out in ecommerce. There are tons of different settings. Ecommerce was not designed for the customer to be super detailed, like they are inside the main system. Out in ecommerce, they just say something like - I want this and that. Behind the scenes we have to check packages, counts, quantities, and other availability. This makes it kinda interesting... We have to play in simple requests but record things in crazy levels of details.

Steve was helping to guide the discussion. He did a great job and it was fun to watch and participate. We ended up having Alan pop in and go through things. As he was talking, I was scribbling down notes, ideas, and such. There are so many moving parts and pieces. All part of the same game or same puzzle.

We got into some Metrc and state compliance issues and needs. We ended up checking out some data for a client. They had added things, removed things, set things to inactive, voided things, and adjusted quantities using adjustment tools in the system. A complex series of events and timing. Also, different things done by different people. Thank goodness for histories being kept and maintained by the system. We ended up having Sean and Marisa do some fixes and then reach back out to the clients to let them know (passing on the knowledge and info - training).

Putting in another plug for a couple of other things that we still need to build out and/or refine a bit:

- We need to add a history table for sub inventory. The table already exists, but has not yet been wired up. That would really help.

- A quick search tool for RFID tags, media/content (files and links), and sub inventory attributes and packages (batches). The quick search already exists, we just don't have those things listed in the available search options. That would be really cool.

- The story about what is happening is so important. Eventually, it will end at a certain state or status, but what happened to get it there is huge. That's where the history and story comes in.

- We added more to the known issues report and known issues list. This will become part of the master code branch so that we can gather up ideas and such. We are hoping to get this report and tool out soon. Still under construction, but coming. Yeah!

- Steve is doing awesome on JIT (just in time) project management and delegation. Super fun to watch him work today.

- Steve and Kelly were on a meeting earlier today - as part of that meeting, they were using elements of time (calendar objects) to schedule recipe/builds to happen on certain days (production). The elements of time hit the calendar and the individual elements of time had links to fire off or do certain recipes on certain days. Creative use of both tools and mixing them together. As a side note, we are seeing elements of time being used more and more to coordinate and orchestrate different pieces as needed. So powerful!

-  There is a value of group trouble shooting and putting the puzzle pieces together. Not too many, but enough!

- Some of the jobs and tasks require planning and even pre-planning.

- We deal with moving targets all of the time - static (non moving) vs dynamic (constantly moving)

- Out in ecommerce, we have different levels. Inside the system, we help take the users into deep waters, based on permissions. However, out in ecommerce, we need to keep it simple (customer view and customer level), yet eventually we need the deep water info. What do we automate and what do we leave or make as a human type interaction? There is a balance and not situations are the same. Wouldn't it be cool if we could virtually setup the data assembly line with automated tasks and manual entry tasks. We can do that, but we have to be involved every time. Wouldn't it be cool if we could build the tool to help configure things as needed and have it all tied into the big picture software package or system app. Let's keep working towards that!

 
No po photos available. Click to view time details.
Shop 7651 Meeting with Steve 3/29/2021  

Meeting with Steve to go over some ideas and plans. Steve has been on fire today. He was pitching new ideas, lining out developers on small steps to bigger projects, and showing me new code that he has been working on. Fun to see. He has a lot of vision and loves to share it and push it along. That is awesome!

Here are some random notes:

- Steve's vision is great! He's been the primary visionary person throughout the years.

- Creative direct messaging options, using HTML compatible customer log notes, that populate out in ecommerce land. This could be controlled by settings, push notification to the user's or client's phone, simple one click login, possible bulk tools on the build and send side, ways of skipping or marking things as read on the user/client side. All kinds of fun ideas. As a side note, we already allow unlimited customer logs or customer log notes. You can already mark them as show on the web, and they will show up outside in the ecommerce area. All we would need to do is tweak that tech a little bit to turn it into a two-way messaging app. If we wanted to... just an idea at this point.

- Steve is working on the mini units project for a gun and firearm dealer. They can set a flag at the part or item category level. It says use or don't use mini units. A mini unit is a sub section under child or sub inventory. The sub, or package, could have multiple subs or serialized pieces under the sub inventory. The mini units project allows for something to be sold as a sub inventory item in bulk, and then as the invoice gets fulfilled, the different serialized pieces could be added in as details of the bulk entry. To explain, say you wanted to sell 10 of a certain item... The invoice would say sold 10 of XYZ item. Then, inside the system, you could tie in special serial numbers to all 10 of those mini unit items. This becomes a mix between a normal stock/unit (one-by-one serialized inventory) and parent/child inventory with granular control and ability to sell in bulk (simple line items on an invoice, but more details held in the background).

- Steve and Sean are going through different scenarios and figuring out processes and procedures. They are then making notes and coming up with solutions. The two of them have been able to work very well together. That is awesome.

- Steve sees one of our core values as being able to listen and hopefully understand what is needed. We are then able to make a plan to fill those needs. That is what adilas has been doing for the past 20 years. The market is talking and leading out with what they want and need, how can we build and capture that market?

- Sometimes the best thing is just taking the next little step. drop by drop, inch by inch, line by line.

- How can we capitalize on what we are building and basically inventing? We love doing R&D. We just need to help it start paying for itself.

- Steve really likes building contacts and doing social networking as a way of getting the information out and selling the product. He really likes, small, on the ground sales team that work and play well together. We pitch it, we sell it, we deploy and do setup, we help train and maintain the clients. We use small internal teams to do the whole process.

- I heard Steve pitching the dependable independent model to one of our guys today. They, our guys and gals, really love that model. Having said that, it does take a special person to fully bloom there. Sometimes it takes some getting used to and/or adaptation of sorts.

- My goal is to help Steve. The two of us together can make a lot of things happen. Good stuff. Both he and I can do whatever and be ok with it. Good Batman and Robin type team.

 
No po photos available. Click to view time details.
Shop 7494 Adilas Time 3/29/2021  

There were a bunch of the guys on the meeting. Mostly just checking in here and there and running small things pass Steve and I. Wayne had some database questions, Steve was working on sub inventory with mini units (serialized units within sub inventory), and Danny was working on some new notification settings. After Danny left, Steve and Sean  went over the power of using web based customer logs as direct ecommerce marketing tools to their clients. Steve has a lot of details and vision on that. He is going to have Danny start playing and building along those lines.

 
No po photos available. Click to view time details.
Shop 7579 Weekly Server Meeting 3/16/2021  

On a meeting with Cory, Steve, and John - dealing with servers. Our plan was to just talk about servers, but Wayne was out of town. So, we chatted and split up to work on projects. I started working on the PO/Invoice line items table and recording sub inventory transactions at the point of sale. We really want to speed up some of the downstream queries that deal with sub inventory. It gets pretty deep, pretty quickly.

 
No po photos available. Click to view time details.
Shop 7490 Adilas Time 3/16/2021  

Quick merge for Danny and some new custom labels for Highland Vineyard. Steve and I then rolled into some talks about sub inventory and trying to help to speed things up through queries, logic, and database storage values. We would love to rework the po/invoice line items table and the custom dates, custom text, and custom numerics tables. They all could use a few more values to help better connect them. Currently, they are connected, but only through a series of virtual bounces and upward threads. We would like to make it more clear and more easy to get the data back out again. Here is some info that may help with this project: https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=4848

After that discussion, we got into other ways of speeding up the cultivation process. A lot of the ways we can speed things up is dealing with how much data we return and/or try to render out to the user, once they have completed a specific step. Eventually we will need to go clear back to the design and mock-up phase and/or stage. Simple drawings for what we want and then go build the dream. Right now, we just keep coding and fixing, coding and fixing. That helps to figure out the process, but it will definitely need a facelift at some time, in order to make it more efficient.

 
No po photos available. Click to view time details.
Shop 7367 Adilas Time 2/23/2021  

When I got on the meeting both Steve and Sean were working on a client's books and getting things to balance (backend accounting dealing with stock/units, outside repairs, and correct costing). Fun to watch them work. Like detectives looking for clues and mismatches.

Steve and I were talking about different clean-up processes, last modified records, and harnessing user clicks as a virtual assistant to help with clean-up and aggregation processes. Cool concept. We also talked quite a bit about how deep things get. There are so many moving pieces. It gets tough to keep track of everything.

As part of our conversation, we talked about simple implementations and going beyond that super simple level. As soon as you add in multiple levels, permissions, settings, sub locations, sub phases, sub inventory, and full backend and frontend accounting and operations - you have to go beyond the super simple, it just breaks down, if it's not deep enough. That seems to be the water that we swim in.

Just for kicks, once Steve left the meeting, Sean and John were still in there. We ended up talking about how cool it would be if the system could help you know where things were wrong or possible problems. Imagine how cool it would be if the system could tell you, things are off or out of whack here and there. That would be super cool!

 
No po photos available. Click to view time details.
Shop 7373 Adilas Time 2/15/2021  

Looking over some security stuff with Steve, John, and Eric. We were looking at cfqueryparams (Adobe ColdFusion Query Parameters). We also got into a custom report and looking at an update page with Steve for sub inventory attributes. This is a special date specific clean-up page for a client (bulk tool for sub inventory attributes).

 
Click to view time photos.
Shop 7395 Projects 2/9/2021  

Marisa has some questions about EDI (electronic data interchange) and API sockets. We told her that EDI and API's are very similar. EDI was more of a front runner, but most modern apps and systems communicate via API sockets. They are very similar in that it allows computers to talk to one another via electronic communication channels. She and Steve were also talking about other client messaging options besides text and email. Different types of push type notification based on elements of time and/or customer logs that are visible via a valid ecommerce or customer portal login.

Steve, Cory, and I spent the rest of the time going over ideas and brainstorming on aggregate totals, and moving grouped and pre-summed data up the chain. We did a lot of drawing and talked about different ideas. We know that the bottom most level or base of the pyramid is the transactional core or transactional data. We also know, that per world or per corporation, we need to get to the aggregated totals for the P&L (profit and loss statement or income statement) and the balance sheet.

Cory was taking notes... here are some of them that she passed over to me.

- ETL (Extract, Transform, Load) - this is how you work with aggregated data. You extract what you want, change or transform it into what you need, and then re-load or push it into a database in the stored or transformed format. Make it easy to get it back out.

- We have a map (using the existing adilas system from operations into accounting) - we need to follow it backwards. Be able to pull the P&L and balance sheet quickly and pull it in from one single query. Currently, we have to go all over the underlying transactions and data details to pull back the values. It would be so cool if we could aggregate things as needed, based on the current map that exists in the system.

- P&L and BSI reverse mapping? Let's look into it. What if we could start from the top and then work/map going down? Follow the flow of the data. There are many sub pieces that may need to be linked and/or aggregated together before we can pull the hard, fast, numbers - all from one single place.

- As we map things out, we know we need to deliver what they (our clients) want and also try to head in the direction we want to go as well. That can be challenging.

- Different levels of drill-downs. Balance sheet starts at Inventory levels (way up high), not at part categories, vendors, parent items, or sub inventory items (child items). Eventually, we have to be way up high for the P&L and balance sheet info. Then, as the user needs more details and sub information, they will do what is called a drill-down (going deeper into the details).

- Here are the main pieces for a P&L: Revenue, COGS, Gross profit, Expenses, Net profit

- Here are the main pieces for a Balance Sheet: Assets, Liabilities, Equity

- Futuristic goal: run the balance sheet and P&L over time all the way down to the second. Imagine a time lapsed view of your financials. You have to go from transactional data up to fully aggregated totals in order to get those numbers. Let it begin!

- Thinking about data... Am I tied to a corp? Am I tied to a location? What is my date/time stamp? Do I have a main category or grouping? Reports and financials by day are the current goal. Eventually, it could go all the way down to hours, minutes, and seconds. For now, we will focus on a per day basis.

- Think of a pyramid. Top most would be all pieces, all of the sums. Quick sums- held at the top. We want to capture and hold these sums or totals per day. Much less information at the top than at the bottom.

- Value added cores - we had a great discussion about how we want to use a value added core type model to help businesses run on adilas and also ways that we could monetize the different value added cores or levels that get added onto the main transactional core (the adilas system).

- One table with totals for each (top most level): Corp ID, Date, Revenue, COGS, Gross profit, Expenses, Net profit, Balance Sheet, Assets, Liabilities, Equity, Out of balance value (sum). These would be the top most corp or world level aggregation tables. Quick financials and numbers.

- We don't know how deep it goes yet, but imagine one table with totals for each level going down - until you get to the transactional data. Not sure how deep this goes yet? This might take more than one iteration to build and figure things out. For now, just pretend and start back filling as needed.

- We were talking about tracking things up to 4 to 5 levels deep. These are some of the existing pieces (verbage from the system): Destination/main title, main category/main grouping, sub group or sub category, vendors or types. We need to figure out the 4-5 deep path for all major pieces. For example: If recording revenue, it has a certain path. If recording an expense/receipt, it has a certain path. The same thing is true for things like: deposits, user-maintained balance sheet items, system-maintained balance sheet items, basically every piece of the P&L and the balance sheet - they all have specific paths and need to be at that 4-5 levels deep. Even BSI’s are 5 levels deep. Five levels should cover everything (for now).

- Talked about everything being under one database (new aggregated or math sum/count tables). If we feel we have reached capacity, we could always go out to another database (level 4- aggregated sums) or just add more tables. Lots of options. Once again, trying to figure out where the natural lines exists and what could be extra or add-on values.

See attached for some drawings that we were talking about as we were discussing some of these details and ideas.

 
No po photos available. Click to view time details.
Shop 7262 Adilas Time 1/28/2021  

Recording notes, going over new serial numbers for the adilas label builder app from Calvin, and touching base on other projects. Steve and John were going over some custom reports and what they needed, as far as new logic and/or tweaks. The reports were dealing with cross overs between PO's, elements of time, and sub inventory - lots of mixing and blending. Anytime you get so many things involved, it can get kinda deep, kinda quickly. Basically, the users love how it is recording the data (catching all of the data points), they just want the reporting to be super easy and almost know what they want without asking the system for it. It's just the next logical step, but sometimes, they get really demanding and add some crazy pressure. We just keep going and taking that next step. That's all we can do. Keep on faking it till you make it!

 
No po photos available. Click to view time details.
Shop 7293 Meet with Alan 1/27/2021  

Alan and I met up for an hour and went over a bunch of different projects. Alan reported on his corp object manager project (session based objects for corporations and corp-wide settings), logic and flow for Eric's EMV chip reader project, timeouts, error handling, and connections. We then got into the enterprise or aggregate vendor project with multiple corporation mappings and enterprise type relationships.

After that, we touched base on RFID tags and how they play into ecommerce based on settings and and usage. We also got into discussions about transition invoices, restore to cart, and how those things play with sub inventory out in ecommerce land. Lots of deep sub inventory stuff. We closed our meeting by going over some testing and automated testing and how that is going on some of Alan's new projects. Lots and lots of moving pieces. Sometimes it is tough to keep the big picture in mind and make sure that logic and data flow from piece to piece. It gets pretty big, pretty fast.

 
No po photos available. Click to view time details.
Shop 7338 Suzi and team, John Brandon Steve and Cory 1/21/2021  

- There was an original email dated back in July - Cultivation report for Ianthus

- Suzi and Philip from Ianthus were on the call - there were quite a few adilas folks on the call.

- Cultivation mapping - done by Dustin

- When a plat it changed from one phase to other phase, you auto populate those fields.

- They have some custom fields (sub inventory attributes) that they want auto filled when certain actions happen - changes of specific phases

- Maybe setting up which sub inventory attributes show up based on what phase. Also, does one or more of them have (sub attributes) a mapping from other data that is being entered up higher. It may take some more mapping. We may want to show/hide certain sub attributes based on the phases. That means we need to go through the process and really detail out what is shown and what is hidden. Along those same lines, they would love to set it up so that if a sub attribute is being shown, it can get a value or its data from one or more spots (other user entered form values). 

- Currently, some of the info that they are wanting to catch (automatically) is dealing with dates and sub dates.

- As a side note, because we allow each corporation build their own sub attributes, we then have to be able to show/hide and map out these pieces as they go through the different phases. The eventually need all of this data, but we are showing so many fields, it makes it more difficult. We are catching all of the data right now, it just isn't organized (visual report or visual form) to make it easy.

- Another thing that they were talking about was getting to those sub attributes later on - other reports  and passing that data along to other places.

- Just an idea... what if we build a phase builder type app - these would be settings, user controlled, and allow you to setup a single phase, what data to gather (maybe a point and click interface to setup what will show up), then the ability to setup defaults, show/hide fields, what to default things to, other data mappings, etc.

- There were some talks about back filling the data - separate tasks going backwards. Along with that, if we back fill things (update the data), we also need to build it going forward so it becomes an automated process.

- Eventually, they were getting into the nitty gritty details of each phase. The start of one phase sets certain values, the end of a phase closes things down (other actions) and also starts the next phase. We need to detail out each phase. I'm just dreaming here, but virtually a way to setup pods or sections of a virtual data assembly line process.

- The first phase would be a backfill type report - able to do things in bulk. They were talking about being able to select a PO date range and then applying specific dates to all line items on the PO. There were also talks about a PO number range.

- Light talks about required sub attributes and optional sub attributes.

 
No po photos available. Click to view time details.
Shop 7310 Bug fix 1/5/2021  

I got a call from Shari O. about a small bug in the older classic version for sub inventory. Both John and I jumped on a GoToMeeting session and made some changes. We pushed up a new file to fix it.

 
No po photos available. Click to view time details.
Shop 7267 General 1/4/2021  

Working on a number of different projects. Working with John on parts and sub inventory. Helping Steve with a database update and merging in some new code. Towards the end, Steve and I were talking about monies and payments and how we want to structure things in 2021. Internal planning.

Small analogy, a geode (small plain looking rock with crystals inside). Sometimes I feel like adilas is like a geode, the outside doesn't look that exciting, but the inside has all kinds of fun treasures to explore. Kinda fun.

 
No po photos available. Click to view time details.
Shop 7147 Projects 12/29/2020  

Met up with Steve to go over a few things. He had some questions about doing data imports and how to best help that process. We passed some older files back and forth for vendors, customers, and items. We also got into talking about being able to use CSV files to do uploads vs pushing new records into a temp database and then migrating from the temp database to the live database. We've done tons of both. I sent Steve a number of older sample files for each process.

After that, we got into a further discussion talking about a thing we are calling mini units. This is serialized units underneath of sub inventory. See attached for where we are with some Microsoft Excel mock-ups on database tables and what not. Still playing around and trying to find out where things go and how things work. We enjoy this kind of thing.

 
No po photos available. Click to view time details.
Shop 7240 Work with Steve 12/24/2020  

Serialized inventory and playing with ideas on mini units. Steve, Sean, John, and I were doing some brainstorming. We were drawing, talking, and playing with simple scenarios in Microsoft Excel. See attached for our Excel sheet (small mock up and playing). Parent inventory, sub inventory, and then clear down to what we are calling mini units (serialized subs).

 
Click to view time photos.
Adi 1897 Multi Vendor Cross Corp Invoice to PO - Round 2 11/27/2020  

This project is for round 2 of the Multi Vendor Cross Corp Invoice to PO project. The original project was tracked under the element of time # 1433. This project has gone through multiple phases. Will Hudson did the first round, Steve added sub inventory, and Bryan has been working on the multi-vendor stuff and other enhancements. See attached for a number of new scans. The scans that are attached are from some brainstorming that Brandon was working on but never got around to finishing. Just trying to record the story as it unfolds.

 
No po photos available. Click to view time details.
Shop 7097 id 1824 & 1825 with Danny 11/13/2020  

Danny joined the meeting and Cory and I chatted with Danny for a bit about a custom project that would allow an invoice to link out to all of the sub inventory media/content files per invoice. We already built a bulk merge and print feature, but the current PDF's that the company is using are all password protected and super encrypted. We can't get them to merge due to the security stuff (not even Adobe Acrobat can do it). Anyways, we went over other options and ways to help the client.

After that, Danny and I spent the rest of our session working on new validation and age prompt stuff for his new ecommerce and age verification settings. We are getting closer, working on the code, and also making some decisions on what pieces will be part of this project vs a potential future project. Sometime limiting the scope, per project, is key. Otherwise you launch into the never-ending mist of darkness (no known ending to the project).

 
No po photos available. Click to view time details.
Shop 7031 Adilas Time 11/2/2020  

We got a text from Steve that he was helping around their cabin this morning. He was unable to join us. Just Sean and I were on the meeting. We touched base and chatted about being able to sell subs (rules and regulations) and  being able to sell parent items without having inventory in stock. Basically, sell a parent item (placeholder) and then fill in more information and actual sub inventory later on. We talked a few options and needs. Each industry is so different. Sean then bailed out to work on his own stuff. I started to go back through tons of emails from the weekend.

I fixed a couple of invoices for Trinity Fasteners and let them know via email. There were just categorized incorrectly, not a big deal. 

 
No po photos available. Click to view time details.
Shop 6991 eXPO: E/R api 10/26/2020  

Bryan and I got together and did a work session on a couple different projects. One of them was a recap on some menu boards, changing up the JSON storage, and making things smoother. We also spent some time and worked on complicated loops and sub loops on a sub inventory report that he was working on. Good work session.

 
No po photos available. Click to view time details.
Shop 6902 Projects 10/21/2020  

Emails and recording notes.

2:00 pm to 3:00 pm - Meeting with John M to work on his project. We have not launched it and pushed it live, the development of the project is completed. This is a new corp-wide setting to help control the prefix for the auto sub barcode values within sub inventory. The project included a new database update script, add/edit forms, validation, passing the data to the database, and then using the new setting when the keyword "auto" is used on sub inventory barcodes. Pretty cool. Also, John is doing great and really catching on. Good stuff.

 
No po photos available. Click to view time details.
Shop 6979 danny id 1824/1825 10/14/2020  

Danny and I worked on his local development environment. We had to re-enable some sub inventory attributes. After that, we went over a basic outline for the new projects that he will be working on. We did some small drawings and a general overview. I think that helped get us on the same page together.

 
Showing 150 of 735
Page 1 of 5 :: Go to page ::