407-248-1481
QuoteWerks Update Center
example: QuoteValet "payment option" -deposit
Version 25. Build 2.07 Summary
Version 25. Build 2.07 Summary
8 New, 24 Fixes, and 2 Miscellaneous features Released on 03/12/2025 View all features/fixes from all builds of version 25. ![]() | ||
New Features - Build 2 | ||
1. For HaloPSA users, when creating a new product, the supplier will now be created if it does not exist. [Service Release: 2.02] | ||
2. For HaloPSA users, when creating a new product, the manufacturer will now be created if it does not exist. [Service Release: 2.02] | ||
3. Now the discount price modifier supports values from -1000 to + 100, so effectively a D-34 adds 34% to the list price in order to arrive at the unit price. Previously was D-99 to D100. [Service Release: 2.02] | ||
4. For HaloPSA users, the HaloPSA Product Source now has a mappable TaxCode field. [Service Release: 2.07] | ||
5. For HaloPSA users, Canadian HaloPSA users can now set the default TaxCode (GST, PST, BOTH) if an Item is taxable. [Service Release: 2.07] | ||
6. For Autotask users, the contact lookup process now operates at a significantly faster pace. We've optimized the search functionality by leveraging advanced multithreading and a robust caching system, ensuring a smoother and more responsive user experience. [Service Release: 2.07] | ||
7. For Autotask users, a status message now appears while QuoteItems are being added, providing clear, real-time updates on the process. [Service Release: 2.07] | ||
8. For Maximizer desktop users, saving the quote with a linked document is faster.
[Service Release: 2.07] | ||
Misc Features - Build 2 | ||
1. The folowing fields were removed from the database: DocumentItems.TaxRate, DocumentItems.SerialNumber, and DocumentItems.CMOppRecID. [Service Release: 2.02] | ||
2. On the Layout Designer window, there is now a link "Click to view documentation and videos on how to use the layout designer".
[Service Release: 2.07] | ||
Fixes - Build 2 | ||
1. For Goldmine users, when the option "When printing purchase orders, retrieve vendor information from GoldMine" was set, and from the Print window choosing a Purchase Order layout and choosing the option to "Create PO for each vendor", and choosing to Email the document, the email address from the GoldMine record was not populating in the Send Email window. [Service Release: 2.02] | ||
2. For users of both QuoteWerks Desktop and QuoteWerks Web, in certain scenarios, the file synchronization was not working and would cause QuoteWerks Desktop to terminate unexpectedly. [Service Release: 2.02] | ||
3. For HaloPSA users, resolved an issue where, upon re-saving a quote linked to an existing HaloPSA Opportunity, the Opportunity name was incorrectly overwritten with the QuoteWerks Document name, even when the "Update HaloPSA Opportunity Name with Document Name" option was disabled. With this fix, re-saving an existing HaloPSA Opportunity will now preserve the originally designated Opportunity name. [Service Release: 2.07] | ||
4. For HaloPSA users, resolved an issue where the DataLinking of a Tax Code field would not show the correct value. [Service Release: 2.07] | ||
5. For MS CRM users, resolved an issue where, upon re-saving a quote linked to an existing MS CRM Opportunity, the Opportunity name was incorrectly overwritten with the QuoteWerks Document name, even when the "Update MS CRM Opportunity Name with Document Name" option was disabled. With this fix, re-saving an existing MS CRM Opportunity in will now preserve the originally designated Opportunity name. [Service Release: 2.07] | ||
6. For MS CRM users, resolved an issue where, upon saving a second (or subsequent) time to an existing MS CRM Opportunity, an intermittent error referencing mismatched HTML tags would appear. [Service Release: 2.07] | ||
7. For salesforce.com users, resolved an issue where, upon re-saving a quote linked to an existing salesforce.com Opportunity, the Opportunity name was incorrectly overwritten with the QuoteWerks Document name, even when the "Update salesforce.com Opportunity Name with Document Name" option was disabled. With this fix, re-saving an existing salesforce.com Opportunity will now preserve the originally designated Opportunity name.
[Service Release: 2.07] | ||
8. For Hubspot CRM users, resolved an issue where, upon re-saving a quote linked to an existing Hubspot CRM Deal, the Deal name was incorrectly overwritten with the QuoteWerks Document name, even when the "Update Hubspot CRM Deal Name with Document Name" option was disabled. With this fix, re-saving an existing Hubspot CRM Deal will now preserve the originally designated Deal name. [Service Release: 2.07] | ||
9. For Zoho CRM users, resolved an issue where, upon re-saving a quote linked to an existing Zoho CRM Deal, the Deal name was incorrectly overwritten with the QuoteWerks Document name, even when the "Update Zoho CRM Deal Name with Document Name" option was disabled. With this fix, re-saving an existing Zoho CRM Deal will now preserve the originally designated Deal name. [Service Release: 2.07] | ||
10. For SugarCRM users, resolved an issue where, upon re-saving a quote linked to an existing SugarCRM Opportunity, the Opportunity name was incorrectly overwritten with the QuoteWerks Document name, even when the "Update SugarCRM Opportunity Name with Document Name" option was disabled. With this fix, re-saving an existing SugarCRM Opportunity will now preserve the originally designated Opportunity name. [Service Release: 2.07] | ||
11. Using Data Manager to Export Contacts to Empty DataSet File with Basic Columns would error referencing AccountRep field. [Service Release: 2.07] | ||
12. When clicking on the [View QuoteValet Users] button under the Utilities > Show Logged In Users menu, the list of users currently using QuoteValet would be truncated.
[Service Release: 2.07] | ||
13. For Autotask users, when a remote user downloaded a DTF file, the Autotask Opportunity RecID, Quote RecID, and Call RecID would be missing. Also in certain scenarios saving the quote while writing to the CRM is faster. [Service Release: 2.07] | ||
14. For ConnectWise Manage users, when a remote user downloaded a DTF file, the ConnectWise Manage Opportunity RecID, and Call RecID would be missing. Also in certain scenarios saving the quote while writing to the CRM is faster.
[Service Release: 2.07] | ||
15. For Halo PSA users, when a remote user downloaded a DTF file, the Halo PSA Opportunity RecID, and Quote RecID would be missing. Also in certain scenarios saving the quote while writing to the CRM is faster. [Service Release: 2.07] | ||
16. For salesforce.com users, when a remote user downloaded a DTF file, the salesforce.com Opportunity RecID, and Call RecID would be missing. Also in certain scenarios saving the quote while writing to the CRM is faster. [Service Release: 2.07] | ||
17. For SugarCRM users, when a remote user downloaded a DTF file, the SugarCRM Opportunity RecID, and Call RecID would be missing. Also in certain scenarios saving the quote while writing to the CRM is faster. [Service Release: 2.07] | ||
18. For MSCRM users, when a remote user downloaded a DTF file, the MSCRM Opportunity RecID, and Call RecID would be missing. Also in certain scenarios saving the quote while writing to the CRM is faster. [Service Release: 2.07] | ||
19. For Kaseya BMS users, when a remote user downloaded a DTF file, the Kaseya BMS Opportunity RecID, and Call RecID would be missing. Also in certain scenarios saving the quote while writing to the CRM is faster. [Service Release: 2.07] | ||
20. For Act! for Web users, when a remote user downloaded a DTF file, the Act! for Web Opportunity RecID, Call RecID, Meeting RecID, and TODO RecID would be missing. Also in certain scenarios saving the quote while writing to the CRM is faster. [Service Release: 2.07] | ||
21. For Act! Desktop users, when a remote user downloaded a DTF file, the Act! Opportunity RecID, Call RecID, Meeting RecID, and TODO RecID would be missing. Also in certain scenarios saving the quote while writing to the CRM is faster.
[Service Release: 2.07] | ||
22. For Zoho CRM users, when a remote user downloaded a DTF file, the Zoho CRM Opportunity RecID, Quote RecID, and Call RecID would be missing. Also in certain scenarios saving the quote while writing to the CRM is faster.
[Service Release: 2.07] | ||
23. For HubSpot CRM users, when a remote user downloaded a DTF file, the HubSpot CRM Opportunity RecID would be missing. Also in certain scenarios saving the quote while writing to the CRM is faster. [Service Release: 2.07] | ||
24. On the Edit Contact window of the built-in QuoteWerks Contact Database, double clicking in the Account Rep field did not bring up the F2Lookup. [Service Release: 2.07] |
©1993-2025 Aspire Technologies, Inc.
407-248-1481 (9am-5pm ET M-F)
Please Wait...