407-248-1481

QuoteWerks Update Center

Update Center home

Version 5.7 Summary
79 New, 96 Fixes, and 15 Miscellaneous features
New Features - Version 5.7
 1. SugarCRM version 11.2 is now supported! [Build: 1.03]

 2. GoldMine 2021.2 is now supported! [Build: 1.03]

 3. QuickBooks Desktop USA version 2022 is now supported! [Build: 1.03]

 4. Management Reports capabilities have been greatly expanded. In addition to reporting on the Documents and Product Databases, you can now create reports on Purchase Orders (purchasing), Payments, Contacts, Vendors, Bundles, Configurations, Required Items, and Optional Items. For the Purchasing reports, you can create a report that includes and links the POHeaders, POItems, FulfillmentItems, DocumentHeaders, and DocumentItems all together resulting in very powerful reporting! The Payments table is auto-joined with the DocumentHeaders table. All Management Reports have the ability to Export the report data to text file output, so now all this data can be easily exported and then imported into any other system. [Build: 1.03]

 5. New VendorRFQ product release, including integration with QuoteWerks. VendorRFQ enables customers to communicate with their vendors, discussing and negotiating pricing and details for goods and services, collecting and organizing this information from one or all of their vendors. Your purchasing team will be able to compare and find the lowest prices to purchase available specific goods and services, while knowing at any given time which vendors have received the request for quote, and which have responded. All purchasing and procurement information is available in a centralized location for your team. Under the Utilities->Vendor maintenance menu you will want to setup your vendors, and make sure to enter your account number, the vendor sales rep name, email address, and phone. From the Quote Workbook, simply select an item and click on the VendorRFQ action button to create an RFQ and invite vendors. You can also do this from the Purchasing window. VendorRFQ requires the Corporate Edition of QuoteWerks, a SQL backend (either QuoteWerks DB Hosting subscription, or a SQL database that vendorrfq.com server can access), and a VendorRFQ subscription. VendorRFQ is only supported in master installations, it is not supported in Remote Site or Remote PC installations. The VendorRFQ integration is also supported in the Quote Workbook in QuoteWerks Web. A Misc Access right of "CannotUseVendorRFQLicense" is implemented to control the use of licenses per user. Under the Utilities->View Logs menu, in the Event log, events for "Licensing.VendorRFQLicenseCountExceeded" will be recorded. [Build: 1.03]

 6. Product Sourcing Panel. What used to be the "Etilize panel" now will show product sourcing information even if you do not have an Etilize subscription, and specifically will display any Vendor RFQs for the selected item and also will show any product data source matches if that option has been setup under the Misc tab of the Tools->Options menu. There is now a [Refresh] button, and a new orange indicator that is displayed next to the vendor that is currently the vendor for the line item in the quote. [Build: 1.03]

 7. For Maximizer CRM users, Maximizer CRM 2021 R3 is now supported! [Build: 1.03]

 8. For Product Content Subscribers, added support for Amazon Business pricing. When credentials are setup, searching for products in the Product Lookup Amazon source will return products using the Amazon Business API rather than the Amazon PAPI (Product API) which has the benefit of returning Amazon Business pricing based on your Account versus generic Amazon pricing. [Build: 1.03]

 9. Tech Data France Real-time Pricing & Availability is now supported! [Build: 1.03]

 10. For ConnectWise Manage users, when writing Recurring Forecast Lines or Products to the ConnectWise Opportunity, if the Start and End Dates are not specified, there is now a setup option to default the dates to be "one month" or "one year" from the Opportunity Close Date. The previous behavior would set the recurring end date to be one year from the Opportunity Close Date. This option is useful because ConnectWise Manage takes the value of the contract (ie 12 months * price) when setting the value of the opportunity line item which inflates the value of the opportunity at a glance. [Build: 1.03]

 11. For Zoho CRM users, there is now an option to create quotes in Zoho CRM that are associated with the Zoho CRM Deal. These Quotes are populated with line item detail from the QuoteWerks quote. Line Item detail in Zoho Quotes, is only available in the Professional, Enterprise, and Ultimate editions of Zoho CRM. [Build: 1.03]

 12. For Zoho CRM users, bi-directional Data Linking is now supported for Zoho CRM Quote Headers. Field information can be copied from QuoteWerks into the Zoho CRM Quote and then fields can also be copied from the Zoho CRM Quote Item into QuoteWerks. This happens when QuoteWerks creates or updates an Zoho CRM Quote. This can be done on the Quote level with the EventAction of "CRMQuoteHeader_CreateUpdate". [Build: 1.03]

 13. For Zoho CRM users, bi-directional Data Linking is now supported for the Zoho CRM Quote Items. Field information can be copied from QuoteWerks into the Zoho CRM Quote Item and then fields can also be copied from the Zoho CRM Quote Item into QuoteWerks. This happens when QuoteWerks creates or updates an Zoho CRM Quote. This can be done on the Quote Item level with the EventAction of "CRMQuoteItem_CreateUpdate". [Build: 1.03]

 14. For Zoho CRM users, when creating or updating a Zoho CRM quote, the Sold To, Bill To, and Ship To addresses will be populated in the quote. This functionality can be disabled in the Settings Manager, byval setting SystemSettings\ZohoCRM\DontSetSoldToContactInQuote=-1 SystemSettings\ZohoCRM\DontSetShipToContactInQuote=-1 SystemSettings\ZohoCRM\DontSetBillToContactInQuote=-1 [Build: 1.03]

 15. For Zoho CRM users, in the Zoho CRM Setup in QuoteWerks, when on a Mapping Window, lists of the mappings can now be copied to the Windows Clipboard. If you double click on the left column header, you will be prompted if you want to copy the mapped pairs to the clipboard. If you double click on the right column header, you will be prompted if you want to copy all of the available mappings to the clipboard. Copying the available mappings to the clipboard is helpful, because you can use this data to import into F2 Lookup values including the ItemType in QuoteWerks. [Build: 1.03]

 16. There is a now a Utilities->Customer / Product Price Profile Matrix Maintenance menu that enables you to setup the Price Modifiers to map to each combination of Customer profile and Product profile. This has existed for many years, but was only accessible when editing a native product. Now it is available through this main menu, so that it is easily accessible for the new Etilize Category mappings to Product Profiles. This is very useful for setting up pricing of products without having to explicitly set a Price Modifier for every single part number. Instead you can assign each part number a product price profile like "HARDWARE", "LABOR", "SERVERS", "WORKSTATIONS", etc. Next you specify the Price Modifier to use for each combination of product profile and customer profile like "GOLDLEVEL", "SILVERLEVEL", etc. [Build: 1.03]

 17. For Product Content Subscribers, in addition to being able to setup the Etilize Category mapping to a Price Modifier, you can now map it to a Product Price Profile like "SERVERS". This can then be used with the Customer Profile and Product Profile Matrix which is now accessible through the Utilities->Customer / Product Price Profile Matrix Maintenance menu. [Build: 1.03]

 18. On the System tab of the Help->About window, Double clicking on a system information value will display the value and also copy it to the Windows Clipboard. [Build: 1.03]

 19. The Payments table now has an ByProxy field and the card ref is no longer encrypted and will look like "VISA x1111 exp 12/21". These changes will be more useful now that you can run management reports on the Payments table. [Build: 1.03]

 20. For QuickBooks Online Users in the United States, added support for Automated Sales Tax calculations (PartnerTax) allowing QuickBooks Online to automatically calculate the tax for the jurisdiction rather than specifying a specific tax code. [Build: 1.03]

 21. For Autotask users, in the Autotask Setup in QuoteWerks, when on a Mapping Window, lists of the mappings can now be copied to the Windows Clipboard. If you double click on the left column header, you will be prompted if you want to copy the mapped pairs to the clipboard. If you double click on the right column header, you will be prompted if you want to copy all of the available mappings to the clipboard. Copying the available mappings to the clipboard is helpful, because you can use this data to import into F2 Lookup values including the ItemType in QuoteWerks. [Build: 1.03]

 22. For Act! users, in the Act! Setup in QuoteWerks, when on a Mapping Window, lists of the mappings can now be copied to the Windows Clipboard. If you double click on the left column header, you will be prompted if you want to copy the mapped pairs to the clipboard. If you double click on the right column header, you will be prompted if you want to copy all of the available mappings to the clipboard. Copying the available mappings to the clipboard is helpful, because you can use this data to import into F2 Lookup values including the ItemType in QuoteWerks. [Build: 1.03]

 23. For HubSpot users, in the HubSpot Setup in QuoteWerks, when on a Mapping Window, lists of the mappings can now be copied to the Windows Clipboard. If you double click on the left column header, you will be prompted if you want to copy the mapped pairs to the clipboard. If you double click on the right column header, you will be prompted if you want to copy all of the available mappings to the clipboard. Copying the available mappings to the clipboard is helpful, because you can use this data to import into F2 Lookup values including the ItemType in QuoteWerks. [Build: 1.03]

 24. For SugarCRM users, in the SugarCRM Setup in QuoteWerks, when on a Mapping Window, lists of the mappings can now be copied to the Windows Clipboard. If you double click on the left column header, you will be prompted if you want to copy the mapped pairs to the clipboard. If you double click on the right column header, you will be prompted if you want to copy all of the available mappings to the clipboard. Copying the available mappings to the clipboard is helpful, because you can use this data to import into F2 Lookup values including the ItemType in QuoteWerks. [Build: 1.03]

 25. For salesforce.com users, in the salesforce.com Setup in QuoteWerks, when on a Mapping Window, lists of the mappings can now be copied to the Windows Clipboard. If you double click on the left column header, you will be prompted if you want to copy the mapped pairs to the clipboard. If you double click on the right column header, you will be prompted if you want to copy all of the available mappings to the clipboard. Copying the available mappings to the clipboard is helpful, because you can use this data to import into F2 Lookup values including the ItemType in QuoteWerks. [Build: 1.03]

 26. For salesforce.com users, in the salesforce.com Setup in QuoteWerks, when the associated contact does not have any shipping information, you can specify if the Billing address or the Shipping address of the account should be used. [Build: 1.03]

 27. There is now a QuoteWerks Web button on the main toolbar to facilitate getting into QuoteWerks Web from within QuoteWerks Desktop. [Build: 1.05]

 28. The Select Vendors window now has the spotlight search capability and it will now show the total number of selected vendors, and will show a list of all the selected vendors at the bottom of the dialog, and the tooltip text will display the complete list in the event the list is so long it gets cutoff. [Build: 1.05]

 29. On the product Sourcing panel, if the vendor part number exceeds 17 characters, the full 40 character Vendor Part Number will be displayed in the Tooltip text when hovering over the Vendor Part Number control. [Build: 1.05]

 30. For QuickBooks Online users, there is now an [Ok for All] button that can be used when automating the creation of Items in QuickBooks, remembering and applying all the Item Type and Account selections. Very useful when exporting larger quotes over to QuickBooks and also when exporting Purchase Orders over to QuickBooks. Without this feature, if the integration creates 50 items in QuickBooks, you would have to click OK 50 times. [Build: 1.03]

 31. For ConnectWise Manage users, there is a new option when configuring the QuoteWerks integration to ConnectWise to determine what the taxable status of a group header will be when sent to ConnectWise. The taxable status can be fixed as taxable, not-taxable, or calculated based on if any group member is taxable or not. With the last option, if any group member is taxable, the group header will be taxable. If no group members are taxable, the group header will not be taxable. This option is configured on the Bundles sub-tab of the Products Tab on the ConnectWise Manage Setup. [Build: 1.08]

 32. On the Misc.Printing tab under Tools->My Preferences menu, there is now an option "Paper Size when saving from HTML" [Build: 1.08]

 33. For Zoho CRM users, you can now select a default Deal Pipeline on the Deal tab in the Zoho CRM Integration Setup window. [Build: 1.08]

 34. For Zoho CRM users, you can now select a default Deal Layout on the Deal tab in the Zoho CRM Integration Setup window. [Build: 1.08]

 35. For Zoho CRM users, you can now select a Layout and Pipeline on the Create/Update Deal window. [Build: 1.08]

 36. The Online Ordering grid for Tech Data, Ingram Micro, SYNNEX, D & H, and Dell now display the ManufacturerPartNumber column. [Build: 1.08]

 37. AutoRecover has replaced AutoSave. AutoRecover and AutoSave are both ways to prevent loss of your in-progress work due to a variety of reasons including power loss, computer lock ups, network disconnect, SQL server timing out, etc. AutoSave permanently saves any changes you make to your document as you are making the changes. The downside of this is that you can't open up a document and just make some "hypothetical" or "what-if" to see what it looks like because the AutoSave just made those changes permanent. Also, often we want to open up an existing document, make changes and then just save those changes as a new document, but you can't do that with AutoSave either because it just made those changes permanent to the original existing document. AutoRecover is a superior solution. It just quietly saves a temporary backup of your in-progress work. If you choose not to save the changes, or just close the document, it discards those changes. If QuoteWerks quit unexpectedly for the above reasons, then when you re-launch QuoteWerks it will ask you if you want to recover the in-progress changes. Additionally, AutoRecover has been implemented when the feature to "Terminate Running Instance" is used. Previously it would save copies of all quotes that were open on the terminated instance. Now it just creates AutoRecover documents for them all. If AutoRecover sounds amazing, its because it is! Microsoft Word Desktop has had an AutoRecover feature for decades. For Developers, the addition of AutoRecover will require some changes. The AutoRecover document is stored in the DocumentHeaders and DocumentItems tables just like a regular document, however there is a new DocumentHeaders.IsAutoRecoverDocForDocRecGUID field. If this field is populated then this is an AutoRecover document. If querying the database you will want to make sure that you filter these documents out with IsAutoRecoverDocForDocRecGUID=''. In fact, when looking for documents you will aready want to apply the filter of TemplateType=0 AND Superceeded=0 AND IsAutoRecoverDocForDocRecGUID='' so that the query excludes templates, superseded documents and AutoRecover documents. We also renamed UserSettings KeyName='EnableAutoSave' to KeyName='AutoRecoverEnabled' and UserSettings KeyName='AutoSaveInterval' to KeyName='AutoRecoverInterval'.Also, since an AutoRecover can replace the previously saved document, changing the DocumentHeaders.ID value, it is recommended to query a specific document based on the DocumentHeaders.RecGUID. [Build: 2.11]

 38. For QuoteValet payment users, Stripe Checkout is now supported! Stripe Checkout differs from our standard Stripe Payments integration in that the customer is redirected to Stripe's own servers during the payment process. This offloading to Stripe ensures compliance across a full range of European regulatory requirements (PSD, PSD2, SCA, 3DS, 3DS2 etc). Setup requires only a few additional steps beyond the standard Stripe configuration (including adding a Webhook entry in Stripe's Dashboard and then pasting the corresponding signing secret into the Payment Setup in QuoteWerks). [Build: 2.11]

 39. POItems now have Custom fields that you can populate with information pulled from the quote. They are poiCustomText01, poiCustomText02, poiCustomText03, poiCustomText04, poiCustomText05, poiCustomNumber01, poiCustomNumber02, poiCustomMemo01, and poiCustomDate01. You can map which information gets copied into these fields from the Purchasing tab of the Tools->Options menu. Supports &DH_, &DH_, &APP_, and &SYS_ macros. It does not support &DH_&XXX or &DI_&XXX macros. [Build: 2.11]

 40. For Autotask users, Autotask Service Bundles can now be searched from the Product Lookup window. [Build: 2.11]

 41. For Autotask users, when searching by Description with Autotask Service Bundles lookup, the Invoice Description will now also be searched. [Build: 2.11]

 42. For Autotask users, you can now map the Invoice Description field when doing a Service lookup. [Build: 2.11]

 43. For Autotask users, when searching by Description with Autotask Service lookup, the Invoice Description will now also be searched. [Build: 2.11]

 44. For Autotask users, users can now see the Inventory on Hand for products on the Product Lookup window. This feature is accessed by right clicking on a product search result and selecting 'Show Autotask Inventory On Hand' [Build: 2.11]

 45. For Autotask users, when creating new products, the Vendor name will now be added to the product. [Build: 2.11]

 46. For Autotask users, a Won/Loss Reason combobox was added to the Won/Loss Opportunity window. [Build: 2.11]

 47. For Autotask users, a Close Description textbox was added to the Won/Loss Opportunity window. [Build: 2.11]

 48. For Autotask users, you can now specify a default Tax Code when using Autotask Service Bundles. [Build: 2.11]

 49. For Autotask users, you can now specify a default Item Type when using Autotask Service Bundles. [Build: 2.11]

 50. On the Print Preview window, if the user requires approval to "SavePDF", then when selecting the "Attach to CRM" action, this approval will be required before you can perform the "Attach to CRM" action. [Build: 2.11]

 51. When creating a Purchase Order in QuickBooks Online, If the Checkbox is not checked to use the QuoteWerks Vendor Maintenance Email Address for the Vendor in the QuoteWerks QuickBooks Online setup, the Primary Email Address for the Vendor/supplier in QuickBooks Online will be used. This mimics the behavior when manually creating a Purchase Order for a Vendor / Supplier in QuickBooks Online. Prior to this change, the email address would be blank if the checkbox was not checked. [Build: 2.11]

 52. For QuickBooks Online users, when creating a new Item in QuickBooks Online (In addition to just the Purchase Order), the PO Description / Purchasing Description mapping set in the QuickBooks Online Settings window will be used for the Purchasing Description if the mapped field is different than the Description Field mapping. [Build: 2.11]

 53. Expansion of PrintTime macros. When printing from a layout or a word document, you can use macros like &DH_SoldToCompany in the IntroductionNotes, ClosingNotes, PurchasingNotes, InternalNotes, and DynamicNotes fields that will be replaced with their actual values in the print output only. Now you can also use the PrintTime macros in the CustomText01-CustomText28 and CustomMemo01-CustomMemo04 fields. [Build: 2.11]

 54. For Peachtree users, on the Export to Peachtree window, clicking on the DocDate column will now sort by date. [Build: 2.11]

 55. For VendorRFQ users, when clicking on the [Update] button on the Product Sourcing Panel when a VendorRFQ vendor is selected, you will now be prompted if you want to just update the line item with the current price from the selected RFQ vendor, or if you want to do that and also award the vendor the bid which closes out the bidding for all the other RFQ vendors. [Build: 2.11]

 56. In the Settings Manager, you can now highlight and copy text from the Section Name and Key Name text boxes when editing/viewing a setting. All the text boxes are now wider as well. [Build: 2.11]

 57. The Tools->Refresh Item Details now supports updating the UnitCost, UnitPrice, UnitList, CostModifier, and PriceModifier fields. When updating these fields from the Refresh Item Details window, you have more advanced control over the pricing fields as opposed to the Get Latest Pricing feature. When using Refresh Item details, if you update the Price, the PriceModifier will be cleared just like when you manually enter a price in the line item through the Document Items grid. Same for the Cost and CostModifier. There is an option "[] Display Adjust Price Dialog if cost is changed" which will give you a chance to apply a UnitCost change and also determine the UnitPrice should be affected if the UnitPrice was being calculated by a PriceModifier. Using Refresh Item Details, it simply updates individual specified fields without any regard to the relationships between these Pricing fields. In contrast, the Refresh item w/Latest Pricing behaves differently depending upon if there is a CostModifier and/or PriceModifier. If there is no PriceModifier, then it will update all the pricing fields including the UnitCost, UnitPrice, and UnitList fields, however if there is a Price Modifier, it will update the UnitCost and UnitList and then ask how you want to handle the UnitPrice that is being affected by the change in UnitCost. [Build: 2.14]

 58. You can now set Access Rights for more than one Literature file at a time. To do this, From the File->Print window, you need to check the "Administration mode" checkbox, and then place a checkmark next to every Literature file that you want to set the same Access rights for, then right click and choose "Set Access Rights for all checked items". [Build: 2.14]

 59. You can now enter an ItemType for a Section Header type line item. This gives you more control over not including this type of line item when calculating Deposit Required summing. It is not recommended to use this to Include the Section Header total, but rather to disclude it from the summing action. [Build: 2.14]

 60. The [Request Approval] button on the Print window will now be enabled even if the customer has accepted the quote through QuoteValet. The reason is that after the acceptance, maybe the sales rep needs to change a Purchasing Notes field or similar field and with this button enabled they can now request the approval again. [Build: 2.14]

 61. When one or more line items are selected in the Quote WorkBook and you press the down or up arrow key, these selections will be cleared. Also on the Edit->Line Attributes window, pressing ENTER while on any field will perform the same action as clicking on the OK button. [Build: 2.14]

 62. When using Tools->Refresh pricing w/Latest if the item pricing method was P or M, and the realtime pricing vendor returned a list price and the list price will now be updated. [Build: 2.14]

 63. GoldMine 2022.1 is now supported! [Build: 2.22]

 64. SugarCRM version 11.3 is now supported! [Build: 2.22]

 65. For SugarCRM users, you can now create a new SugarCRM Account and Contact record from the QuoteWerks SoldTo/ShipTo tab using the information already entered on the SoldTo/ShipTo tab. For the feature to be enabled, the Contact field cannot already be populated with a contact that was retrieved from SugarCRM. Also, the Company, and Contact must be populated. This feature is available on the toolbar above the SoldTo, ShipTo, and BillTo areas of the Quote WorkBook. There is also an Access Right "CannotCreateCRMContact" that you can set if you do not want specific users to be able to use this feature. [Build: 2.22]

 66. For salesforce.com users, discount line items will now be included in Opportunities. [Build: 2.22]

 67. For MS CRM users, when using Data Links, custom ListType fields now return the Name field instead of the numeric Value. [Build: 2.22]

 68. When Saving as Next Revision, if there is an existing CRM Opportunity associated with this quote, the opportunity will be updated. [Build: 2.27]

 69. SalesLogix (Infor CRM) 8.5 is now supported! [Build: 1.03]

 70. ConnectWise 2021.3 is now supported! [Build: 2.11]

 71. For Autotask users, when adding a product to an Autotask quote, the Autotask product description field can now include Document Item macro fields. Ont he Autotask integration Setup window, under the Opportunities.Quote Products tab the Mappings section includes a Description tab. [Build: 2.36]

 72. For Autotask users, when retrieving recurring products from Autotask, there is a new setup option to choose if the First Payment should be included. In the QuoteWerks Autotask setup, this option is found by navigating to the Opportunities tab and then to the Quote Products sub-tab. The check box is named "First Payment Included in Document Totals for Recurring Products". [Build: 2.36]

 73. For Autotask users, there is now a Contains and Begins with search option on the Lookup contact window. [Build: 2.36]

 74. For Autotask users, default Status, Staging, Close Reason, and Close descriptions can be added for the various stages of a quote. These settings can be found by navigating to the Opportunities tab and then to the Stages sub-tab. [Build: 2.36]

 75. For ConnectWise users, product lookup searches that return lots of results are now significantly faster. [Build: 2.36]

 76. The Utilities->Document Transport File Diagnostics window has been redesigned and combined with the Utilities->Document Backup Manager. The result is that now there is just a Utilities->Document Transport File Manager menu. This new Document Transport File Manager has a begins with search feature useful for locating a dtf file in the list. There is now a [Restore] button that makes it easy for you to restore the database version of the quote from a DTF file version of the quote. There is also a Right click "Open Document in DB" menu. The Utilities->Document Transport File Manager now shows more details about the .bxx, .dtf, or .dta file, including details like GrandTotal and number of line items, and about the DB version of the document if it exists. [Build: 2.39]

 77. The Import Document now shows more details about the selected .bxx, .dtf, or .dta file, including details like GrandTotal and number of line items, and about the DB version of the document if it exists. [Build: 2.39]

 78. The File->Document Properties window now shows more details about the selected .bxx, .dtf, or .dta file, including details like GrandTotal and number of line items, and about the DB version of the document if it exists. [Build: 2.39]

 79. When placing an Online Order With Tech Data, Ingram Micro, SYNNEX, or D&H, none of them support supplying a ShipToEmailAddress for the electronic order. However we've added a ShipToEmailAddress field to these distributors order screens so that after the order is placed and the QuoteWerks PO is saved in QuoteWerks this ShipToEmailAddress will be populated in the QuoteWerks PO. [Build: 2.39]

Misc Features - Version 5.7
 1. The general Setup Data Mappings form used in many areas now has a much faster load time. [Build: 1.03]

 2. For API Users, the DocRecGUID is now assigned in memory when a new blank quote is instantiated before it is saved to the database. [Build: 1.03]

 3. For ConnectWise Manage users, in the ConnectWise Manage Integration Setup in QuoteWerks, blank options were added for Status Notifications and Defaults for Service Tickets. This will enable the user to select a blank option to clear the default that was previously set. [Build: 1.03]

 4. QuickBooks Desktop version 2002, 2003, and 2004 are no longer supported. [Build: 1.03]

 5. Microsoft oAuth now uses Webview2 for authentication (Microsoft Edge based) rather than Microsoft Internet Explorer. If Webview2 is not installed on the workstation, it will automatically be installed prior to authentication. [Build: 1.03]

 6. VendorRFQ now has a "Submit Bid by Proxy" menu. You can use this Bid By Proxy to submit a bid on behalf of your Vendor. Usually you will use this if your Vendor has given you a price verbally or has sent you an email with pricing. [Build: 1.05]

 7. If a line item that is linked to an RFQ is deleted from a quote, this action will be logged in the Event Log. [Build: 1.05]

 8. On the Open Document window you can now search the QuoteValetDocumentID field. [Build: 1.08]

 9. On the Tools->Options menu, renamed the "Synchronization" tab to "Sync". [Build: 2.11]

 10. The .lt (layout new template) files will now always be installed and overwritten if exist. [Build: 2.11]

 11. The option for "Check for in-use documents" is no longer an option, it is always enabled. [Build: 2.11]

 12. Unused fields from DocumentHeaders have been removed: Region, RefuseSync, Result, ExpectedCloseDate, CompletionDate, InUseBy, MiscLinkID, ShipDate, AdditionalAddress, Version. [Build: 2.11]

 13. Activated beta testing support for GoldMine 2022.1 [Build: 2.11]

 14. For QBO users, Added "VendorAndPurchasesPrefs.PurchaseOrderEnabled" and "VendorAndPurchasesPrefs.UseCustomTxnNumbers" to the QuickBooks Online Info on the QuickBooks Online Settings Window in QuoteWerks. Note: If VendorAndPurchasesPrefs.UseCustomTxnNumbers is TRUE and a Purchase Order Number is not specified in QuoteWerks when creating the PO in QuickBooks Online, the PO Number in QuickBooks Online will be blank. It is recommended to turn this setting off in QuickBooks Online to avoid Purchase Orders in QuickBooks Online without PO numbers. [Build: 2.11]

 15. When converting a Quote to an Order an unnecessary database query was being run looking for Revisions when there was known to be no revisions. [Build: 2.39]

Fixes - Version 5.7
 1. For ConnectWise Manage users, when creating/updating a ConnectWise Service Ticket, Project Boards would be visible when selecting a Service Board. Project Boards will no longer be visible when creating/updating Service Tickets. [Build: 1.03]

 2. For ConnectWise Manage Users, when saving a new Order/Invoice (not via a document conversion), the Win Opportunity options were not appearing when creating/linking to an existing Opportunity. [Build: 1.03]

 3. For ConnectWise Manage Users, When creating/updating a ConnectWise Opportunity and writing forecast lines (not product items) with the "Include Revenue in Total Forecast" unchecked, the "Include Revenue" checkbox would still be checked on the ConnectWise Opportunity. [Build: 1.03]

 4. For Kaseya BMS users, QuoteWerks would only return the first 100 employees / sales reps from Kaseya BMS. There is no longer a limitation to the number returned. [Build: 1.03]

 5. For Zoho CRM users, when attempting to retrieve all attachments from the Merge Document Transport Files window, users would receive an INVALID_URL_PATTERN error. [Build: 1.03]

 6. For Zoho CRM users, if the contact street address was blank, the parent account information was replacing all contact address information even if the account address fields were blank. [Build: 1.03]

 7. The URL used to initiate a FedEx package tracking from the purchasing window, needed to be updated to reflect a change in the URL on the FedEx website. [Build: 1.03]

 8. For Tech Data Online Ordering users, when placing an electronic order though QuoteWerks, on the Tech Data website, under the Reseller Contact Name area, the End users name would be listed there along with the resellers email address and phone. [Build: 1.03]

 9. On the Misc tab of Tools->Options, the setting "When setting up Required Items, default 'Link quantity to parent item' to yes." was not being saved or applied. [Build: 1.03]

 10. For API users if setting the UnitCost value and the Misc Access Right of "CannotManuallyModifyUnitCostInDocument" is set then you would receive an error message when attempting to update this field. Similar message for UnitPrice and UnitList. [Build: 1.03]

 11. Deleting a line item that was the parent in a dependent quantity relationship, the children were not updated to reflect the parent no longer existed. [Build: 1.03]

 12. When importing a text file, the auto line delimiter detector would incorrectly detect the line delimiter as LF if the first line contained column headings and the column heading had a line feed character in it because the column title was two lines and was probably exported from Excel. [Build: 1.03]

 13. For GoldMine users, after exporting order to QuickBooks, the GoldMine linked document Type field was not getting updated. [Build: 1.03]

 14. For salesforce.com users, when searching by account the address isn't pulled in for a contact with no mailing address. [Build: 1.03]

 15. For MSCRM users, when a quote is converted to an order in QuoteWerks and a comma is used as a decimal separator, the 'Actual Revenue' field value is multiplied by 100. [Build: 1.03]

 16. For MSCRM users, the Actual Revenue field was only being populated on the first Opportunity save. [Build: 1.03]

 17. For MSCRM users, existing opportunities were not being displayed on the opportunity dropdown control for the Create Opportunity window if the Account did not have any contacts. [Build: 1.03]

 18. For HubSpot CRM users, the company name search was not showing the company address for contacts that did not have an address. [Build: 1.03]

 19. For MSCRM users, when both an account and contact was linked to the quote, when the MSCRM opportunity was created, only the contact was linked to the opportunity, instead of both the account and the contact. [Build: 1.03]

 20. Google made a change to authentication requirements for desktop applications. GMail oAuth in QuoteWerks now uses an external browser for Authentication. [Build: 1.03]

 21. When creating a Vendor RFQ in a country with non USA date format would receive error about datetime data type. [Build: 1.04]

 22. When rehosting to SQL, the VendorRFQ tables would not get created. [Build: 1.05]

 23. For VendorRFQ users, when converting from QUOTE to ORDER to INVOICE, the RFQ links were kept in all the documents, now they will only be in one document, the QUOTE, or the ORDER, but never the INVOICE. [Build: 1.05]

 24. For VendorRFQ users, If a quote had line items in it that were linked to VendorRFQ items, and that quote was saved as a Template, the Vendor RFQ data was not getting removed. [Build: 1.05]

 25. For VendorRFQ users, If a quote had line items in it that were linked to VendorRFQ items, and the Save As Next Revision action was performed on the quote, the Vendor RFQ data was not getting removed from the previous revision (if the option to keep previous revisions was set). [Build: 1.05]

 26. If there was only one line item in the quote and the user choose to delete it, the code to recall a vendor rfq item was not being run. [Build: 1.05]

 27. In the Synchronization Wizard, pressing DEL key while on the Profile combo box was not deleting the selected profile. [Build: 1.05]

 28. For QuickBooks Online users, if the "I do not charge sales tax in QuickBooks" checkbox in the QuoteWerks setup for QuickBooks Online was checked, the following error would be returned when exporting documents to QuickBooks Online: "The selected Sales Tax Item '' was not found in QuickBooks. Export cancelled." [Build: 1.08]

 29. On the Product Sourcing Panel, the availability table was getting cutoff on the right side. [Build: 1.08]

 30. For QuickBooks Desktop users, exporting payments to QuickBooks Desktop caused an XML failure issue on the CardRef. [Build: 1.08]

 31. The InUseDocuments logic was rewritten to lessen the time frame window in which two users could possibly open the same quote at the same time. [Build: 1.08]

 32. When the "[] Check for In Use documents" option was not checked, records were still being added to the InUseDocuments table. [Build: 1.08]

 33. For Zoho CRM users, when closing a quote, users would receive an error message about deleting an existing attachment record. [Build: 1.08]

 34. For Zoho CRM users, Zoho CRM quote items did not have the unit price value. [Build: 1.08]

 35. For Product Content Subscribers, when using the Multiple Product Database Search, Amazon could be available as a Product Source to choose from. The integration with Amazon and Amazon Business does not allow for this functionality and no results would be returned the source was selected. Amazon will not be selectable for as a source for the Multiple Product Database Search. [Build: 1.08]

 36. Under File-Import menu, When importing an older XML file from our competitor data conversion utility would receive error Run-time error '91': Object variable or With block variable not set. [Build: 1.08]

 37. On the Purchasing Window, when selecting more than one item from the same document would receive an error that there was more than one InUse Document record. [Build: 2.11]

 38. For Zoho CRM users, if more than 2 decimals were used for the Unit Cost or Unit Price fields in QuoteWerks, Zoho CRM would error out when attempting to create the quote line item. [Build: 2.11]

 39. For VendorRFQ users, it was allowing you to create an RFQ item for an item that did not have a ManufacturerPartNumber. [Build: 2.11]

 40. Placing an online order with D & H, when you click Verify current P& A it crashes QuoteWerks. Type mismatch error. [Build: 2.11]

 41. When the real-time module was activated, and when using Refresh with Latest pricing on a line item that had vendor that did not exist, the UnitCost would be set to 0. [Build: 2.11]

 42. For Amazon users, When 'Enable Individual Product Data Source Security' was set to ON, Non-Master Rights users could not see the Amazon product source in the Product window [Build: 2.11]

 43. On the Pricing tab of the Edit Product window, when the []Base pricing on foreign currency option was set and the Item Costing Method was "Discount from List", and the Foreign List Price amount was changed, the "Foreign Cost amount" was not changing. Also when importing and choosing to update the Foreign List, the Foreign Cost and Foreign Price were not getting updated as expected. [Build: 2.11]

 44. For MS CRM users, writing to custom number fields were not being saved to a MS CRM opportunity. [Build: 2.11]

 45. For Autotask users, when a user does not use a valid email address for the username field for the API login credentials, a more descriptive error message will be displayed. [Build: 2.11]

 46. For Autotask users, when creating a service item with a description over 400 characters, the item would not be added. Descriptions over 400 characters will now be saved under the Invoice Description field for the first 1000 characters. [Build: 2.11]

 47. For Autotask users, the Opportunity name field on the Create/Update Opportunity window was being shortened to 100 characters instead of the 128 characters that Autotask allows. [Build: 2.11]

 48. For ConnectWise Manage users, while searching for a ConnectWise Manage company/contact in QuoteWerks, if a ConnectWise Manage company was deleted and was not removed from the ConnectWise Manage 'Recycle Bin', the company would still be retuned in the search results. [Build: 2.11]

 49. When a Product Data Source was disabled due to something like the database file was not found, you were not able to manually disable the Product Data Source. [Build: 2.11]

 50. When QuoteWerks was started and then left at the Login window for longer than the AutoRecover period would receive error 9 subscript out of range. [Build: 2.11]

 51. For VendorRFQ users, when selecting items that were associated with a vendorRFQ and converting them to a group, if you proceeded, the VendorRFQ items would be recalled which was not an intended behaviour. [Build: 2.11]

 52. For Google Contacts users, Google changed their API requiring changes for the integration to continue to work. [Build: 2.11]

 53. For ConnectWise Manage Users exporting QuoteWerks Purchase Orders to ConnectWise Manage 2021.3, an error similar to "'The line number '1' already exists [ resource: purchaseOrderLineItem - field: ]" would be returned with more than One PO Line Item. This is due to a page count and Line item count issue in ConnectWise Manage (the ConnectWise Line Item issue documented in ConnectWise tickets 14460914 and 13694355). QuoteWerks development is using a workaround to enable Purchase Orders to be sent from QuoteWerks to ConnectWise Manage. This workaround will work for ConnectWise Manage 2021.3 users and higher. [Build: 2.11]

 54. For Google Contacts users, Google discontinued support for the Google Contacts API, the integration needed to be rewritten to use their new People API. The new People API only allows 30 search results to be returned unlike the previous API. [Build: 2.11]

 55. For Google Contact users, the fax extension was not being shown in the Contact Lookup grid after completing a search. [Build: 2.11]

 56. For QuickBooks Online South African (ZA) users, the tax options when creating a Purchase Order were ignored. [Build: 2.11]

 57. For Amazon Business users, when placing an Online order with Amazon Business with the Vendor of 'Amazon Business', the Amazon PO Number on the Online Order form would not be visible. This entry is required when placing an Online Order with Amazon Business. [Build: 2.11]

 58. For Zoho CRM users, a null exception could occur when attempting to get the Zoho CRM version type. [Build: 2.11]

 59. For Zoho CRM users, closed deals were showing on the Create/Update Deal window dropdown. [Build: 2.11]

 60. For Zoho CRM users, closed deals were able to be saved multiple times. [Build: 2.11]

 61. For Zoho CRM users, when on the Close Zoho Deal window, the closing date was not defaulting to Today's date. [Build: 2.11]

 62. For Autotask users, the Quote Name field on the Create/Update window was allowing more than 100 characters. [Build: 2.14]

 63. For Autotask users, when creating a new Service item, users would receive an error message. [Build: 2.14]

 64. If a document was uploaded to QuoteValet, if it has been Accepted, or Accepted By Proxy, or Lost, then when you open the document, QuoteWerks will no longer try to apply field level changes from the QuoteValet document to the QuoteWerks document. This change fixes an issue where a customer accepted a quote on QuoteValet and supplied some field values that initially updated the QuoteWerks quote, but then the user changed them, and the next time they opened the quote, it would apply the values from the accepted QuoteValet quote, overwriting the changes the user had made after the acceptance. [Build: 2.14]

 65. For HubSpot CRM users, SoldTo and ShipTo Datalinking was not working for contacts that did not have a company associated with them. [Build: 2.14]

 66. For Zoho CRM users, SoldTo and ShipTo Datalinking was not working for contacts that did not have a company associated with them. [Build: 2.14]

 67. For salesforce.com users, the Document Number Datalink was not updating the set Opportunity field with the new Document Number when Converting a Quote to an Order. [Build: 2.14]

 68. For SugarCRM users, some API connections were not reconnecting after a long period of inactivity. [Build: 2.14]

 69. For Zoho CRM users, the Access token information was not being saved if a user created a new Access Token on the Manage User Access window and proceeded to click Cancel on the Zoho CRM Setup window. [Build: 2.22]

 70. For Zoho CRM users, clearing a user's credentials and opening up the Zoho CRM Setup window will display an error. [Build: 2.22]

 71. For HubSpot CRM users, the Access token information was not being saved if a user created a new Access Token on the Manage User Access window and proceeded to click Cancel on the HubSpot CRM Setup window. [Build: 2.22]

 72. For HubSpot CRM users, clearing a user's credentials and opening up the HubSpot CRM Setup window will display an error. [Build: 2.22]

 73. For MS CRM users, negative Unit Price line items were being added into MS CRM quotes in the Discount field. [Build: 2.22]

 74. For Autotask users, the 'Show Autotask Inventory On Hand' feature on the Product Lookup right click menu was not returning results if there was only 1 warehouse with inventory. [Build: 2.22]

 75. For MS CRM users, the Macro Tester was not working for Account datalink fields. [Build: 2.22]

 76. For QuoteWerks users, when the Complete of Opportunity from QuoteWerks setting is set to 'Never', the Opportunity was not being saved when the Quote was being Converted to Order or Invoice. [Build: 2.22]

 77. When importing some Tech Data Excel quotes, the promo pricing was not populating the Notes field. [Build: 2.22]

 78. When the Complete of Opportunity from QuoteWerks setting is set to 'Never', the Opportunity was not being saved when the Quote was being Converted to Order or Invoice. [Build: 2.22]

 79. When importing some Tech Data Excel quotes, the promo pricing was not populating the Notes field. [Build: 2.22]

 80. For users with AutoRecover enabled, would receive various errors as a result of a quote being open, and autorecover document generated, and then a different user tried to open that quote at the same time. [Build: 2.27]

 81. For Amazon Business users, when testing the integration via the [Test] Button on the Amazon Tab of the Real-time Setup form in QuoteWerks, a '400' error would be returned even though the integration with Amazon Business may have been working. This was due to a change in the Amazon API. [Build: 2.27]

 82. If there was an autorecover for a document that was never saved, and upon starting QuoteWerks you chose to delete this doucment, would receive an error about RecGUID and BOF or EOF. [Build: 2.28]

 83. For Access backend users, the changes in v5.6 build 5.10 that stored import log file data in the EventsLog table of the SITE.MDB file was causing the SITE.MDB file to grow past its 2GB max limit when running imports that updated existing records. [Build: 2.28]

 84. For Autotask users, more than 500 characters could be added to the Close Description when closing an Autotask opportunity. [Build: 2.36]

 85. On the Ordered Items tab of the Purchasing window, searching for a serial number would only find a single exact match even though it was supposed to be a Begins With type of search. It is now a Contains search and is working. [Build: 2.36]

 86. For HubSpot CRM users, API requests would timeout after an hour of inactivity. [Build: 2.36]

 87. For HubSpot CRM users, clearing a user's credentials and attempting to do a Contact search will display an error. [Build: 2.36]

 88. For Zoho CRM users, clearing a user's credentials and attempting to do a Contact search will display an error. [Build: 2.36]

 89. For QuoteValet users, when you opened a quote that was previously uploaded to QuoteValet, and changes were applied to the quote by the customer on QuoteValet, QuoteWerks saved those changes to the database, but did not update the CRM Sales Opportunity (if there was one). Now it will prompt you to update the CRM Sales Opportunity if the GrandTotal changes. [Build: 2.36]

 90. For Autotask users, when the "Complete Sales Opportunity from QuoteWerks" was set to Never, and a quote was opened that was previously uploaded to QuoteValet, that had a customer change options on QuoteValet, and then accepted, the changes would not be applied to the open Opportunity in Autotask. [Build: 2.36]

 91. If a user did not have MasterRights user and had the Access Right of "CannotModifyTemplates" set, and the user was doing a "New From Template" action and there was an auto recover document for this template from another user that did have the ability to modify templates, then when doing the "New From Template" action the user would receive an error like "QuoteWerks found a AutoRecover document for the document...However you do not have rights to MODIFY this TEMPLATE, so the AutoRecover document cannot be recovered by you.", and the user would not be able to complete the "New From Template" action. [Build: 2.36]

 92. When choosing Not to apply an AutoRecover document, and choosing to delete it, it was not getting deleted. [Build: 2.39]

 93. Line items from AutoRecover documents were appearing on the Purchasing tab of the Purchasing window. [Build: 2.39]

 94. For Hubspot CRM users, when using the DataLink to populate a HubSpot CRM custom number field, would receive the error "not a valid number". [Build: 2.39]

 95. When performing a "New from Template" action and the template is currently in use, you will no longer receive a "Open in ReadOnly mode" message, since the operation is just copying the data and putting it into the new document. [Build: 2.39]

 96. Open IceCat users would receive an HTTP Get Error: "Unauthorized". [Build: 2.40]