Certainly Debbie, The UseExpensesInsteadOfHardCodedGrids.png screenshot below:
illustrates a solution I designed for an Oil & Gas Client several years ago, and
uses the Expense object (which was officially designed to track costs ) to prove the desired 1:many (one row per expense item) relationship, which
relate directly "under" a particular Project (in this case, but the same idea could be done under a Task or Issue), and
happens to be templatized (e.g. all the expense rows "show up" when the Project is created from a certain Project), which
effectively provides an ready and waiting quote of all possible items for the end user to then fill in as a Quote, and
uses custom data at the expense level to capture a number of specific fields, such as
Revenue Category (for grouping), Revenue Type (for sub grouping), Quoted Units ("how many?"), Book Rate (for standardized Price Book pricing), Override Rate (special deal as a $/unit instead of the Book Rate), Quoted Discount (special deal as a % off the Book Rate), Quoted Rate (a calculated field of the resulting Rate, after discounts), Quoted Amount (Quoted Units * Quoted Rate), and Lock Quote (Yes/No checkbox so the user can confirm particular rows as negotiations process)
Negotiations then proceed and in time, all items are locked and the deal is struck, at which point we then used our "https://store.atappstore.com/product/magic-reports/" Magic Report solution to create a pdf of the quote for physical signatures (crude, but effective), the finalized pdf was then uploaded to Workfront for the record, and the resulting work (and in time, associated invoice...another Magic Report) was then scheduled and performed accordingly. Thanks for the stroll down memory lane. I hope it give you some ideas for your situation. Regards, Doug
Doug Den Hoed - AtAppStore