407-248-1481
QuoteWerks Update Center
example: QuoteValet "payment option" -deposit
Version 5.6 Build 5.12 Summary
Version 5.6 Build 5.12 Summary
9 New, 11 Fixes, and 6 Miscellaneous features Released on 08/24/2021 View all features/fixes from all builds of version 5.6 Download (96.1 MB) See a video showcasing the new features. | ||
New Features - Build 5 | ||
1. Product Import templates are no longer saved as .pit files. The .pit data is now stored in the SystemSettings table under the SectionName="Product Import Templates". Each template will now be stored under the KeyName equal to what the .pit file base name used to be. Also, the import log will no longer be written out as a .log file, instead a new EventViewer record will be written under the category of "ProductImport". This .log file would be replaced on each successive import. An advantage of this new change is that every time the product import is run, it saves and preserves the import log for every time an import is run and the import log will contain a list of all the settings used in the import. If you used the command line option like /i:"ACME Product Inventory.pit", you will still need to include the ".pit" postfix at the end of the template name. When the import templates used to be files, you could simply copy the file to another installation if needed. With the changes you will need to go into the Settings Manager and right click on an import template and choose Copy SET command. For more details see the documentation on the Settings Manager. [Service Release: 5.10] | ||
2. Contact Import templates are no longer saved as .cit files. The .cit data is now stored in the SystemSettings table under the SectionName="Contact Import Templates". Each template will now be stored under the KeyName equal to what the .cit file base name used to be. Also, the import log will no longer be written out as a .log file, instead a new EventViewer record will be written under the category of "ContactImport". This .log file would be replaced on each successive import. An advantage of this new change is that every time the contact import is run, it saves and preserves the import log for every time an import is run and the import log will contain a list of all the settings used in the import. If you used the command line option like /i:"New Customers.cit", you will still need to include the ".cit" postfix at the end of the template name. When the import templates used to be files, you could simply copy the file to another installation if needed. With the changes you will need to go into the Settings Manager and right click on an import template and choose Copy SET command. For more details see the documentation on the Settings Manager. [Service Release: 5.10] | ||
3. Vendor Import templates are no longer saved as .vit files. The .vit data is now stored in the SystemSettings table under the SectionName="Vendor Import Templates". Each template will now be stored under the KeyName equal to what the .vit file base name used to be. Also, the import log will no longer be written out as a .log file, instead a new EventViewer record will be written under the category of "VendorImport". This .log file would be replaced on each successive import. An advantage of this new change is that every time the vendor import is run, it saves and preserves the import log for every time an import is run and the import log will contain a list of all the settings used in the import. If you used the command line option like /i:"Updated Vendors.vit", you will still need to include the ".vit" postfix at the end of the template name. When the import templates used to be files, you could simply copy the file to another installation if needed. With the changes you will need to go into the Settings Manager and right click on an import template and choose Copy SET command. For more details see the documentation on the Settings Manager. [Service Release: 5.10] | ||
4. Paste Special templates are no longer saved as .qii files. The .qii data is now stored in the SystemSettings table under the SectionName="Paste Special Templates". Each template will now be stored under the KeyName equal to what the .qii file base name used to be. When the paste special templates used to be files, you could simply copy the file to another installation if needed. With the changes you will need to go into the Settings Manager and right click on an template and choose Copy SET command. For more details see the documentation on the Settings Manager. [Service Release: 5.10] | ||
5. Synchronization Profiles are no longer saved as .qsp files. The .qsp data is now stored in the SiteSettings table under the SectionName="Synchronization Profiles". Each profile will now be stored under the KeyName equal to what the .qsp file base name used to be. If you used the command line option like /sync:"Chicago Sync Profile.qsp", you should no longer include the ".qsp" postfix at the end of the profile name, but for backwards compatibility, if you do, it will still work. When the synchronization profiles used to be files, you could simply copy the file to another installation if needed. With the changes you will need to go into the Settings Manager and right click on a synchronization profile and choose Copy SET command. For more details see the documentation on the Settings Manager.
[Service Release: 5.10] | ||
6. SugarCRM 11.1 is now supported! [Service Release: 5.10] | ||
7. Act! v24 is now supported! [Service Release: 5.10] | ||
8. Sage 50 Accounting 2022 (Peachtree) is now supported! [Service Release: 5.12] | ||
9. Act for Web v24 is now supported!
[Service Release: 5.12] | ||
Misc Features - Build 5 | ||
1. There is now an [Event Viewer] button under the Utilities->View Logs window [Service Release: 5.10] | ||
2. SYNNEX moved/renamed one of their warehouses from Grove City, OH to Columnbus, OH. Applied necessary changes. [Service Release: 5.10] | ||
3. Activated beta testing support for Sage 50 Accounting 2022 (Peachtree) [Service Release: 5.10] | ||
4. On the Send Email window, when selecting a file to attach, the file name and path were being forced to lower case characters. [Service Release: 5.10] | ||
5. Activated beta testing support for ACT! for Web version 24. [Service Release: 5.12] | ||
6. The Act installer helper GetAct64bitInfo.exe is now only installed when the user chooses to install Act.
[Service Release: 5.12] | ||
Fixes - Build 5 | ||
1. Divide by 0 error when using the Group Header Price override feature by manually changing the UnitPrice of the Group Header line and any of the group members had a quantity of 0. [Service Release: 5.10] | ||
2. For MS CRM users, if an existing quote was deleted in MS CRM, QuoteWerks would error when a user tried to re-save instead of creating a brand new one. [Service Release: 5.10] | ||
3. InUseDocuments tracking between QuoteWerks Desktop and QuoteWerks Web. [Service Release: 5.10] | ||
4. In the File->Print window, when selecting [Save as PDF] the "Make PDF Ready Only" and "Add To File Links" options were missing. [Service Release: 5.10] | ||
5. When loading the purchasing window received error "VendorSourcing" field not found. [Service Release: 5.10] | ||
6. when placing an Online Order from the Purchasing Window, in the dropdown that allows a user to select from a list of addresses to use, the dropdown list was not populating with the ship to addresses, only the 'Our Location' was being loaded. [Service Release: 5.10] | ||
7. Click the Configurator button. Select an existing configuration, click Edit, Click the Flowchart tab, Select an existing selection container, Right click the selection container, click Properties, Click the Items tab, Click the X on the upper right hand side. QuoteWerks would quit unexpectedly. [Service Release: 5.10] | ||
8. For HubSpot CRM users, the deal pipeline combobox was disabled on the Setup and Deal window for the free tier HubSpot CRM accounts. [Service Release: 5.10] | ||
9. When using the Add Item Assistant to add an item that had a required item and if that required item had the "[] Link quantity to parent" option set, and the initial quantity of the main item was more than 1, when the required item was added to the quote, its linked child quantity would not be correct. Additionally if the required item of the required item had the "[] Link quantity to parent" option set, its linked child quantity would not be correct. [Service Release: 5.10] | ||
10. For SQL backend users, when importing large numbers of products into a product database with the Update option, the SQL transaction log would grow very large. [Service Release: 5.12] | ||
11. For SugarCRM users, when doing datalinking, error messages about unrelated datafields could appear. [Service Release: 5.12] |
©1993-2024 Aspire Technologies, Inc.
407-248-1481 (9am-5pm ET M-F)
Please Wait...