Adilas.biz Developer's Notebook Homepage

[reset this page] . [historical web outline - entries by month] . [adilas community funded projects] . [contact adilas.biz support - email form] . [help]

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 - 7/1/2017 to 7/31/2017 - (55)
Photos	Time Id	Color	Title/Caption	Start Date	Notes
	Shop 2834		General	7/1/2017	Working on the sales tax expansion project. I spent a lot of time cascading the source of where the cart line items come from. These are things like: simple searches, advanced searches, view detail pages, my cart favorite buttons, barcode scans, QR code scans, sub inventory, advanced add to cart, recipe/build, etc. The list goes on. We aren't tracking that data in a database yet, but we are starting to gather it up. We are also seeing more ways we can speed things up, standardize things, and make it more efficient. Good stuff. Steve and I and then Calvin and I had different phone calls and online meetings to talk about progress and potential problems and/or issues. Calvin has his stuff going on but we are seeing a bottle neck in one of the processes. He is looking more into that part of the puzzle. I am combing the data, building pages, and doing the updates and cascading the new code around for the project. Steve has been helping with sales, tech support, training, and helping out if and when I have questions. Here are some fun notes from one of the meetings that Steve and I had today. - Start grabbing and storing some of our own data. We have tons of users who use our product on a daily basis. We could really catch and get some great data from our users and how they use the system. This could be things like the item to cart source stuff or other usage habits. Think about stats and data warehousing. Just an idea. On a different note, think of how useful some of that data would be back to our users and/or to their managers or business owners. It could help us improve our own product and/or help a business focus on key components and/or key processes. - Along those same lines, Steve was showing me a Google spreadsheet or Google doc where multiple users were working on the same document in real-time. You could see where they were working and it was kinda fun to watch what they were doing. I mentioned that it might be both fun and scary if you could see what was happening with your full adilas account (world building level) through a visual display of some kind. Steve would love that. He has dreamed of stuff like that for years. Almost a game-like interface where you could see invoices going out, products being purchased, things being sold, checks being made, deposits being made, and employees doing different tasks. Think of the whole world building type concept. It could be both super cool and kinda scary... :) Fun concept and idea. - As we were talking about things, we kept going back to how our current model works. We would love to have enough monies to help and keep our dependables going and being happy. The secret is where the money comes from... is it adilas monies or is is custom or adilas market monies. Some of our guys may have to mix and blend to get what they need. The market is very fertile ground where different parties buy and sell their products and services. That is pretty cool. Think of it as where do you get fed? - One last idea was dealing with the sales tax calculations and how and when they happen. We have a unique problem where some items need a special excise tax. That tax needs to be calculated and collected based off of the original list price vs. off of the ending or final saleprice. The final sale price includes discounts, price changes, specials, etc. Kinda random. Anyways, we will end up adding a new field to the store/location table where all of the tax settings are stored. We will end up adding 13 more setting so that each tax setting (state, county, city, and other 1-10) can use this new setting and/or tax calculation rule.

	Shop 2840		General	7/1/2017	Spent some time recording notes from the rest of the day. We are working hard and learning tons and tons every day. That is fun. Getting ready to jump back into the sales tax expansion project.

	Shop 2847		Adilas Time	7/3/2017	On the morning GoToMeeting with Steve. Over the weekend, we had a couple of ideas about harnessing the work and actions of the adilas users. There is an small army of users that use it every day. One of our problems is how long it takes us to get new code and new changes put in place. What if they, our users, could help us? Wouldn't that be super awesome. They are in there working anyways, what if every time they go to the water hole, they take a load of laundry either to or from the washing area... (virtual analogy - we really aren't washing clothes or anything). - Harness the users clicks - help them build out the system and/or help to do the data migration stuff. Think of the thousands of clicks that each user does each day. What if we could harness that? All kinds of different options and scenarios. - We could set up a task to be done and then everybody could work on the same task. It doesn't matter who's data it is, they are system updates that a developer would be clicking through. No data would be leaked, it is just helping to take a load off of the developers. That would be awesome. - It could be pretty cool if we could turn tasks on/off with the click of a button. We want it to be very light lifting, so that we don't hurt or tax any body too much. These are just some numbers, but we have a current migration project that has millions and millions of records. We are estimating around 40,000 clicks for the developers. We can process about 3,000 records in about 8 seconds. If you take 8 seconds times 40,000 clicks. It would be 320,000 seconds of total time. That is over 88 hours of constant clicking at 8 seconds per click. We could take that down to 50 or 100 at a time and have it only take a half a second or a full second and we could get the job done pretty quick. That would be pretty awesome. - We don't have everything all worked out yet, but it could be a really cool feature. It is almost like having a dam and then running a hydro electric operation using the already naturally flowing stream or river waters. - no more batches... do real-time updates and processes - brick walls bring the challenges and then you have to have ideas to figure things out. That is huge and part of the learning process. - burning platforms and coming up with solutions - sometimes you have to be forced down a channel and then you have to figure out what to do. - everybody bring a brick... we are going to be building a pyramid... - we could use the user clicks to migrate data, get people off the bus, and prep and setup the watchers and feeders and/or run the daily processes for the days prior. All kinds of stuff. - Proactive approach vs. putting out fires all the time - make it part of the plan - Different topic... what about using custom tags to build form pages. We could tie this in with the custom database fields and settings. This is for things like show/hide, rename, set max and mins, custom verbage, defaults, etc. Instead of using CFScript (what Calvin did originally), we could use custom tags and then have the database pull the data based on a sort and then populate the HTML or web pages using the custom tags. Program the logic once and then use over and over again. This relates to the db_field _settings table in the database. Currently, we only have one page that uses it and it is for add/edit customer field settings. What if we expanded that and turned it into a global option or feature. You could virtually reconfigure your entire site and database if you could get everything dynamic and cascaded throughout the whole system. That would be super cool. Most of the day was spent as a work session. Steve and I met earlier this morning and then switched gears and just worked on projects. I was working on cascading the tax calculation rules (new database setting for calc taxes before or after discounts). I then switched over to working on the in-line dollars off discounts. Calvin called a couple of times and we worked through some ideas and options. Good session.

	Shop 2815		Virtual Post-It Note	7/3/2017	We promised to get to the new Text 130U in the first week of July. Just a reminder.

	Shop 2850		Campaign Rise	7/3/2017	On a GoToMeeting session with Bryan. We went over how sub inventory is used in labels and how the existing code for the ~777 (where the package number if 777) works as a barcode or QR code. We also went over the logic and how the QR codes work with sub inventory, prices, and quantities. Good little session. We then talked briefly about some Campaign Rise reports and questions.

	Shop 2821		Russell time	7/3/2017	On a Zoom session with Russell. We looked at some code and merged it in and pushed it to all servers. It was dealing with a mobile app icon for tables, iPads, and smart phones. We pushed the code and Russell ran a number of quick tests. Also, by way of a note, I was on the phone with Calvin a couple of time today going over projects and options.

	Shop 2711		General	7/3/2017	Emails and other stuff. Waiting for a meeting but no one showed up. Called it a day.

	Shop 2818		4th of July	7/4/2017

	Shop 2848		Working with Shannon and Shawn	7/4/2017	On a GoToMeeting session with Shannon and Shawn. I worked with Shannon on a couple of tech support questions first. We ended up going out to the data 3 box and looking under the covers and into the raw database to figure things out. Shannon had a couple of questions so we bounced between the different subjects and had her take some screen shots and some notes. After that, Shawn and I looked at his progress to add some new payroll functionality to allow multiple other calculations based off of percentages vs. off of straight dollar amounts. Shawn has been tweaking things around and it is getting closer and closer. Looking good, it just needs a final sign-off and maybe some like detail work. In general, it was looking great.

	Shop 2849		Working on an expense/reciept data import project	7/4/2017	Working on a digital upload for a client. The topic of the upload was expense/receipts. This was the first digital upload of this type. Lots of time building the new page and flow. Once we ran the code, it went pretty quick. Uploaded over 700+ expense/receipts for a client on the data 7 server.

	Shop 2817		Brandon will be out of the office	7/5/2017	I will be out of the office for this week.

	Shop 2712		Alan Time	7/5/2017

	Shop 2713		Alan Time	7/10/2017

	Shop 2823		Russell time	7/11/2017

	Shop 2853		Adilas Time	7/12/2017	On the morning GoToMeeting session. Wayne Andersen was on and we talked briefly about a time for him to do a demo for Steve and I to show us some frameworks and how some of that could play in as we roll forward. The rest of the session was used to do emails, light tech support, record some bills, and make a small tweak on how the customer queue sorts its records based on sub queue filters or a request to see all records. Minor things.

	Shop 2851		Campaign Rise	7/12/2017	Out of the office for a cub scout day camp. Canceled the meeting.

	Shop 2822		Russell time	7/12/2017	Out of the office for a cub scout day camp. Canceled the meeting.

	Shop 2714		Alan Time	7/12/2017	Out of the office for a cub scout day camp. Canceled the meeting.

	Shop 2854		Adilas Time	7/13/2017	On the morning GoToMeeting session with Steve. We did some catch-up and then started getting back into the sales tax expansion project. I spent time reviewing notes and getting back into the code changes. Steve was working on other projects. Part way through, Eric popped in to check on progress and to see when we could get back on to customer loyalty points, gift cards, and the other special tracking accounts. He is getting more and more requests for that.

	Shop 2852		Campaign Rise	7/13/2017	On a GoToMeeting session with Bryan. We looked into some projects that he is doing and I pointed him to some code that was already done and similar in scope to what he needed. We then tried to do some debugging on his local site for some API socket connections. We couldn't find it. He will have to look into it deeper later on.

	Shop 2824		Russell time	7/13/2017	On a Zoom session with Russell. We did some catch-up and then worked on the database planning for parent attributes and attribute groups. Russell recorded some of it. We also talked about some other future ideas and projects that are on the tick list. Good stuff.

	Shop 2871		General	7/13/2017	Emails, paying bills, and general stuff.

	Shop 2870		Working with Wayne	7/14/2017	On a GoToMeeting session with Wayne Andersen (chiming in from Portugal). Steve and I were on the meeting. - CF Wheels framework - Model view controller strategy - A model is specific business groupings (say our 12 main players). - The view is how the pieces show up and/or be displayed. - The controller part is the logic and/or rules for each section. - Object oriented programming - Inheritance - Beefing up the actual methods and frameworks to have all of the custom validation on the methods themselves. - Using the database to help populate and drive the page layout, display, logic, validation, etc. As you change the database, the page automatically flexes and rolls out the new fields and values. This could even help us run the custom logic and pieces. - Think one-to-many on code, logic, functions, display items, etc. - Getters and setters - playing with smaller pieces. - Using a related folder structure vs. page names. For example: a users folder, customer folder, invoice folder, etc. Currently, the page names hold the underlying things such as add_edit_customer or invoice_home or view_cart. - We are getting more mature and are seeing more of what is going on. We could really plan and lay things out better and better. This is the nature of the beast. - Noodle code, sprawl, and custom add-on's - currently, we have code all over the place and have tons of different developers working on different pieces. We need to reorganize and plan things out more fully. We then, at some time and/or while we are running, will need to do a full re-write and then make that transition into a more robust framework. - The more we go into an object oriented framework, the easier it will be to help train and bring on new developers. That is huge... Right now, we spend months and months trying to bring on new developers and trying to help them find their way around. Imagine if we could bring them in, get them oriented, and then help them get in easier and do their job. - We will still need to allow for custom code, custom display, and custom logic, but we could really benefit from a standard framework. One of our goals is to become a full on platform that others could build off of, duplicate, extend, re-use, re-purpose, and/or consume as needed. - We want to provide our users with their data... that could be web, html, csv, excel, xml, json, pdf, etc. We have tons of critical data that our people need. It would be so cool if we could provide any data or data tables or tabular data in all kinds of ways at the click of the button. As far as the data goes, it is their data, we just need to allow them to get it and provide it in as many ways as possible. - The look and feel is huge... many of the sales start right there. Some people don't even look past the cover to see what we have under the covers. We need to change the appearance of what people are seeing. In some ways, we have been lightly hiding. We may need to come more out in the open. We need to keep the logic and view on separate layers. Right now, we have a number of files that are intertwined together. We need to somewhat break things apart and allow the logic and data to be on a separate level than the display. - If we use a framework, we are using some existing pieces that already exist and then we get to leverage those functions how we want. We could really harness that and it would save us tons of time. - The API layer (application programming interface) is huge. This is the path to the data. If you make it so that you use the API for all of your calls, it makes it really strong. Currently, we use the same methods but internally we use native ColdFusion. Externally, we format things into XML and JSON and run our methods through other pieces. If we used the same thing for both... It would be very stable and a well beaten path because we are using it all the time. Currently, it is lightly coupled but it is separate. It would be really nice if we could tie things together. - We want our more senior developers to work on this project. This is not for our beginner and/or junior developers. We need to make it stable, good, easy, etc. Totally possible. - Steve would love things to go toward the gaming level. Full on interfaces, levels, characters, worlds, etc. Virtual environments, custom interfaces, and showing real-time data tracking. Take real processes and then simulate them in some kind of a system. Similar to the idea of harnessing our users clicks and navigation patterns. What if they could help us do the things we need to... Take real actions and turn it into science and/or data management, internal processes, warehousing, etc. Great meeting and some really fun progress. Good stuff.

	Shop 2872		General	7/14/2017	Working on some to do list items. Did some prep on the developer's homepage to help look-up expense types and banks for corporations. This is used by the developers to help them get the underlying auto id numbers for the different pieces. That page already existed, we just added a couple more pre-set look-ups.

	Shop 2873		General	7/15/2017	Working on some small tweaks. Paid some bills, ran some reports for payroll commissions, and made a couple small code tweaks to files that I was using. Uploaded new files and did some light testing. Sent off a custom data upload project to Wayne in Portugal with some details and information. Trying to clean-up my to do list.

	Shop 2855		Adilas Time	7/17/2017	On the morning GoToMeeting session with Steve and Alan. We started out and were talking about ideas for moving to the next level. We were talking about needs per page. We came up with some ideas such as: - part of a platform - built on a framework - able to export data to all levels and formats - black boxes (able to plug in custom code) - full validation - run on the API socket level - separate display and logic - separate databases - dynamic naming for all database fields - in-line database extensions - object oriented programming - built on time and running all levels through time and space (data assembly line) - 3D world building Steve had a question... Do we keep evolving what we have and keep patching and fixing or do we do a full rewrite and fully restructure things? This is not a new question, but it keeps coming up. Do we build on what we have or do we rewrite and virtually start over? We have so many options, it is somewhat overwhelming to new comers. That tends to require lots of training and setup. One of our main pieces is how customizable we can be. That is a big selling point for our system. One of the challenges is that we use tons of other outside libraries for code, what happens if those libraries go down or are no longer supported? We need both the electric elevators and the manual doors with staircases... We have to have options to do both manual and automated functions. That is really important. Our main focus used to be just functionality... it seems to be changing gears and is getting more end user oriented. We have to maintain a balance between functionality and user interface. That is always a challenge. We keep seeing things "fracture" right and left. The deeper we go, the more things break into subs and subs of subs. As a funny note, on 6/22/17 Steve proposed a new company name (just for fun). He was calling it "Fracture". Kinda funny. Alan and Steve were talking about new trends such as predictive typing, JQuery, Ajax, JavaScript, API socket stuff, object oriented programming, etc. We have to mix and blend tons of different ideas. Kinda like a painter having a pallet of tools, colors, and ideas. We are very good at slowly cascading features across the site. Maybe we just keep doing that... The main draw back is the time it takes to do that... Steve would really like to keep the adilas team as a small tight strategic group vs. a huge multi level corporation. Once again, it will be a balancing act. Keep the vision going! We will just keep working on it every day. Instead of jumping to a full rewrite... what if we do a full "continue rewrite". Adilas is a giant idea farm. We just need to keep going and harvesting those ideas. As a side note, we don't really fit into some of the standard software models. Our model has been a continual rewrite process vs. a staged or version based release. Our product has been the same price with all of the new functionality - almost free upgrades. We release new features almost weekly or monthly. A more traditional method might be a full rewrite per year or every other year. We are releasing on a weekly or monthly rate. There are days that we push multiple different releases in a single day. Pretty crazy. We are seeing that the new changes we want to implement have both a code aspect and a personnel aspect. There may need to be some changes on the teams and how the people are organized. Here are some other things that we are seeing... - We need to get all of the code into one repository (master). Currently, we only have some of the pieces. If we wanted to make a global change... we would miss some of the custom stuff. We need to pull it all together. - We need to go over the CFC's and pull related pieces into similar files. Currently, the methods and functions are organized but all together in a general clump. We would love to have folders for all main pieces such as customers, invoices, quotes, PO's, etc. We then want to pull all of the CFC's into specific pieces that have like and/or related pieces. We could also just make a special page that shows the mapping of where those pieces are. If it is organized, you could get there really easy. It doesn't have to be in the exact same sport. Maybe think of mapping and/or documentation of where things are at vs. physically moving things around (this idea came later on in the discussion). - We might need to restructure how the files and folders are organized. See element of time # 2870 for more details. - At some point, we may need to form our independent developers into lightly structured teams, leads, and managers of sorts. - As a side note, we could start changing the structure without changing every aspect. Currently all core code is under the top_secret folder. We could use that as a research library. What if we created a new folder and started to organize things better? We could still use the same database, just start changing the structure from the inside out. This could play into the concept of the continual rewrite idea but could really help with the structure of the whole. We have a ton of key players... all doing different things... all have different ideas... but we never really get together. Maybe a monthly meeting would be good with an agenda and letting all of the key players know what is going on. That could really help. Keep experimenting on the side. There may not be a silver bullet or specific answer... just keep working on it every day. As we kept talking about it... we jumped out to the photo gallery that Russell helped us make from the developers notebook. We are actually trying to do a form of object oriented programming and it is developing as we go. See attached for a quick screen shot. Keep your options open... You may not want to force everything into the same space. Don't wreck your toolbox by forcing it. We may gain a ton of advantage by using tons of different tools vs. forcing it into a perfectly standard model. We might benefit by the hybrid type model. We are seeing the clients' role being a huge part of the puzzle. They are basically saying that they want their own custom unified system that works and flows as they want and see. Our users are getting drunk on technology. They want more control. This could be settings, permissions, controls, rules, views, displays, logic, flow, etc. We are seeing small projects that are being built out... as we get more pieces, our clients and/or our developers are seeing new places to build bridges between the different pieces. Adilas is becoming a cluster of bridges. Maybe we keep allowing that. Our answer may be what Shannon said way back... "How we run adilas may need to be as flexible as adilas itself." We run a hybrid model. What if we strip out the best pieces of object oriented programming or other pieces that we want. We basically harvest whatever pieces we need. We just organize things and then create a virtual mapping. It doesn't really matter where things are as long as we come together to get things done. Think of our developers - I'm in Utah, Steve is in Colorado, and Alan was in California. We all came together to have our meeting. We need a platform or interface that pulls from all of the different pieces. We mix and blend things together to get the final output or desired outcome. Kinda like our analogy of funnels and tool boxes. You set up a funnel of what is coming in (data, logic, needs, etc.). You then use the tools to get what you need out of the system. You can repeat this over and over again and/or even use reverse logic as needed. See the photo gallery for ideas on funnels and toolboxes. Mix and blend as needed. Basically, setup the possible options and then let the users mix and blend as needed. Don't draw all of the lines (possible solutions)... leave it open and let them mix and blend as needed. If our clients want a more specific or structured flow process, we send that over to custom code. We are harnessing our ideas and concepts little by little. No more batches... even on rolling out new features and implementing some our ideas... no more batching... apply bits and pieces as we go. That is the model. We can't have tomorrow without the yesterdays. See attached for a couple of screen shots.

	Shop 2860		Lunch	7/17/2017

	Shop 2715		Adilas Time	7/17/2017	Back on again with Steve. We talked about harnessing some of our own notes and ideas. We talked about how we are technically doing that every day, little by little. We also talked about how our experiences yesterday (as a concept) help us make decisions today and allow us to build for tomorrow. I re-read the notes from this morning and made a couple of tweaks and changes. We have a huge resource of all of the notes and ideas we have captured over the years. That is huge... We then rolled into a work session on the sales tax expansion project. I went back in and started working more on the in-line dollars off discounts on the advanced add to cart page. That is a big project and it takes a little bit just to get into it.

	Shop 2865		Adilas Time	7/17/2017	On a GoToMeeting session with Bryan, Alan, and Dave Forbis. They were going over the Campaign Rise project. They are using elements of time to hold custom page verbage, contact us info, and even video links and such. They are also using elements of time for virtual inboxes, campaigns, events, and all kinds of stuff. They are kinda using elements of time and media/content as placeholders for all kinds of stuff including the custom verbage for special web pages. This allows them to change the elements of time and that in turn affects the main web site. Basically, a small workaround for a CMS (content management system) type system. They (the developers and the Campaign Rise folks) are going to need some custom email accounts and options. I will be helping with that. They also need to setup the merchant processing to allow monies to flow through. As a side note, they would eventually like to go towards the "Bitcoin" or "Bit Coin" stuff. This is a digital monetary value kinda like a computer credit of sorts. They are also still working and building out the impact reports. These reports pull from all of the different data points and assign a value to it. This could be followers, sign-ups, events, subscribers, monies raised, etc. The guys were giving Dave a report on certain features, updates, and changes that were being made. Dave said that the clients seems to be pretty happy with the progress. There are still some small clean-up things but things are going good. They are shooting for round 1 being done by the end of the week. One of the to do list tasks deals with showing Steve and I what they have created and helping them (Campaign Rise) with some free advertising as Steve starts showing what is possible to other adilas clients and other potential clients. After that meeting, I started to answer emails, light tech support, and other small tasks. I ended the day checking into an error on the data 6 server not being able to do outbound pings to the data 0 box. Started a ticket with tech support.

	Shop 2856		Adilas Time	7/18/2017	On the morning GoToMeeting session. Wayne checked in and showed us his progress on the QuickBooks checks data import. He is pretty good at that stuff. Fun to see what he is doing and how he is doing it. After that, Steve and I looked at our outstanding projects that are in the works and just made some comments on the state and status of those projects. We then jumped into a work session for the sales tax expansion project. More work on in-line dollars off discounts.

	Shop 2861		Lunch	7/18/2017

	Shop 2874		Campaign Rise	7/18/2017	On a GoToMeeting session with Bryan. He wanted some help with a custom report and wanted to know how transfer invoices played into the mix. The problem was dealing with how tight his queries were... The queries were only pulling PO oriented data and thus couldn't even show the transfers because they are on the invoice side.

	Shop 2825		Russell time	7/18/2017	On a Zoom meeting with Russell. He had a bunch of custom ecommerce changes that needed to be pushed. We had to do some custom merging to get it how we wanted it. That pretty much took up the full session. We pushed things up and then he had to make a few little tweaks and such.

	Shop 2867		Adilas Time	7/18/2017	No action was taken.

	Shop 2857		Adilas Time	7/19/2017	Spent the morning reconfiguring the main Application.cfm pages. They used to be domain specific and all of the configuration stuff was hardcoded per page. The pages now pull data directly from the database. This will help with all future updates and changes. The Application.cfm pages used to contain a potential hole and/or weakness. This update should help them flow and transfer better between servers. Also as a note, depending on the configuration, the new pages allow for all kind of white labeling and custom domain names to run the site. That will be cool when we actually need it. Kind of a maintenance day of sorts.

	Shop 2862		Lunch	7/19/2017

	Shop 2716		General	7/19/2017	Started out and did some emails and tech support. One of the emails had a great list of feature request from a client. I have attached them here. Some of them were things like: limiting discounts, daily price changes reports, see all IP addresses for logins, restrict or limit login by IP addresses, new advanced invoice export columns and values, coupons and special discount rules, tracking and auditing employee purchases, transfer quotes, rewards and rules for dealing with rewards, an export request for the customer queue, easier web/ecommerce management of items and categories, additional values on the daily/weekly sales reports, and other requests. Anyways, I spent a good 45 minutes responding to their email. I though that it would be good to get the info recorded here as well. In a nut shell, clients want to configure the system, have it play by their rules, and then be able to get the data back out through reports, searches, and data exports. That kinda sums it up in a way. Most of our clients want similar type features. Good stuff.

	Shop 2866		Adilas Time	7/19/2017	Spent most of the afternoon going over javascript to help calculate new in-line dollars off discounts with all of the new crazy sales tax rules and settings. It gets pretty deep. I also did some emails and light tech support stuff.

	Shop 2858		Adilas Time	7/20/2017	On the morning GoToMeeting session. Wayne Andersen checked in a number of different times. He was showing me some code for his first data import of QuickBook checks and expenses for a client. There were over 1,300+ expenses, and some with multiple line items. We had to tweak some code just a little bit here and there and then ran things live. It looked good. In the meantime, I was working on the advanced add to cart javascript to help with in-line dollars off discounts and new tax settings.

	Shop 2863		Lunch	7/20/2017

	Shop 2884		Working with Steve	7/20/2017	On a GoToMeeting session with Steve. He was briefing me on a meeting he had with the bank. We were making some plans. After that, he needed a little bit of help with his wire job for the campground reservation stuff.

	Shop 2826		Russell time	7/20/2017	On a Zoom session with Russell. We pushed up some code and then fixed a number of small ecommerce errors and bugs. After that, I got him setup with where to go to see some code that did an export to Microsoft Excel. He is wanting to provide an export feature for the customer queue.

	Shop 2868		Adilas Time	7/20/2017	Nothing happened here. The time was used up on other appointments.

	Shop 2875		Campaign Rise	7/20/2017	On a GoToMeeting session with Bryan. We worked on some code that he had for sending emails. We then spent some time going over a big custom report that he is building. It keeps timing out, so we are trying to trim off un-needed pieces and such. The report is dealing with tons of PO/invoice line item transactions and he is having to run tons of logic on large blocks of code at a time. Kinda funky. Hopefully, we'll get it all figured out.

	Shop 2859		Adilas Time	7/21/2017	On the morning GoToMeeting session with Steve. We ended up looking into a possible hole with sub inventory. We made some changes and the pushed up some files. The last part of the session was updating tons of black box files on the PO line items section. That is where we closed the sub inventory hole. I went through each server and all of the live black box files for PO line items and got everything all updated. As a side note, while we were doing this, Steve and I were chatting about all kinds of stuff. While we were talking, we were reviewing tons of different topics. Here is a small little piece from our conversation, dealing with QuickBooks. Instead of building a huge export to QuickBooks... what if we went the opposite way and made a great import tool from QuickBooks to adilas. Help our users get all of their data in one place. Anyways, I liked that idea and thought that I would record it.

	Shop 2864		Lunch	7/21/2017

	Shop 2869		Adilas Time	7/21/2017	Recording notes and other general to do list stuff. Paying bills and doing emails.

	Shop 2819		Brandon will be out of the office	7/24/2017	I will be out of the office this week.

	Shop 2717		Alan Time	7/24/2017

	Shop 2891		Adilas Time	7/31/2017	On the morning GoToMeeting session with Steve. We started out doing some catch-up and talking about developments that happened over the last week or so. Steve and I got into a discussion about the direction with Russell, the shop, and AFB. Russell is looking into basically running the shop and incorporating the hub type model in some ways. Instead of doing a full merge between the two companies, we would keep it connected but still be independent companies. Kinda like a division or department. This would involve Russell and the other guys and they would provide the and manage the bigger custom projects. After that, I spent an hour or more doing emails and tech support. At the end of the session, I was tracking down a bug with showing multiple user login histories. It looks like the error is coming from the choose corp page. The system is logging in the user and recording the history and then doing it again if they switch corps. It makes it look like a duplicate entry with a slight time delay (couple of seconds). Anyways, we'll get it fixed.

	Shop 2895		Lunch	7/31/2017

	Shop 2890		SWC: Mike and Anna sub-inventory	7/31/2017	On a Zoom session with Bryan, Mike, and Anna. Bryan setup the meeting and we were talking with the client about moving to sub inventory and other cool features that were coming down the pipeline. These are some notes from our conversation - mostly them talking and telling us their needs. - They have a very item centric system and inventory (tons of parent items) - Having all of these items creates its own problems - They do a lot of internal builds - They are currently not using sub inventory - They would like to know about mini conversions - The difference between tags and parent inventory attributes - They do tons of internal mini manufacturing - breaking down items into subs and mini conversions - They need the outbound data for reporting - currently using excel to do tricks and such - pivot tables and creating a fake train and/or data trail - They have a need for sub part/item categories - They are on the production side of things - As a general idea, we (adilas) need to create a social hub or blog type place where all of the ideas and projects are publically available (developer's notebook - being live, searchable, and updated). Anyways, we tried to listen and got them some good contact info. We also pitched them about using the piggy-back type model for development. They seemed very nice and I enjoyed the conversation, ideas, and questions. Good stuff.

	Shop 2827		Russell time	7/31/2017	Zoom session with Russell. Talking about the Adilas Shop and the hub model for different services. Russell wants to do all of the custom code projects and run them through the shop environment. That will be awesome. We then looked over some code and did some code sign-off. At the end of the session, we looked over his parent attribute project and got him going back on that project.

	Shop 2902		SWC excel export	7/31/2017	On a GoToMeeting session with Bryan. We spent the whole time looking into an expanded parts and item search for a client. The search and report does a custom export to excel. The crazy thing is that the report finds an item and then does a backwards look-up to see the existing quantity and then to make a guess or assumption on where that quantity came from (inbound PO's or from transfer invoices). Pretty crazy logic and reverse look-ups. We were mapping things out and then getting into the code to make the mapping happen. We ended up doing some drawings, samples, scenarios, and then even creating a text document that had some mappings and instructions on it. We are hoping to get things nailed down and standardized. Pretty deep stuff.

	Shop 2889		Will Time - Talk about Auto search textbox	7/31/2017	Code review/comments/suggestions - We didn't meet. This didn't happen today.

What's New

Products

Find Us