Hello Karen,

I'm sorry that you were disappointed at the recent Upgrade.

We had a long discussion about how Optional Fields should be implemented in Adagio JobCost:

• On which files they should be supported
• How they should flow from the other modules
• How they should flow to the general ledger

At the conclusion of the discussion, we decided that there were too many unanswered questions to adequately scope the development resources required, so that particular feature did not make the cut for this particular cycle. Compatibility with Adagio Console is important as well, for those sites wishing to automate tasks in JobCost, or at least make sure that people are elegantly removed from the system when a Console shutdown request is made.

Feel free to send me (or post) a description of how you would like Optional Fields to work in Adagio JobCost. What would you use them for? Where would they be entered? Where would they be printed? Would they flow to other modules (specifically Ledger)? Optional Fields could be on Jobs, Phases, Categories, Job Estimates, Cost and Billing transactions. They could flow from Payables, Receivables, Invoices, Inventory and BankRec. They could flow to Ledger.

As you can see, the number of interactions is high, and so the task is complex. I know you were looking for this in last year's Adagio Wish - I hope that we will be able to grant that wish soon. At the moment though, we are working on significant upgrades to Adagio Payables, Ledger, and Receivables as part of a necessary housekeeping release of the product line.