Texting some of my contacts to meet for lunch or whatever. Light networking with friends and acquaintances.

Working on the daily sales and profit reports. We had a client who wanted to see all invoice payments per day, even if they didn't sell anything that day but just got some payments from invoices that were on account. We have a number or reports that already show that data. The client wanted that data to show up on a special report. The existing report only showed data based on the main invoices that happened for a specific date range. It's ok for main invoices, invoice line items, and invoice payment to have different dates. That's how we track accounts receivable (A/R's).

So, we went in and opened it up a bit more. Also added in some notes on the error messages to show any other details that were needed to help the users. Pushed up the new code and let Cory know.

Emails and research. Meeting with John. Quick update on servers. It sounds like Wayne and John are working on a small mini project for the adilas cafe model. After that, John and I spent time working on the SWOT analysis. We were going over our strengths and weaknesses and making notes on each entry. We pretty much spent the whole time going over that. The current authoring file is on the Adobe Cloud. Lots of little comments, links, and researching out stats and what not.

Phone call with Cory. We had to back out some code. We fixed a known issue but created a small disconnect for a different client. Both clients are using the same report. One client offers or extends credit to their clients (invoices on account). The other one just deals with cash and needs the report to filter on a per salesperson basis and doesn't care about any other relative data. The disconnect is the date on the invoice payments. If you extend credit, the invoice payment date may be different than the actual invoice date. If you just do cash type transactions, they always match up. Anyways, we reverted some code and pushed up the old code until we can figure out a plan moving forward. I hate doing that (reverting code) but sometimes it helps calm the tech support lines. My ideal would be just fix it and let it move forward. Sometimes, if it is under pressure, people aren't very patient and thus the quick revert.

Meeting with Aspen and going a small review of what is happening (daily). Emails, text messages, and then recording notes for today (6/13) as well as adding in a video link for the group pivot meeting on 6/6/23.