407-248-1481
QuoteWerks Turkey Logo - QuoteWerks Sales Quoting and Proposal Software - CPQ that integrates with leading CRM, PSA, and Accounting Solutions (ConnectWise, Autotask, QuickBooks, salesforce.com and more)
Request a Demo
Customer Area

QuoteWerks Update Center

Update Center home

Version 24.0 Summary
92 New, 113 Fixes, and 17 Miscellaneous features
New Features - Version 24.0
 1. Act! For Web 25.100 is now supported! [Build: 1.01]

 2. Goldmine 2023.4 is now supported! [Build: 1.01]

 3. SugarCRM version 13.2 is now supported! [Build: 1.01]

 4. Sage 50 Accounting 2024 (Peachtree) is now supported! [Build: 1.01]

 5. QuickBooks Desktop USA version 2024 is now supported! [Build: 1.01]

 6. USA Address verification is now supported. On the SoldTo/ShipTo tab of the Quote WorkBook there is now a button to verify and standardize the address using the US Postal Service database. On the Sales Tax tab of the Real-time Setup window there is the option "Show/Display USA address verification icon" to hide this feature if not wanted. The option is useful if you live in a country besides the USA like Canada. You may still ship and do business with customers in the USA, you can use this option to benefit from USA address verification even though your company is not located in the USA. On the Misc.General(more) tab of the Users Preferences window there is a "Address Verification Mode" option with the choices of "Manual" and "Auto Verify USA Address on Address selection". When an address is verified, it is logged in the document transaction log. The Realtime Module and current UMP is required for this feature. [Build: 1.01]

 7. The USA Sales Tax Rate Lookup in the Real-Time module has been improved. Now the the feature will verify the address against the USPS database, and refine the Postal Code to be a Zip+4 postal code (taking into account the street number and name). With this pinpointed Zip+4 Postal Code the Sales Tax Rates for that specific Zip+4 location will be retrieved. On the Sales Tax tab of the Real-time Setup window there is the option "Base Sales Tax on the Address From" to choose which address controls the sales tax rate. The standard is for the Ship To address to determine the tax rate locality. On the Misc.General(more) tab of the Users Preferences window there is a "Sales Tax Lookup Mode" option with the choices of "Manual", "Auto Verify USA Address and Retrieve Sales tax info on Address selection", and "Display Realtime USA Sales Tax Lookup window on Address selection". You can also click on the "Lookup tax rate" button next to the Tax Rate field on the Sale Info tab of the Quote Workbook, this will display a window that will let you choose to use the address verification and see the details of the Tax Information for the Zip+4 Postal Code. When a realtime Sales Tax is applied to the document, it is logged in the document transaction log. The Realtime Module and current UMP is required for this feature. [Build: 1.01]

See a screenshot/video of this feature

 8. Whole document spell check. Pressing the F7 key while in a text box will display the traditional spell check dialog. Choosing the Tools->Spelling menu (or CTRL-F7) will run the Whole Document Spell Check wizard. A wizard will be displayed that presents each field one by one indicating misspelled words with a red squiggly line underneath it. When done correcting the spelling, you can click the [Next] button to move to the next field. There is also a [Previous] button to go back if needed, or [Close] to stop. If you choose to [Ignore All], that word will be ignored in all the remaining fields checked. If a field is empty or there are no spelling errors, or the user does not have rights to modify the field, it will be skipped. The Whole Document Spellcheck can include fields on the Quote WorkBook tabs, and also line item columns for each line item. You can customize the list of fields that are included under the Spelling tab of the Tools->My Preferences menu. [Build: 1.01]

 9. You can now spell check individual cells on the Document Items tab grid by pressing F7 while in the cell. [Build: 1.01]

 10. QuoteWerks Web now supports SSO login. QuoteWerks Desktop user setup was updated to reflect this. [Build: 1.01]

 11. The Product Content Subscription now has PartLocator support for Arbitech in the USA. We've negotiated an arrangement with Arbitech to host their product data so as to provide our mutual customers with the best experience possible. [Build: 1.01]

 12. The Product Content Subscription now has PartLocator support for Accutech Data in the USA. We've negotiated an arrangement with Accutech Data to host their product data so as to provide our mutual customers with the best experience possible. [Build: 1.01]

 13. On the Product Lookup window, the Etilize keyword search box now has a drop-down list of your most 20 recent searches. [Build: 1.01]

 14. For the Deposit Amount, there is now an option to include the Sales Tax in the deposit amount when selecting the "TOTALING: Add up multiple matching line items in the document" or "Percent of a line item in the document" options. Defaults for this can be specified on the Documents tab of the Tools->Options menu. [Build: 1.01]

 15. For the Deposit Amount, there is now an option to "Include Shipping Amount (including Sales Tax) in Deposit Required". [Build: 1.01]

 16. The Summary line "TOTALING: Add up multiple matching line items in the document" option now has the option to "Include Sales Tax" [Build: 1.01]

 17. On the Custom Tab of Quote WorkBook, the fields CustomMemo01, CustomMemo02, CustomMemo03, and CustomMemo04 now have vertical scrollbars. [Build: 1.01]

 18. On the QuoteValet Upload window, next to the [Reminder Options] button is an indicator that displays how many reminders are set. [Build: 1.01]

See a screenshot/video of this feature

 19. The QuoteValet Auto-Reminders window now has [Select All] and [De-Select All] buttons [Build: 1.01]

See a screenshot/video of this feature

 20. Under the Tools->Options menu on the Print tab added options of "Include Percent Charge lines on Sales Orders" and "Include Percent Discount lines on Sales Orders" and "Include Group Header lines on Sales Orders". [Build: 1.01]

 21. For ConnectWise PSA users, QuoteWerks now supports up to 6 ConnectWise PSA Tax levels when using the DataLink to retrieve the tax rate from ConnectWise PSA. Previously, QuoteWerks only supported the first 5 levels. Note: The ConnectWise PSA API as of October 2023 only supports 6 Tax Levels. The ConnectWise UI allows administrators to create more than 6, however. [Build: 1.01]

 22. You can now select multiple bundles at the same time to delete. [Build: 1.02]

 23. For SugarCRM users, significant speed improvements were made across all API calls. [Build: 1.03]

 24. You can now specify company wide Spell Check words to Ignore. In the Settings Manager, you can set SystemSettings\System\SpellCheckCompanyCustomDictionaryData key with a list of words to ignore, with each word being on its own line, so separated by CRLF. [Build: 1.03]

 25. For Autotask users, the shipping description will now map over for shipping items on an Autotask quote. The shipping description can also be manually set. This new feature is located on Autotask Setup window -> Opportunities->Quote Products->Shipping section. [Build: 1.06]

 26. For Hubspot CRM users, if two words are entered when doing a Name search on the Lookup window, a match with the first word for the first name and the second word for the last name will be used. [Build: 1.06]

 27. For Zoho CRM users, product lookup can now show up to 10,000 records. [Build: 1.06]

 28. Act! For Web 25.2 is now supported! [Build: 1.08]

 29. Autotask 2024 is now supported! [Build: 1.08]

 30. SugarCRM 13.3 is now supported! [Build: 1.08]

 31. Goldmine version 2024.1 is now supported! [Build: 1.09]

 32. ConnectWise 2024.1 is now supported! [Build: 1.08]

 33. ConnectWise 2024.2 is now supported! [Build: 1.09]

 34. The USA Sales Tax Rate Lookup in the Real-Time module has been improved to now account for address locations that have not yet been assigned a Zip+4 code by the USPS yet. This can happen with new construction resulting in new addresses that have not been assigned a Zip+4 code yet by the United States Postal System. A list of Tax Jurisdictions for the base Postal Code for you to choose from will now be displayed when using the Prompt for Sales Tax option. If the option is set to not display the Sales tax Lookup window, then you will receive a message to use the window to choose the appropriate Sales Tax Jurisdiction. These options are set on the Misc.General (more) tab of the Tools->My Preferences menu. [Build: 2.04]

 35. The USA Sales Tax Rate Lookup in the Real-Time module has been improved to now account for USA address locations that cannot be verified by the USPS. A list of Tax Jurisdictions for the base Postal Code will now be displayed when using the Prompt for Sales Tax option for the user to manually intervene. If the option is set to not display the Sales tax Lookup window, then you will receive a message to use the window to choose the appropriate Sales Tax Jurisdiction. These options are set on the Misc.General (more) tab of the Tools->My Preferences menu. [Build: 2.04]

 36. The USA Sales Tax Rate Lookup in the Real-Time module has been improved to now account for address locations that cannot be verified by the USPS, like many addresses in Puerto Rico (a USA territory). Puerto Rico addresses use various non-standardized formats that the USPS API does not recognize. A list of Tax Jurisdictions for the base Postal Code will now be displayed when using the Prompt for Sales Tax option for the user to manually intervene. If the option is set to not display the Sales tax Lookup window, then you will receive a message to use the window to choose the appropriate Sales Tax Jurisdiction. These options are set on the Misc.General (more) tab of the Tools->My Preferences menu. [Build: 2.04]

 37. On Sales Tax Rate lookup window you can now it will default to the SoldTo/ShipTo/BillTo Address setup in options, but you can now choose the SoldTo/ShipTo, or BillTo address to do a validation and sales tax rate lookup based on any of those addresses. Useful if, for example, you are shipping your product to a shipping address that is a staging area (like your office location), but ultimately the final shipping address, and what the tax rate should be based on will be your Customer's address which is currently located in the SoldTo address fields. [Build: 2.04]

 38. When the USA Address verification is used the USPS returns the address standardized and formatted as all upper case letters. We now Proper Case the results. [Build: 2.04]

 39. For Ingram Micro Realtime users, added support for the Ingram Micro JSON API for Real-time P&A calls. The JSON API is self-service to create credentials via the following URL: https://developer.ingrammicro.com. This support has been added for Ingram Micro Customers in the United States, Canada, the United Kingdom, Australia, and New Zealand. Also added an option for Sandbox Mode. [Build: 2.04]

 40. For ConnectWise PSA Users, there is now a setup option that enables the QuoteWerks Admin to require fields when creating/Updating a ConnectWise PSA Opportunity. The fields that can be made mandatory are Opportunity Type, Description, Source, and Campaign. The ConnectWise Opportunity will not be able to be created/updated until the specified fields have data entered. The Required Fields can be specified on the Connectwise Setup->Opportunities Tab->Required Fields Sub Tab. [Build: 2.04]

 41. For QuickBooks Online Users, added a new setup option for "If the ShipTo Customer Does Not Exist" of 'Do not create - write in only' If this option is selected, then the Ship To Customer will be a "write in" on the document, which does not require that it exist as a customer record. This option adds to the existing options of 'Create' and 'Prompt to create'. [Build: 2.04]

 42. When editing a product definition, if you change an existing product's Manufacturer Part Number to another Manufacturer Part Number, it will now be checked to see if that newly entered/changed Manufacturer Part Number already exists in another product definition. [Build: 2.04]

 43. The DocumentItems Manufacturer field length was increased from 30 to 40 characters. [Build: 2.04]

 44. The User Properties window now has CreatedOn and LastModifiedOn fields. [Build: 2.04]

 45. When searching for contacts, if there is an error, it is no logged in the err.log file. Also the tooltip will be set on the status label enabling you to see more of a longer message. [Build: 2.04]

 46. SugarCRM 14.0 is now supported! [Build: 2.07]

 47. GoldMine 2024.2 is now supported! [Build: 2.07]

 48. QuoteValet Multiple Signature Support. In addition to the Primary Signature collected as part of Quote Acceptance, you can now require additional customer signatures. You can also configure one or more counter-signers composed of QuoteWerks users, groups, and/or third-party emails. The signature collection process can be configured for Sequential or Simultaneous capture, and all communication and signature capture is handled automatically. These options are set on the Upload to QuoteValet window. For existing customers that have directly customized the QuoteValet HTML or CSS template, the multiple signature features will not work until those customized templates have been updated with the multiple signature elements. [Build: 3.01]

 49. Multiple Contacts. You can now have more than one contact per company in the built-in QuoteWerks Contact Database. You can create and search for use these additional contacts in the quote. There are 4 primary search fields Company, Phone, Contact, Email. With Begins With, Contains, etc operators. You can filter on multiple things at the same time. The Phone search searches all the phone number fields across companies and contacts. There is also two "Other field" options to choose whatever other fields you might commonly search and the selections are remembered. If the labels for these fields were customized, the customized label will be shown. You can re-order the columns and set the column widths on the search results grid which will be remembered per user. The Data Manager, Management Reports, and DataLink features were updated to support the new two table system of CRMCompanies and CRMContacts. Professional or Corporate Edition is required for the Multiple Contacts feature. [Build: 3.01]

 50. The QuoteWerks built-in Contact Database contacts now have a Role, Reference, and Notes fields which are very useful for saving details about these contacts and their Role that are visible in the search results. [Build: 3.01]

 51. The Contact Import wizard was updated to support the new multiple contacts per company along with other improvements. When using the Contact Import Wizard you will only be able to import the first contact (primary contact) for a company. If you have data of companies that have more than one contact that you want to import, you can use the Data Manager to import this. [Build: 3.01]

 52. On the Contact Lookup window for the built-in QuoteWerks Contact Database, there is now a right click menu option of "Move...". You can use this to move a contact from one Company to another Company. If the Contact that you are moving is the only contact for the company, you be prompted to Delete the company record since a Company record cannot exist without at least one contact. If this is the case and you have the Misc Access right of "CannotDeleteContactRecord" you will not be able to proceed. Similarly, if you have the Misc Acccess right of "CannotModifyContactRecord", you will not be able to move the Contact. [Build: 3.01]

 53. The Contact import Wizard has been redesigned to use a two list mapping approach instead of the combobox drop downs for each field approach. Field Auto-Map, and field search features found in the Product Import Wizard were added. When selecting a QuoteWerks field for mapping, if that field label has been customized the customized label value will appear in a status area below the list. Also there is an option now to specify which line of data to start the import at. This is useful in excluding the first row of data typically that contains the column names and not data to be imported, yet useful to have in the file when doing the mapping of columns. Additionally more field delimiters than just comma and tab are now supported. [Build: 3.01]

 54. When using the Contact Import Wizard and choosing the option to "Delete all existing Companies/Contacts", there is a now a more pronounced dialog requiring you to type in the case sensitive word of "Delete" to proceed with the deletion of all Company/Contact records. [Build: 3.01]

 55. The Create new CRM contact feature for the built-in QuoteWerks Contact Database was updated. When creating the new company and contact record, it will copy the SoldToPrice Profile and Terms fields from the current quote into the newly created company record in QuoteWerks contact database. [Build: 3.01]

 56. Act! for Web version 26 is now supported! [Build: 3.01]

 57. Act! Desktop version 26 is now supported! [Build: 3.01]

 58. For HubSpot CRM users, there is a new option on the setup window of "[] When converting to order/invoice, and there is no existing deal, prompt to create a won deal." [Build: 3.01]

 59. For HubSpot CRM users, the HubSpot CRM Setup window now has a 'UserName Mappings' button for users to map QuoteWerks UserNames to HubSpot CRM UserNames. [Build: 3.01]

 60. For HubSpot CRM users, when retrieving the HubSpot CRM Deal ownername field using the DataLink and populating QuoteWerks PreparedBy or SalesRep field, the 'HubSpot CRM UserName Mappings' will map the HubSpot CRM UserName to the QuoteWerks user name. [Build: 3.01]

 61. For HubSpot CRM users, you can choose the default owner for a Deal in the HubSpot CRM Setup Window. The Owner can either be the logged in user or the Sales Rep. The Sales Rep name must match the HubSpot CRM user name to be selected. [Build: 3.01]

 62. UPS shipping integration was updated to support the new required REST integration method which will now require a Client ID and Client Secret. Effective August 5th, 2024 UPS will no longer support the old integration method. You can obtain these new credentials from UPS by going to https://developer.ups.com and creating a new "application". [Build: 3.01]

 63. FedEx shipping integration was updated to support the new required REST integration method which will now require an Account Number, API Key, and Secret key. Effective May 15th, 2024 FedEx no longer supports the old integration method. You can obtain these new credentials from FedEx by going to https://developer.fedex.com/ and creating a new API Project. [Build: 3.01]

 64. When importing vendors and choosing the option to "Delete all existing vendors", there is a now a more pronounced dialog requiring you to type in the case sensitive word of "Delete" to proceed with the deletion of all vendor records. [Build: 3.01]

 65. In the Vendor Import Wizard you can now specify which This is useful in excluding the first row of data typically that contains the column names and not data to be imported, yet useful to have in the file when doing the mapping of columns. of the data to start the import at. This is useful in excluding the first row of data typically that contains the column names and not data to be imported, yet useful to have in the file when doing the mapping of columns. [Build: 3.01]

 66. In the Product Import Wizard when selecting a QuoteWerks field for mapping, if that field label has been customized, the customized label value will appear in a status area below the list. [Build: 3.01]

 67. In the Product Import Wizard on the Basic Mappings Step, field label customizations will be displayed on this wizard step. [Build: 3.01]

 68. Added SoldToFax as a destination field in QuoteWerks in the DataLink mapping. [Build: 3.01]

 69. Added new macro "&APP_&OurLocationInlineAddress". [Build: 3.01]

 70. SugarCRM version 14.1 now supported! [Build: 3.02]

 71. Added new Misc Access Right "CannotUseQuoteWerksWebLicense" [Build: 3.02]

 72. For QuoteWerks built-in Contact Database users, improved the "Move Contact" feature to make it easier to use and handle different addresses better. To use this feature, now you can hold down the CTRL key and select multiple Contacts that you want to move to another company. The last Contact you select will be the company the other Contact selections are moved to. Important, only CTRL selecting will work, SHIFT selecting will cannot be used. Also, the "Company ID" column was added to help make it easier to understand which contacts are connected to which companies to help you with the Move Contact feature. Since individual Contacts can have different addresses than the main company record, additional logic was added to move the address with the Contact only if it was needed. [Build: 3.04]

 73. For QuoteWerks built-in Contact Database users, on the Contact Lookup window results grid, the results of the search are sorted to group all the resulting contacts that are from the same company together. Additionally, the first row for that Company is bolded to give you a visual indicator showing which contacts are from the same company since you can have company records with the same company name in the database. [Build: 3.04]

 74. For QuoteWerks built-in Contact Database users, added [Delete Company] button to the Edit Company window, and removed the Delete button from the Contact Lookup window. [Build: 3.04]

 75. For QuoteWerks built-in Contact Database users, on the Contact Lookup window, added right click menus of "New Company..." and "Edit Company...". [Build: 3.04]

 76. For QuoteWerks built-in Contact Database users, you can now Clone a contact. On the Edit Company window, on the list of Contacts added the right click menu "Clone..." and added a button [Clone]. [Build: 3.04]

 77. HaloPSA integration! The integration with HaloPSA includes the ability to search for clients, Users, create/update Opportunities, create/update Quotes and upload quote attachments to HaloPSA. DataLink is supported for Clients, Users, Opportunities, Quotes, LineItems, and incldues the ability to retrieve the aggregate Sales Tax Rate from HaloPSA. The HaloPSA Product Database is available as a Product Data Source. You can attach files to the HaloPSA Opportunity from the PDF Preview window, the Links tab, and the Print window. There is a button on the SoldTo/ShipTo tab to display the SoldToContact, ShipToContact, or BillToContact in HaloPSA, a link on the Links tab that you can click to view the HaloPSA Opportunity in HaloPSA, also there is a link on the tab to view the HaloPSA Quote in HaloPSA. Additionally, emails sent from QuoteWerks are logged in the HaloPSA Opportunity Progress tab. The Corporate Edition of QuoteWerks is required to integrate with HaloPSA. [Build: 4.10]

 78. GoldMine 2024.3 is now supported! [Build: 4.10]

 79. For QuoteValet users, the QuoteValet Setup window in QuoteWerks Desktop is now web-based and shared with QuoteWerks Web. This provides for a modern web interface with improvements, especially for setting up the QuoteValet Notifications. [Build: 4.10]

 80. For QuoteValet users, it is now possible to enable and configure DKIM for automated emails sent out from the QuoteValet notification service. Enabling this option will help to ensure proper email delivery when QuoteValet notifications are configured to originate from your company's domain name. [Build: 4.10]

 81. For Zoho CRM users, you can now create Deals for an Account that does not have any contacts. [Build: 4.10]

 82. For SQL users, especially Aspire Hosted DB customers, after making changes to users, or groups, or User Preferences on the User Maintenance window, or after changes to the QuoteValet Setup window, the speed of the synchronizing process with QuoteValet is massively improved. [Build: 4.10]

 83. For SQL users, especially Aspire Hosted DB customers, massive speed increase when clicking on the OK button on the User Preferences window, either from Tools->My Preferences or from the User Maintenance window. [Build: 4.10]

 84. For SQL users, especially Aspire Hosted DB customers, massive speed increase when clicking on the OK button on the Tools->Options window. Also when clicking OK on the Real-time Setup window. [Build: 4.10]

 85. For Hubspot CRM users, the files api was updated to version 3. [Build: 4.10]

 86. For Hubspot CRM users, data integrity changes were made for the upcoming Hubspot changes taking place January 6, 2025. [Build: 4.10]

 87. For QuoteWerks built-in Contact Database users, added the Address1 column on the Contacts tab of the Edit Company window. [Build: 4.10]

 88. For DataLink users, when creating a new DataLink Mapping, after selecting the action, the current CRM will now be automatically selected by default. [Build: 4.10]

 89. GoldMine 2024.4 is now supported! [Build: 4.12]

 90. For HaloPSA users, you can now select the ticket type on the Opportunity window. [Build: 4.16]

 91. For HaloPSA users, you can now select a default ticket type on the HaloPSA Settings window. [Build: 4.16]

 92. For HaloPSA users, selecting a ticket type will now only show the statuses available for that ticket type. [Build: 4.16]

Misc Features - Version 24.0
 1. QuoteWerks no longer supports "S" type Etilize Annual Subscription License Keys (which expire and need to be replaced annually). Starting with v24 QuoteWerks requires an Etilize Subscription using a Tenant Account. [Build: 1.01]

 2. New method implemented for saving line items resulting in significant speed increases. [Build: 1.01]

 3. The "SYNNEX" tab on the Real-time Setup window was renamed to "TD SYNNEX" to reflect their name change, and then further renamed to "TD SYNNEX North America" to reflect these settings are only for North America. [Build: 2.04]

 4. The Tech Data" tab on the Real-time Setup window was renamed to "TD SYNNEX Europe" to reflect the Tech Data API still being used for the new "TD SYNNEX" company for their locations in Europe. The region options of "USA" and "Canada" were removed. The Online Ordering setup options were removed from this tab as they were only available for USA and Canada. [Build: 2.04]

 5. References to "Computer 2000" distributor have been removed. [Build: 2.04]

 6. When hovering over the Address verification warning/error label under an address on the Sold To/Ship To tab you will now see details of the warning/error. [Build: 2.04]

 7. The [Export Contacts] button has been removed from the Contact Manager Setup for the QuoteWerks Contact Database. This action can be accomplished exporting from the Data Manager now. [Build: 3.01]

 8. Removed Tech Data Shopping Cart import from Paste Special. [Build: 3.01]

 9. The height of the Product import Wizard was increased to be able to see more mapped fields on the screen in the Advanced Mappings step. The width was also increased to better see the wider mapping selections. [Build: 3.01]

 10. For HubSpot CRM users, the owners api was updated to version 3. [Build: 3.01]

 11. Activated beta testing support for Act! for Web version 26. [Build: 3.01]

 12. Activated beta testing support for Act! Desktop version 26. [Build: 3.01]

 13. The Utilities->Change Registration Information menu was removed. This Change Registration Information window can now be accessed from the Company tab of Tools->Options menu. [Build: 3.01]

 14. The Setup Wizard now requires the Address1, City, State, and PostalCode fields. [Build: 3.01]

 15. For QuoteWerks built-in Contact Database users, removed the feature "As you type in the search value field, 2 seconds after you stop typing the search will auto execute." [Build: 3.04]

 16. Maximizer CRM Live (Web) integration has been removed from QuoteWerks Desktop. [Build: 4.10]

 17. Added more logging to the Build 4 QWContacts to CRMCompanies data conversion process. [Build: 4.10]

Fixes - Version 24.0
 1. The "QuoteWerks Web Multi-Factor Authentication method" options did not list the recently added "Authenticator" and "DUO". [Build: 1.01]

 2. If you have a C, J, or F primary License Key a tenant account based Real-time Module subscription would not be recognized. [Build: 1.01]

 3. For Maximizer Desktop users, when doing a search on the Contact Lookup window no columns would be displayed. This issue was introduced in v23 Build 5.00. [Build: 1.01]

 4. For API users, the qw.dll backend dll, when calling the .getfieldvalue("?") method would receive "Runtime error 94: Invalid Use of Null". This issue was introduced in v23 Build 1.00 [Build: 1.01]

 5. When importing values for the F2 Lookup, after the import, the list was reloaded without having been cleared first. [Build: 1.01]

 6. The Line Numbering options on the Print tab of the Tools->Options menu were not working. [Build: 1.01]

 7. For ConnectWise PSA users, QuoteWerks was not updating existing ConnectWise Activities. A new Activity would be created each time. [Build: 1.01]

 8. Since v23 build 2, when the Bundles window was re-designed, the ability to select multiple bundles at the same time to add to the quote was mistakenly removed. [Build: 1.01]

 9. On the Edit Product window the Cost/Price/List fields and the Foreign Cost/Price/List fields were not getting not getting truncated to the "Number Decimal Places Unit" setting on the Misc tab of Tools->Options menu. [Build: 1.01]

 10. When using Refresh with Latest pricing, and the item was based on Customer Based or Volume pricing, the resulting calculated UnitPrice was not getting truncated to the "Number Decimal Places Unit" setting on the Misc tab of Tools->Options menu. [Build: 1.01]

 11. For Autotask users, when searching for a contact, the sold/ship/bill will only populate with the company address despite the contact having a different address. [Build: 1.01]

 12. For Autotask users, text over 50 characters was being truncated when saving the Autotask Product Name. [Build: 1.01]

 13. When using the F2Lookup field through the setup window of Act Desktop, Autotask, Hubspot, MSCRM, Salesforce, SugarCRM, or Zoho: Editing a F2 Lookup field without using a QuoteWerks skin would cause an error. Editing a F2 Lookup field description would cause the error "The Lookup value name already exists in the list." Pressing the Delete button on the F2 Lookup window would close the window. Updating an existing field description would not update the value in the database. [Build: 1.01]

 14. Word document merging was not displaying text fields. [Build: 1.02]

 15. For API users, the qw.dll backend dll, when calling the .getfieldvalue("?") method would receive "An invalid Time Zone '', was encountered in ReturnTimeZoneOffsetFromUTCInMinutes". [Build: 1.02]

 16. When clicking on OK under Tools->My Preferences would receive error "Run-time error '91': Object variable or With block variable not set". [Build: 1.02]

 17. The GetSaveFile dialog Folder MRU now has a limit of saving the last 10 folders used. [Build: 1.02]

 18. For Autotask users, error when trying to edit the value of a description in the F2Lookup when editing the list in the Autotask Setup. [Build: 1.03]

 19. When saving a quote if the length of the data being saved was larger than the database field supports, would receive an error instead of being truncated. This was a result of the new line item saving method introduced in v24 Build 1. [Build: 1.03]

 20. When try to use an Amazon business pricing product from the Product Lookup window, would receive Type mistmatch error. [Build: 1.03]

 21. For Spell checking all Mixed case words were being ignored. [Build: 1.03]

 22. Error subscript out of range when clicking on the [Group Properties] button on the Edit bundle window. [Build: 1.04]

 23. When adding a bundle by double clicking on the list of bundles, QuoteWerks sometimes would quit unexpectedly. [Build: 1.04]

 24. For SugarCRM users, when trying to retrieve a datalink value would return Error: "FieldName" not found! [Build: 1.05]

 25. For Zoho CRM users, doing a contact lookup search ending in "\" would cause an error. [Build: 1.06]

 26. For Zoho CRM users, doing a contact lookup search with the word in parentheses would not return the result. [Build: 1.06]

 27. For Zoho CRM users, if more than 2000 results were found, a LIMIT_REACHED error would be shown. [Build: 1.06]

 28. For Zoho CRM users, doing a product lookup search with "Begins with" would cause an error. [Build: 1.06]

 29. For Zoho CRM users, doing a product lookup search on the Description field with "Contains" would return all the records. [Build: 1.06]

 30. CRM Login credentials would be removed for the current session, after using the SpellCheck feature. [Build: 1.06]

 31. Ignoring all words when spell checking an email would display a partially complete message instead of a complete message. [Build: 1.06]

 32. On the Purchase Orders tab of the Purchasing window, if you right clicked on a PO and select 'E-Mail PO Status to Customer(s)', the default template for this email contains macros for the &DH_DocNo and &DH_SoldToPONumber in the email's subject, however both rendered as "n/a". [Build: 1.06]

 33. On the Show Logged in users, when users were logged into QuoteWerks Web, the information would not be displayed correctly on this window. [Build: 1.08]

 34. On the User properties window, the "QuoteWerks Web Login (selected in QWW UI)" frame on the Login tab was not display the information correctly. [Build: 1.08]

 35. For Zoho CRM users, some users were receiving "invalid query formed" errors when using the Zoho CRM Product Lookup. [Build: 1.10]

 36. For SugarCRM users, some custom Lost and Won Opportunity Stages were not showing for users. [Build: 1.10]

 37. Spell Check was not correcting a misspelled word after pressing the change button. [Build: 1.10]

 38. When double byte characters were encountered in various CRM product data sources would result in error like "Error in RecordsetSetTextValue for field 'Description' Error (-2147217887) Multiple-step operation generated errors. Check each status value.". , Zoho QuickBooks Desktop, QuickBooks Online, salesforce, Peachtree, ConnectWise, Autotask, Kaseya BMS, Amazon Product Content [Build: 2.04]

 39. For Autotask users, the '<Existing Autotask Opportunity Category>' settings on the Autotask Setup -> Opportunity Setup window was not being applied when an existing opportunity was being selected from Autotask on the Opportunity window. [Build: 2.04]

 40. For Autotask users, the name field was not being searched when doing a Manufacturer Part Number search on the Product Lookup window. Now both the name field and the Manufacturer Part Number fields are being searched. [Build: 2.04]

 41. For Zoho CRM users, the session token would become invalid after an hour of inactivity. [Build: 2.04]

 42. On the Menus tab of the User Properties window, the "Tools->Spelling..." menu was renamed to "Tools->Whole Document Spell Check..." to reflect the change in the previous build. [Build: 2.04]

 43. For Zoho CRM users, doing a product lookup search by Manufacturer caused an error. [Build: 2.04]

 44. For a Payments Management Report, when attempting to add a field to the report would receive an error relating to "ReturnREFieldType()" and could also receive errors running the report. [Build: 2.04]

 45. When applying a licensing Redemption Code for an Edition Upgrade, License Relinquishment, or License Transfer, the associated Tenant account now will be branded with the new primary license and seed number, eliminating the need to contact Tech Support for a "branding" issue. [Build: 2.04]

 46. If on the last row in the Document Items grid and there are more rows than can be visible on the screen and you are on the last row and you type a value in a cell and press ENTER, the change would not take effect. [Build: 2.04]

 47. For Zoho CRM users, if the CreatedBy or ModifiedBy fields were removed from the Zoho CRM Account module, users would receive an error on the Lookup Zoho CRM contact window. [Build: 2.04]

 48. Under the Tools->My Preferences on the E-Mail.Sending tab the "Auto spell-check before sending e-mail" settings was not being saved. [Build: 2.04]

 49. When on the Print window for a quote that has a Spec Sheet or File Links, if you press the X on the upper right of the form instead of the [Close] button, the next time the Print window is displayed, the Spec Sheet from the previous quote would still appear. [Build: 2.04]

 50. On the Print tab of the Tools->Options menu the setting "Include Group Header lines of Sales Orders" was not being respected. [Build: 2.04]

 51. For QuickBooks Desktop users, when exporting Estimates to QuickBooks Desktop from QuoteWerks the ShipToAddress will now be populated. [Build: 2.04]

 52. On the Print window, when selecting Cover Page, Primary Layout, Additional Layout, Literature, Spec Sheets, or File Links, it will now insert these element types per the Print Order specified on the Print tab under the Tools->Options menu. [Build: 2.04]

 53. Whole Document Spell Check would freeze when clicking the [Previous] button in certain circumstances, also Spell Check was not correctly signaling the previous button was pressed in certain situations. [Build: 2.04]

 54. For Ingram Micro users that have not configured the integration for JSON, XML Pricing and Availability requests to Ingram Micro would fail. [Build: 2.06]

 55. For Peachtree users, when choosing on the Mappings tab under the Peachtree Interactive Link Setup, the "Convert grouped items to single item" option was not working. [Build: 3.01]

 56. When setting a default for the DocDueDate on the Documents.General tab under Tools->Options, a time portion was getting added to the DocDueDate. [Build: 3.01]

 57. On the File Saved Dialog, the [Open containing folder] button would not work if there were commas in the folder path. [Build: 3.01]

 58. For TD SYNNEX online ordering users, for the 'End User Details' and 'Reseller Details' the Fax Number is no longer a required field. [Build: 3.01]

 59. For QuickBooks Online users the "/" character is now supported for an item name. [Build: 3.01]

 60. For Hubspot CRM users, when doing a Merge Document Transport Files, users would receive a 404 error message. [Build: 3.01]

 61. On the Accounting tab of the Tools->Options menu, the "Default 'Export to' on Create PO window" option was not being applied on the Create PO window. [Build: 3.01]

 62. For Goldmine users, when e-mailing a PO, and choosing the "Under e-mail Recipient contact" option, the email was not being logged under the GoldMine History tab. [Build: 3.01]

 63. The Compare Prices vendor selection window still had "SYNNEX" instead of "TD SYNNEX". -Fix For Office 365 email users, the original OAuth keys required for the Office 365 email integration expired and have now been updated. [Build: 3.01]

 64. For Ingram Micro JSON users, would receive the following error when attempting to retrieve Realtime Pricing: "Unknown iError '200' in ReturnRealtimeErrorDescription()." This was due to a change in the results from Ingram Micro where Booleans could be Nullable. [Build: 3.01]

 65. Error QuoteWerks trapped Error (-2147217900) Invalid column name 'PriceProfile' when using the feature from the SoldTo/ShipTo tab to create a new Company/Contact in the QuoteWerks Contact Database. [Build: 3.01]

 66. When attempting to authenticate with Office 365, users would receive a 'could not load assembly' error message. [Build: 3.01]

 67. For SugarCRM users, when converting to order, the stage is not being automatically set to Closed Won. [Build: 3.02]

 68. For SugarCRM users, blank stage names could be being shown. [Build: 3.02]

 69. When selecting a Contact from the QuoteWerks built-in Contact Database, the Price Profile was not getting copied to the Quote. [Build: 3.02]

 70. The AccountRep column was missing from the Contact Lookup grid when searching for a Contact in the QuoteWerks built-in Contact Database. [Build: 3.02]

 71. When closing QuoteWerks would receive error "Access DB maintenance error" that the SITE.MDB file could not be compacted. [Build: 3.02]

 72. UPS shipping integration would return different result formats causing error. [Build: 3.02]

 73. For QuoteWerks built-in Contact Database users, when setting a Contact as the Primary Contact for a New contact would receive error about missing 'Companies' table. [Build: 3.04]

 74. For QuoteWerks built-in Contact Database users, when setting up a DataLink the PriceProfile and AccountRep fields were incorrectly displayed as being Company fields when in fact they are Contact fields. [Build: 4.10]

 75. For QuickBooks Online Users with the Global version of QuickBooks Online, if shipping was taxable in QuoteWerks when sending a document to QuickBooks, an error would be returned "Business Validation Error: Select a tax code for the shipping line." and the document would not be created in QuickBooks Online. [Build: 4.10]

 76. For Zoho CRM users, creating a Deal with a contact without an account would cause an invalid query formed error. [Build: 4.10]

 77. For Act for Web! users, creating an opportunity would cause an Object Reference Error if the "Opportunity Competitors" datatype was changed in the Act for Web! settings. [Build: 4.10]

 78. For Autotask users, having a custom field on the Autotask Services and performing a Product Lookup search would cause an Object doesn't support this property or method error message. [Build: 4.10]

 79. For Product Content Subscribers, using TD SYNNEX Europe, the "TD SYNNEX" distributor pricing option was not appearing in the Etilize Panel. [Build: 4.10]

 80. For UPS users, the production url was not being used for retrieving the shipping rates. [Build: 4.10]

 81. When changing the value, and pressing enter in a the unit cost cell on the Document Items grid, and you were on the last row of the grid, and the Item Cost Assistant was configured to display, would receive an error about a modal window. [Build: 4.10]

 82. For QuoteWerks Built-in Contact Database users, when clicking on the Contact Search Button and moving the "P" / Primary Contact designator column on the lookup to the first position, closing the search window, and searching again, will receive a Run Time Error '35604' - "The first column in a ListLiewControl must be left aligned." QuoteWerks then terminates. [Build: 4.10]

 83. For QuoteValet users, when the logged in user is uploading a quote that has a different Sales Rep than the logged in user to QuoteValet would receive error "Error in GetUserDoubleVar, Array user 'XXXXX' does not match user 'YYYYY' requested!" [Build: 4.10]

 84. For QuoteWerks Built-in Contact Database users, when cloning a contact on the Edit Company window, the list of contacts would not be refreshed to show the newly cloned contact. [Build: 4.10]

 85. For API users, using the DocFunctions.SetDocumentHeaderValue method to set "LocalTaxRate" or "GSTTaxRate" was not recalculating the tax. [Build: 4.10]

 86. QuoteValet Activity Email Notifications were setup with CC and BCC entries but the notifications were not being sent. [Build: 4.10]

 87. When dbl-clicking on a Bundle in the Bundles window to add the bundle to the quote, if the Bundle contained items from external sources like ConnectWise the Bundle Items display was still loading when the dbl-click was received causing QuoteWerks to terminate. [Build: 4.10]

 88. When clicking on a Bundle in the Bundles window, the list of Bundle Items was getting loaded twice. [Build: 4.10]

 89. When creating a new Bundle or Configuration would receive an error about ""You can only Edit one bundle/configuration at a time". [Build: 4.10]

 90. When clicking on the File->Print menu, and there was no Tenant Account Number would receive error "Error in InitializeOrUseCloudSettings. This requires an Aspire Tenant Account and Password" [Build: 4.12]

 91. For QuickBooks Online Integration subscribers, when exporting an item to a QuickBooks Online Document where the mapping for Description and Purchasing Description were the same field, the Purchasing Description would be blank. [Build: 4.12]

 92. For QuickBooks Online Integration subscribers, Document Header macros for CustomerText01 - CustomText28 would return empty values. [Build: 4.12]

 93. For HaloPSA users, when doing a Contact Lookup search certain Clients or Users could return an error. [Build: 4.12]

 94. For HaloPSA users, the Team value was not being set when creating an Opportunity. [Build: 4.12]

 95. For HaloPSA users, some users with HaloPSA On-Premise would receive a HaloPSA failed authentication message after entering their credentials and clicking Test Connection on the HaloPSA Setup window. [Build: 4.12]

 96. For HaloPSA users, if the QuoteWerks Logged in User setting was set for the Default Record Owner, the QuoteWerks logged in user was not correctly mapping the HaloPSA user. [Build: 4.16]

 97. For HaloPSA users, DataLink fields are now sorted alphabetically with custom fields added at the bottom. [Build: 4.16]

 98. For HaloPSA users, DataLink fields are now sorted alphabetically with custom fields added at the bottom. [Build: 4.16]

 99. For HaloPSA users, the Macro Tester feature found under Contacts -> Macro Tester is now working. [Build: 4.16]

 100. For HaloPSA users, DataLink fields were updated for Clients to include the current list of available fields from the HaloPSA Api. [Build: 4.16]

 101. For HaloPSA users, Quotes were not able to be created due to a HaloPSA API issue. [Build: 4.16]

 102. For HaloPSA users, date fields Quotes were not able to be created due to a HaloPSA API issue. [Build: 4.16]

 103. For HaloPSA users, when saving a Quote a second time, if your Windows PC date is set to dd/mm/yyyy, the date is being shown in the format as mm/dd/yyyy. [Build: 4.16]

 104. For MS CRM users, if the QuoteWerks Logged in User setting was set for the Default Record Owner, the QuoteWerks logged in user was not correctly mapping the MS CRM user. [Build: 4.16]

 105. For Hubspot CRM users, if the QuoteWerks Logged in User setting was set for the Default Record Owner, the QuoteWerks logged in user was not correctly mapping the Hubspot CRM user. [Build: 4.16]

 106. For HaloPSA users, some users were receiving a security protocol is not supported error message when selecting HaloPSA from the Contact Manager Setup window. [Build: 4.16]

 107. For HaloPSA users, some ticket types were not being shown. You can now select the Opportunity ticket type among others now added as a default Ticket Type option on the HaloPSA Setup window and the Opportunity window. [Build: 4.16]

 108. For HaloPSA users, unlinking an existing Opportunity on the Opportunity window would not show the new Opportunity textbox. [Build: 4.16]

 109. For HaloPSA users, some DataLink types were not returning a value such as drop down lists. [Build: 4.16]

 110. For Hubspot CRM users, custom fields with data values that had currency symbols were returning 0. [Build: 4.16]

 111. For HaloPSA users, existing Opportunities were showing 0 on the probability field on the Opportunity form. [Build: 4.16]

 112. For HaloPSA users, custom fields with data values that had currency symbols were returning 0. [Build: 4.16]

 113. Would receive error in SystemSetting_GetEx(), SectionName='HubSpotCRM UserName Mappings',KeyName='' You must specify SectionName, AND KeyName values!, when using a CRM integration that had a DefaultRecordOwner option. [Build: 4.16]

  •            
©1993-2024 Aspire Technologies, Inc.
    407-248-1481 (9am-5pm ET M-F)