all data is live and searchable
[reset this page] .
[historical web outline - entries by month] .
[adilas community funded projects] .
[contact adilas.biz support - email form] .
[help]
|
Adilas.biz Developer's Notebook Report - 4/1/2012 to 4/30/2012 - (38)
|
||||||
|
Photos
|
Time Id | Color | Title/Caption | Start Date | Notes | |
|
AU 760 |
|
Daily Tasks | 4/2/2012 |
• Working on the barcode label changes. Needed a bigger price field (font size) for a company. • Made a new label for 2.25 x 1.25 inches. Bumped up the alternative price label size and made a couple of other small tweaks. • Posted files and did some light testing. • On the phone with our sub-contractor going over things. We talked about location specific inventory as compared to general or global inventory tracking. • New label for company. Had to add more to the height to help them in printing. |
|
|
AU 761 |
|
Daily Tasks | 4/3/2012 | • Spent the day with my wife for her Birthday. | |
|
AU 762 |
|
Daily Tasks | 4/4/2012 |
• Added some strategic focus areas for the CMC evals. • Other light verbiage changes. • Posted files online. • Changed addresses on websites and resume for two companies. • Worked on prep work for Federal tax settings and new tables. |
|
|
AU 763 |
|
Daily Tasks | 4/5/2012 |
• Prep work for new Federal tax calcs. • Some re-work on the Federal tax tables. • Spent some time online researching, checking file size before doing an upload. |
|
|
AU 764 |
|
Daily Tasks | 4/6/2012 |
• New photo upload table to help monitor actions. • Steve called and we discussed new image monitoring report. Built part of the new report. Posted the files online. • Small tweak to the monitor images page. Changed from a URL controlled vars to FORM controlled page. • Working on cascading the new photo upload history settings and options to the right action pages. • Finished up the 2012 Federal tax tables (small rework). • Did some prep work on the state tax withholding for the state of Alabama. |
|
|
AU 765 |
|
Daily Tasks | 4/7/2012 |
• Working on the advanced expense/receipt search and results page. Added options to export to Excel and refine your search. • On the phone with Steve going over ideas for adilas university. We also talked about reps and what we need to do to keep our company progressing. • Posted files online that were done. |
|
|
AU 785 |
|
Daily Ideas | 4/7/2012 |
-Convert the image monitoring page over to the real application and tie it to global admin permission. -On discounts – have a special button that converts the whole cart into a Java Script application that allows cart as a whole, individual items, or any number of items to be discounted. This could really help. Both percentages and dollars off options. We need a general discount, full cart as a whole, or selective discounts. |
|
|
AU 766 |
|
Daily Tasks | 4/9/2012 |
• Research and sending out emails to folks dealing with “lean” accounting and a thing called the “Shingo prize” based out of USU. Kind of fun, kind of brave. • On the phone with a customer going over smart group buttons and a potential problem with their patient migration. • Small change to the customer queue. Added the customer type to the output. • Custom work for company. Flipped a number of customer types to help them get going in the right direction. • On the phone doing tech support for different clients. • Working on new filtered sort options for the printable parts list report. • Posted files online. |
|
|
AU 767 |
|
Daily Tasks | 4/10/2012 |
• Rep checks. • Quick fix on the customer quick search option. Added the options to quickly search for a phone number, a cell phone, a work phone, or an email address. • On the phone with Steve going over new changes and directions for the next couple of days. • Tech support and emails. |
|
|
AU 768 |
|
Daily Tasks | 4/11/2012 |
• Bank and rep checks. • Flex grid tie-ons. • Worked on Alabama state tax calcs. |
|
|
AU 769 |
|
Daily Tasks | 4/12/2012 |
• Writing an email about options for tweaking the adilas check in/out processes. Quoted him $1,000 and a date around June(ish). • Writing emails about showing the relationships between payees and departments. Basically, we need to show what is going on to take the guess work out of things. • Brainstorming and making phone calls to USU. Called a guy that works with the “Shingo Prize” and also left a message with a lead or head professor in lean accounting. • Brainstorming on making adilas a full-on business platform and library of sorts. (see red notebook or below for notes) • Worked on the Alabama state tax calcs. |
|
|
AU 786 |
|
Daily Ideas | 4/12/2012 |
-We had a request to store payroll settings per employee. Maybe what we need to do is show what relationships exist so that they may be manually updated. Currently each employee may be assigned to one or more departments. Instead of changing that – maybe just show the relationships and settings. Also maybe a multi-update feature for pay rates, or allow them to be updated from the setup employee page. Spread the love. -Brainstorming notes on making adilas a full-on business platform. Open the door to the data and how it plays, gets connected, is shown and is used over and over again. -I love the word “upstream” – what is the source? What feeds what? How does that affect things? Where is it easiest to control? -We keep getting great ideas but I and/or our existing pieces become the bottleneck. What if we re-built with platform in mind? -Small idea (different company arms). Diagram in notebook: Main adilas (in center box) connected to: hardware, library, marketing, personnel, web services, business(sm, md, lg, xl), stand-alone apps, web, mobile or mini, non-profit, custom look-feel (skins), software, education, eCommerce, commercial, shareware/freeware, government, trainings and setup, info/resources... Don’t get stuck here, think unlimited entry and exit points. -The goal is to create, define, provide, build, re-use, and create a culture that embraces change, thoughts, ideas, concepts and flow. -Allow people to create their own uses of the system. This means provide a core pre-built structure. However, if people only need 3 out of 20 options, let them put it together in a custom wrapper to meet their needs. -Think about a global library of functions, logic, data and mappings. -Create a buffet or smorgasbord of options. They (persons – our company – other company – teams – individuals) could pick and choose. -Allow different pieces (already defined or new pieces) to play in any 1-to-1 or 1-many(one-to-many) relationship. For example: we have vendors, elements of time and expense/receipts. However, they are not currently tied together. If I had a shipping and packing company it might be nice to know who (vendor) is coming in today, what do they need (invoice), and what are they bringing (PO’s and expense/receipts). Imagine being able to virtually morph or create dynamic relationships between the different players through a standard “re-skin-able” interface. -All the players already exist (or may be created) and then you put them in to play by defining rules, parameters, scopes and functions. You get to name them, use them, whatever. -Our current system is already built with data components (ColdFusion CFC’s) and logic pages (searches and reports). What if we allowed others (or our own little sister company) to get at any of those pieces. Once access is granted, the sky is the limit on what pieces could play or piggy back on one another. Get as many or as few as are needed. -I see it as the main “adilas” is the pre-built or canned version. We keep adding permissions and settings but keep a basic and consistent flow. If a new wrapper is needed (custom look, feel, function, relationship, process, steps, etc.), allow that to happen without causing problems upstream and/or downstream (cause and effect relationships). -This may not fit here but what if all data was returned as a standard like xml or Java (or whatever else new comes out) and then consumed by whatever type of application that calls it. The end goal is call, crunch, serve, apply, do it again. -On a different note – what if every function or method call had a user id, corp id, app id. Every function could also pass its data to a converter function. The converter function would get, check, interpret and then send the results back. The original method call would return the native format by default. However, if a different format was needed, it could translate the output to that format. -The incoming values would also need to be standardized – so that flow back and forth would be possible. -A full re-write from the ground up may be required. That would be a couple steps backward to make huge and giant leaps forward. It wouldn’t be the first time. (Meaning a full re-write) -Security, mobility and built with growth in mind are huge keys. -Currently built in Adobe ColdFusion and MySQL databases. It could literally be built in ColdFusion, Java, PHP, ASP, net, Ruby, Visual Basic, Access, Flash, ActionScript, Java Script, you name it. I think the more the merrier… Oracle, Microsoft, Apple, Unix, Web-based, App-based, software, firmware, hardware, freeware, shareware, etc. -Expose the code, the logic, the theory, the formats and the experience to the world. -As long as things are being expanded, what about languages? Computers? Operating systems? Countries? Etc…. -There is enough to go around (info, resources, ideas, etc.)! Share with the people. On a similar note, just read a cool scripture today during my study, it was 2 Kings 4:42-44 (pg. 513 in the Bible)... related topic. -Another quick idea – how cool would it be to over lay a calendar view on everything that happens in the system. Elements of time have groups, details, calendar and time slot view – think everything out of those four levels. -Random other note: If we were to expose this stuff to the world – we should video tape the presentation and then send that around to different colleges around the world. I’m thinking that the college level is the entry point for new and creative thinkers and future business leaders. It may branch out from there, but that is where I’d like to focus first. Post the videos on adilas university for the world to see. -Plan it out, break it up into pieces and even provide code samples. |
|
|
Adi 327 |
|
Training - Step to Success Templete Ideas | 4/13/2012 |
Headings linked to a jump to group Links or thumbnails of screen shots Links to adilas shortcuts Icons for important info etc Mouse roll overs Printable PDF buttons for sections Check boxes Tracking each user that learns so we can hold progress and award certifaces Sections that show and hide Links to try it on a play site. If we capture the student we can send them to a specific play site Links to lots of video Student interface with progress tracking Quick search of all words or word combos for help lookup Imbeded tags per section to help with help look up How do I list so a student can jump to relevant sections. Part of the index that should roll with the sections or always be available. Hover icon or ? |
|
|
AU 770 |
|
Daily Tasks | 4/13/2012 |
• Working on state tax calcs for Alabama. • Emails and tech support. |
|
|
AU 787 |
|
Daily Ideas | 4/13/2012 |
-This is somewhat related to gift cards but what about general credits for customers. They virtually are the same thing as a gift card but with a different name and must be tied to a specific customer. -Gift cards – it could be as a simple as a section that creates the card (name, number/identifier, optional customer assignment, use expiration yes/no, etc.). It would also need a sub section for adding (loading the card) and sub-tracking (using of paying with the card). These cards would need to go all the way out to the accounting side. The other key would be to be able to search, get amount available, be able to subtract from cart or invoice checkout (payment) and be able to fully close them out. Quick search, home page, look-back page. |
|
|
AU 771 |
|
Daily Tasks | 4/14/2012 |
• Added the option to search all locations from the printable parts list. • Also added a look-back date option and the ability to export to MS Excel from the printable parts list report. |
|
|
AU 772 |
|
Daily Tasks | 4/16/2012 |
• New logos for companies. • Emails and tech support. • On the phone with a customer going over PO’s and how to get things into the system. • On the phone with Steve going over a game plan. Another associate was also on the phone and I spent quite a bit of time listening to both of them talk back and forth. Our associate was interested in pushing this thing toward the education and non-profit side of the market. We, Steve and I, helped to fill in a little bit of her vision of where we want to head with things. Kind of fun to brainstorm a bit on where we want things to go. |
|
|
AU 788 |
|
Daily Ideas | 4/16/2012 |
Some ideas from the phone call: - Custom labels (not in flash) – use a mini webpage – label size – with an image – with possible custom mappings. - We may need a mini receipt with label options. - We may need a multi-print queue of sorts. Maybe what it could do is send the info to flash and automatically hit the print button. It could be done in a frame set with options on one side and commands being executed in the other window. - Another multi print queue option might be to pass lists of info to the players and have them loop and print, loop and print. (Just ideas.) - These multi print queues are for things that need specific print sizes, specs and exact placement needs. These are things like checks, labels, and multiple invoices. - We need a clean-up feature to help with updating cost of goods sold. Basically matching up PO’s and costs to invoices and costs. Catching the pieces that “get to ride” on the cost changes. (This will become part of what we call ICC’s or Internal Cost Corrections.) - We also need the ice-down date to help lock the system once we are done. (This will become part of what we call ICC’s or Internal Cost Corrections.) - We also need a couple of other “special line items” like principal, interest, gift card/certificate and maybe coupon/promotion. - Maybe change the word “black hole” to balance sheet or something like that. |
|
|
AU 2244 |
|
Notes from Steve & a Rep | 4/16/2012 |
Notes from Steve and a rep: - Custom labels (not in flash) mini web page(s) - Mini receipt – with label options - Multi prints – multi print queues o Checks o Labels o Invoices - Sweep the floor for cost of goods - Ice down date - New special items o Principal o Gift card/certificates - Change “blackhole” to balance sheet o Gift card - Normal invoice sale |
|
|
AU 773 |
|
Daily Tasks | 4/17/2012 |
• On the phone with a customer talking about their website and search engine key words. Made some small fixes and took off a banner ad and the other locations and stores. • On the phone with Steve going over priorities. We need to get the content server up and running. We also talked quite a bit about small balance sheet tweaks for gift cards, in store credits, promotions, coupons, etc. • Added a new database field for number of dependents for state tax calcs. • Made some changes to the departments. Cascaded the payroll and payee/user to department settings around. Tried to expose some of the hidden relationship between the players (payees, departments and payroll settings). |
|
|
AU 774 |
|
Daily Tasks | 4/18/2012 |
• Looking over instruction to do an email newsletter. Sent a customer a few ideas and direction about what to do. • Emails, tech support and brainstorming on the “game” of adilas. • Working on exports to MS Excel for expense/receipt payments. • Added new filters to the advanced expense/receipt payment search for vendor/payees and payee id’s. • Added a number of drill-down links for all expense/receipts to vendors and user/payee pages. • Uploaded new files and did some light testing. |
|
|
AU 789 |
|
Daily Ideas | 4/18/2012 |
-Diagrams in Red Notebook – permission levels, stages and key flags, full life cycle, core cross section. -Not bound by walls, virtually jump to any place at any time, if you ever get lost – return to the main homepage. Main homepage (click on the logo to return here), sub-homepages, sub functions and components. The quick search is a vehicle of transport to multiple parts of the system; it follows you to every page. -Learn how to play the game. Relate to the game of golf, fairways, greens, roughs, sand traps, lakes, etc. -Data sphere – orbs, levels, stations, connections, processes, functions, etc. -We need to add the key work “adv” (for advanced search) to the quick search options. -Let people heave their data how they will and when they want it. Allow for saving to PDF and exports to MS Excel for all sections. |
|
|
AU 775 |
|
Daily Tasks | 4/19/2012 |
• Testing and updating help files. • Added the keyword “Adv” (short for advanced or advanced search) to the quick search. Edited the adilas start-up history document and biography. |
|
|
AU 776 |
|
Daily Tasks | 4/20/2012 |
• Reading emails and a proposal for a California company to do full circle tracking of products and services. • Other emails and tech support. • Did some emails back and forth to Steve about help files and options. • Re-read and updated the adilas history biography. • Posted a PDF version online at adilas university.biz. • More work on Alabama state tax calcs. |
|
|
AU 777 |
|
Daily Tasks | 4/21/2012 |
• Phone calls and tech support. • Finished up the Alabama state tax calcs and posted files online. |
|
|
AU 778 |
|
Daily Tasks | 4/23/2012 |
• Reading emails. • Did some research and calling some folks about “Lean” Accounting. Left messages with gentlemen at (leanfront.com) and (book written guy). • Normal bank stuff. • Worked on small tweaks and changes. • Working on the admin clean-up tool for un-deposited invoice payments. • Added a date problem flag for time cards if main dates were different. • Added a quick search and add form to the top of the PO line items page. That is a huge time saver. • Added a drill down link to the credit card transaction code or “authorization code” from the printable invoice if the invoice is marked void. • Posted files online. |
|
|
AU 779 |
|
Daily Tasks | 4/24/2012 |
• Emails and tech support. • Added the invoice total to the create main invoice method (part of the history message). That helps in case an invoice gets voided out; at least it is a starting place. • Worked on help files. • Small verbiage change from time cared (with a space) to timecard (with no space). |
|
|
AU 790 |
|
Daily Ideas | 4/24/2012 |
-Along with the note below (for payroll) record a new payroll status and show a drill-down to the underlying data. -We have had some requests to tighten up payroll, record each unit or invoice that was physically paid for and be able to re-pull that data as needed. We’ve also had the request to be able to convert reports to PDF format. -Create a culture of change and progression. Change is good! -On cash drawers – what if we assigned them to a sub location and to a user or user group. Track things by both drawer and user. |
|
|
AU 780 |
|
Daily Tasks | 4/25/2012 |
• Emails and added a new error message to the user to department check for system time cards. • Posted files on line. • Cleaned out email inbox and recorded ideas. |
|
|
AU 791 |
|
Daily Ideas | 4/25/2012 | -Think mini projects and try storming. Just like I want to make a hybrid vehicle of sorts – but I’m willing to do it in a miniature or as a toy first. Instead of doing everything at once, break it into mini steps and specific try storming options. That makes it a lot more chewable… yum! (On post-it note pg. 137 Red Notebook) | |
|
AU 781 |
|
Daily Tasks | 4/26/2012 |
• Cleaning out email inbox and recording ideas. • Small fix for duplicate invoice payments being deposited on the same deposit. • Working on recipe and builds. • Started to activate the build and hold recipes. • Working on flow and processes. • Posted some files online and did some light testing. |
|
|
AU 782 |
|
Daily Tasks | 4/27/2012 |
• Brainstorming about COGS watchers and feeders and sending emails to Steve. • Updating new deposit pages and their help files. • More work on build and hold recipes. |
|
|
AU 792 |
|
Daily Ideas | 4/27/2012 |
-Tied to comment below – what about recipe/builds, internal invoices, or PO’s tied to stock/units. Just some ideas – maybe part of a build and build recipe or reverse build of sorts. -On stock/units we need the ability to have them produce child inventories (new items or new stock/units) of be broken (chop shop) in to smaller sell-able pieces. Start with something and then have it multiply or divide into something else. (Idea from another associate.) What about renting or borrowing from a master stock/unit? Does it totally go away or are we able to use it again? What does the word sell or sale mean? Brainstorming and recording ideas while cleaning out my email inbox: o On the eCommerce side – we need a customer portal where they can pay for past bills, create quotes, statements, buy new things and get access to custom paperwork or forms. Most of these ideas have been recorded before but the paperwork and forms (PDF, Word, Excel) have not been recorded. o On the label generator – it would be cool if we could make assignments to main application types and then build custom mappings for that type. It would be cool to be able to save these settings and be able to name them. Basically a custom 1-many between application types and fields or values. It may also be cool if you could hard code a value or let the system show an option. What about custom stuff like sized, logo, yes/no, font color, font size, positioning. o We need to make the words “make” and “model” dynamic if using specific units. o The calendar interface needs to be a back drop for any date/time related report, invoices per month, customer birthdays, bills and due dates, etc. o We need a mini calendar app to help on some of the date fields – not required but available. o We have a known issue with PO payments and the balance sheet. It has to do with force payments and how does that effect something. No way of searching, editing, fixing or finding what happened. o We need to circle back around and work on automating sales tax, collected fees, standalone declarations, watchers, feeders, callouts, etc. o On inventory items – we have been asked about multiple categories and sub categories. Currently using either the reference field or the RFID tag field as a text copy of the categories. o We were also asked about a part number grid (grid items) to hold values like red, white, blue, large, medium, small, etc. – attributes. o We have had requests for more flexible “Google-type” searches. These are called regular expressions or we can check for spaces and build our own list or array searches. o Add drill-down links from vendors to all incoming items (lines), all sold items, (invoice lines), all payments made (PO parts or e/r parts), all e/r line items, etc. o When starting a new location – it takes quite a while to get the starting inventory in. The system requires it, the parts inventory, to be entered one at a time. It would be cool if we could do something like an update PO but pull from all inventory items. This could be as simple as a switch or a permission to include all parts in the update or just location specific activity. Anyway, once completed, it would do what we want and setup initial inventory levels. (This whole idea could be done with the duplicate PO tool.) o The more we use the flex-grid, the more we will need ways of getting data in and out of it. The flex grid also needs to be a filter (pre-search filter) for other main application types. o We have a growing need to help manage cash drawers, petty cash, pay outs, etc. o On build PO’s – we need a way to add a new product (with a variable vendor) while in the build PO mode. Currently this is not allowed and requires a user to first prep and create the placeholder part and then go back and use it on or as a part of the build. Basically, they need a live PO to create the item and build PO to use it. It would be nice to have it all wrapped up together in a single step. o We had a request to make the customer log types dynamic per corporation. These are recorded as the customer log reason or subject field. Currently they are held in the contact_types table. All we would need to do is add a corp_id number and an add/edit interface and it could be done. o ICC’s (internal cost corrections), cost of goods corrections, cost differences – this is location specific, date sensitive and according to part numbers, what we need is a 1-many relationship from parts to the corrections. We virtually track what came in (PO’s), what was sold (invoices) and calculate the differences of cost differences between the two. This correction could really help with perfect Cost of Goods Sold (COGS). o On the accounting side, the cost differences would need to play into the P&L or income statement as part of COGS. It would also be cool if they, the differences or manual corrections, would show up under the part usage sections. o We talked about a thing called watchers and feeders for the balance sheet. This could be things like taxes, collected fees, etc. Why not cost of goods sold corrections or differences. It automatically sits in the background and runs logic on items sold vs. items sitting in inventory. This would be cool and would take out the manual portion of this task. If it was virtual, it could be very dynamic but may take more processing power. If it was manual, it would take up more storage space but would be quicker to get to. o What about correcting per location – locations play a part of inventory. o Steve wants to use an invoice depending on whether the cost needs to go up or down. Use a -1 of a +1 on the quantity. Each entry would have two lines. You would then adjust the cost accordingly, pretty creative. The price on both lines would be $0.00. Doing it this way only effects COGS and does not affect inventory because a -1 or a +1 =0 on the quantity side. Pretty cool! General ideas: o We need to go through the application and show/hide stock/unity fields, permissions and settings. This could be kind of a big project. However, it may make the interface simpler. o We’ve had request to be able to clean-up old inventory items. This is twofold: 1. COGS and 2. Quantities on hand. Basically, we need a “sweep the floor” function to get everything in order and then really hide the items on the look-back reports. Even if they are inactive, they still show up if there is a problem with COGS and quantities on hand. (ICC’s - internal cost corrections, see next page for another idea – April 30th entry) |
|
|
AU 2245 |
|
Brainstorming & Tech - Working on Build & Hold PO's (Recipes) | 4/27/2012 |
Working on build & hold PO’s: - Add in extra verbage to show what is what… PO side, invoice side, internal parts tickets, etc. - Be able to pass a valid PO number to and through the entire page flow. This includes side trips and adding and editing items. Be able to change the PO number if needed. - Make sure that the costs flow through correctly. This includes posting the total costs against the output or final project. - What about the recipe totals and calculations? Costs? Prices? Profits? Etc. - Make sure that the multiplier field works. - What about adding an item (part number) during the process… maybe show some logic and guide them in the right direction. - A PO must be started first, then checked for a valid build PO (PO type id = 4) - What about hidden line items on build and hold PO’s and recipes? - Be able to duplicate a PO including switching locations and PO types. Also, include/don’t include certain line items. Costs also need to be adjustable in this process. This should be a single page. - Make sure and check before doing the build. Valid PO number, valid recipe with ingredients and outputs. - Question on the build prep… Is it too strict? Meaning what about on the PO types? What about requirements for both ingredients and output values? Should we open it up any? Decided to keep it tight. - What about multiple outputs with calc on the fly costing? Should we open it up so that the user can change or manipulate the costs? - What about zero quantities – prepping the recipe – and then adding them in as options… this may change the cost calcs for the output. An example might be… cinnamon rolls with nuts, raisins, apple, icing, or not (options). If added, the cost needs to group. - We may need some java script of sorts to help with math on the build prep page. I could get really funky if we have more than one output value (say a byproduct or something). - What about partial usage or waste? How do we account for that? - What about breaking up packages or mix and matching items together… - What about adding in labor charges? Say a $75 fee for assembly of a kit or something. - What about forcing or substituting items? What about going over on one or more items and short on other items. - What about one department charging another department for labor or supplies. - How deep do we want to go... mini manufacturing, heavy, or full-on? What are the levels? Where are we headed? Keep it simple! - What about cost plus 10% or something like that? - Allow changes to prices and costs. Working with build & hold recipes: (extended costs & prices) (See scans in photo gallery for 4/27/12) |
|
|
AU 783 |
|
Daily Tasks | 4/28/2012 |
• New logo for a company. • Added a new section to the add mode for new expense/receipts for up to 3 line items. • This puts all of the main, the line items (up to 3), and the expense/receipt payments (up to 3) all on the same page. |
|
|
AU 2246 |
|
Tech - Expense/Receipt Add/Edit | 4/28/2012 |
Expense/Receipt Add/Edit: (See scans in photo gallery for 4/28/12) |
|
|
AU 784 |
|
Daily Tasks | 4/30/2012 |
• On the phone with Steve touching base and updating each other on progress and projects in the works, good stuff. • Tech support, emails and small tweaks. • Added the money type – “Drawer – Cash/Till” and changed “gift Certificate” to “Gift Card/Certificate”. Did some final testing on the new add expense/receipt line item section for the add main expense/receipt form. • More work on build and hold recipes. Also added options to open and close cost and price fields during the build process. This will help with some flexibility on the builds. |
|
|
AU 793 |
|
Daily Ideas | 4/30/2012 |
-On the part number look back report – maybe add a part number status filter and/or help them clean things up so that it works correctly. -We had a request to have a report and the ability to delete items (part numbers) in bulk. This would need to set COGS to the correct values and get rid of any remaining pieces (whole or parts) and mark the items as inactive. Do all of this all at once. |
|