407-248-1481
QuoteWerks Update Center
example: QuoteValet "payment option" -deposit
Version 5.2 Build 8.25 Summary
Version 5.2 Build 8.25 Summary
25 New, 35 Fixes, and 8 Miscellaneous features Released on 07/11/2017 View all features/fixes from all builds of version 5.2 Download (115 MB) See a video showcasing the new features. | ||
New Features - Build 8 | ||
1. QuickBooks Online Integration! Use QuickBooks Online Customer Information in your quote. Add QuickBooks Online product items to your quote. Create new QuickBooks Online customers, items, estimates, invoices, sales receipts, purchase orders, and more. The QuickBooks Online integration requires QuoteWerks Professional or Corporate Edition and requires a monthly or annual subscription. [Service Release: 8.12] | ||
2. For QuoteValet users, YouTube video support! With your QuoteValet quote you can now include one or more videos to be displayed on the QuoteValet quote. You can even set one of them to start auto-playing as soon as the QuoteValet page is displayed. You can also include one video per line item. You can specify the default video(s) you would like each new Quote, Order or Invoice to include on the General tab of the QuoteValet setup window. You can also specify one video in a native database product definition which will be included in the quote for the line item when the product is added into the quote. You can see the video details for the line item in the quote by selecting the line item and clicking on the "Show/Hide Picture Panel" toolbar button above the line items grid. When adding videos to the quote, if you have setup your YouTube account information on the General tab of the QuoteValet setup, you will be able to choose from a list of all your existing videos that have already been uploaded to YouTube. If you are using a shared standardized QuoteValet template the videos will automatically just appear in the QuoteValet page. If you are using a customized QuoteValet template you will need to make some modifications to your customized template. The layout designer fields and macros of &DH_&Video1_URL, &DH_&Video1_Title, &DH_&Video2_URL, &DH_&Video2_Title, &DH_&Video3_URL, &DH_&Video3_Title, and &DI_&Video1_URL, &DI_&Video1_Title have also been added. [Service Release: 8.12] | ||
3. For QuoteValet users, you can now have more than one QuoteValet OrderForm Template used by the QuoteValet Shopping Cart. When uploading the OrderForm Template to QuoteValet you can choose which OrderForm template you want to use. [Service Release: 8.12] | ||
4. Windows Authentication Login support. You can now setup QuoteWerks users to use their Windows Authentication to automatically log into QuoteWerks without having to enter the QuoteWerks Native Login UserName and Password on the QuoteWerks Login window. Windows Authentication only works with domains. When using the Windows Authentication Login, you will still need to set a password for the QuoteWerks Native Login. Holding the SHIFT key down while starting QuoteWerks will force the QuoteWerks Login window to appear. [Service Release: 8.12] | ||
5. ConnectWise 2017.5 is now supported! [Service Release: 8.12] | ||
6. The Product Content Subscription now has PartLocator support for D&H Canada. We've negotiated an arrangement with D&H Canada to host their parts list to provide our mutual customers with a better ability to locate D&H Canada part numbers when quoting. [Service Release: 8.12] | ||
7. The Product Content Subscription now has PartLocator support for Jenne (USA). We've negotiated an arrangement with Jenne to host their parts list to provide our mutual customers with a better ability to locate Jenne part numbers when quoting. Now, on the Etilize panel, a Jenne option will only appear if the Jenne part number was found by the PartLocator. Previously the Jenne option would always appear even if a part number was not offeered by Jenne. [Service Release: 8.12] | ||
8. For Jenne customers with the Product Content Subscription, Jenne items will now appear in the Etilize Comparison Window if the Jenne part number was found using the PartLocator. [Service Release: 8.12] | ||
9. The user Maintenance window now has columns to show the UserName, OSLoginName, a Reference column, and also a "Flags" column. An "M" will appear in the Flags column if the user has master rights, and a "*" will appear in the UserName has a blank password. The Reference column will display the first 50 characters of the first line of the Notes field. [Service Release: 8.12] | ||
10. For QuoteValet users, you are no longer required to fill out the ManufacturerPartNumber field as a requirement for a picture to appear on the QuoteValet quote for a line item. [Service Release: 8.12] | ||
11. For ConnectWise users, when retrieving a contact from ConnectWise, QuoteWerks now respects the Contact's Communication Defaults for Phone, Fax, and Email if specified. [Service Release: 8.12] | ||
12. For MS CRM users, custom status reasons for a Lost or Won Opportunity are now supported for versions 6 and higher. [Service Release: 8.12] | ||
13. Effective July 2017 Supplies Network now requires all xml queries to be sent using the TLS 1.2 protocol. QuoteWerks now supports this. The TLS 1.2 protocol is not available on Windows XP machines, so any users that wish to use QuoteWerks (or any other software) to interact with Supplies Network XML services will need to be running the software on Windows Vista or higher. Additionally TLS 1.2 requires that the Microsoft .NET framework version 4.5 be installed and Internet Explorer (IE) 11 or higher needs to be installed. In Microsoft IE, TLS 1.2 must be enabled. To enable, click on the Gear/Settings button in IE and select Internet Options from the menu. Go to the Advanced tab, and under the Security section, make sure that TLS v1.2 is checked. [Service Release: 8.12] | ||
14. The action of "DocumentDeletedFromQuoteValet" is now added to the Document Audit Trail log. [Service Release: 8.12] | ||
15. When documents are deleted, that action is now logged in the event.log, like this: [AuditTrail] John Lewe deleted document 'FLAQ1964' (DocID=3365)
[Service Release: 8.12] | ||
16. For ConnectWise users, added Datalink mappings for individual TaxCodeLevelRates 1 - 5. This is helpful for Canadian users to be able to map to PST and GST tax rates which was not available with the existing "Company->TaxRate" Datalink that combines all of the tax code levels into a single rate. The new Datalinks are "Company->TaxCodeLevel1Rate" through "Company->TaxCodeLevel5Rate". [Service Release: 8.15] | ||
17. SugarCRM 7.9 is now supported! [Service Release: 8.18] | ||
18. Sage 50 Accounting 2018 US Edition (Peachtree) is now supported! [Service Release: 8.18] | ||
19. For QuickBooks Online Users, the BillTo Email address is now populated in Estimates, Invoices and Sales Receipts. There is a new Setting in the QuickBooks Online Setup in QuoteWerks to default the "Send later" Option for emailing documents. [Service Release: 8.18] | ||
20. For QuickBooks Online Users, added additional QuoteWerks header fields that can be mapped to QuickBooks Online Custom fields. These fields include: SoldToCompany, SoldToContact, ShipToCompany, ShipToContact, BillToCompany, BillToContact, and SoldToPONumber. [Service Release: 8.18] | ||
21. For QuoteValet Mobile users, we've updated the user interface, fixed some UI issues like the issue when scrolling through multiple pages of the NEW template list.
You can now select a contact for the Mobile quote from Autotask, and we've updated QuoteValet Mobile to work with the new ConnectWise REST API. Posted live August-23-2017. [Service Release: 8.19] | ||
22. For ConnectWise users, when writing products to a ConnectWise Opportunity, if the Vendor Name is not empty in QuoteWerks, the vendor will now be added to the ConnectWise Procurement Item. The Vendor Name in QuoteWerks must match exactly to the Vendor Company name in ConnectWise. If no match is found, no vendor will be written to the ConnectWise product on the opportunity. [Service Release: 8.19] | ||
23. The Amazon consumer pricing feature that was part of the Product Content Subscription is now available again! [Service Release: 8.20] | ||
24. QuickBooks USA 2018 is now supported! [Service Release: 8.25] | ||
25. For QuickBooks Online users, you can now map the QuoteWerks InternalPartNumber field to the QuickBooks Item Name. [Service Release: 8.25] | ||
Misc Features - Build 8 | ||
1. Most SQL queries timeout setting was increased from 30 seconds to 45 seconds. [Service Release: 8.12] | ||
2. During data conversion to version 5.2 build 1, the KeyName from INI data is now trimmed to clean any possible corruption in INI data. [Service Release: 8.12] | ||
3. For MS CRM users, the MS CRM Lost Opportunity window now has the cancel button disabled. [Service Release: 8.12] | ||
4. If a field or label in the layout designer has the [ ] Hyperlink option set, the full value of the field or label will now just run outside the bounds of the field or label ensuring that the URL link will not be cutoff. [Service Release: 8.12] | ||
5. More Debug information added to errors relating to threaded realtime calls. [Service Release: 8.12] | ||
6. For ConnectWise Users, the Create/Update Opportunity Window is now smaller to fit on laptop screens. [Service Release: 8.14] | ||
7. For QuickBooks Online users, the maximum search results for products/items and customers/contacts has been increased from 100 to 1000. [Service Release: 8.18] | ||
8. For ConnectWise users, the ConnectWise User list including Assign Tos would include all ConnectWise Member types including API users. API users are no longer returned. [Service Release: 8.19] | ||
Fixes - Build 8 | ||
1. Issue displaying the QuoteWerks Help file from the Help->Contents & Index or by pressing F1 within QuoteWerks. [Service Release: 8.12] | ||
2. For ConnectWise Users, added back Company->Territory and Company->Market as Datalink Fields. [Service Release: 8.12] | ||
3. For ConnectWise users, when creating a new Opportunity in ConnectWise for a company that did not have existing opportunities, a message was displayed "There was an error Retrieving Existing Opportunities for the ConnectWise Contact." After which, a new Opportunity could be created. The Message is no longer displayed. [Service Release: 8.12] | ||
4. For ConnectWise users, when creating new catalog items / products in ConnectWise, QuoteWerks was providing ConnectWise with both the SubCategory Name and Subcategory ID via the API. This was causing a problem if there were multiple SubCategories Named the same especially if one was inactive. [Service Release: 8.12] | ||
5. For ConnectWise users, when creating new catalog items / products in ConnectWise, if the field in QuoteWerks that was mapped to the ConnectWise ItemID contained a LineFeed, an error would be returned from ConnectWise. [Service Release: 8.12] | ||
6. For ConnectWise users, when searching ConnectWise for products via the QuoteWerks Product Lookup, the Manufacturer Part Number Search was only searching the ProductID. This could cause an issue depending on the mappings. The search will now return results for both the ConnectWise Product ID and Manufacturer Part Number. [Service Release: 8.12] | ||
7. For ConnectWise Users, when updating an Existing Opportunity in ConnectWise that was previously deleted in ConnectWise, there was not an option in QuoteWerks to create a new Opportunity in ConnectWise. [Service Release: 8.12] | ||
8. For ConnectWise Users, after converting an Opportunity to Lost, the default options for Ticket, Agreement, and Sales Order Conversion would be used as if the Opportunity was Won. [Service Release: 8.12] | ||
9. For some users, when attempting to preview, print, or save as PDF customized layouts (FPC files) would result in an error about pdc32.dll. [Service Release: 8.12] | ||
10. For ASI customers with the Product Content Subscription, the ASI cost was appearing as 0.00 in the Etilize Comparison Window. [Service Release: 8.12] | ||
11. For Autotask Users, when updating an Opportunity in Autotask, the error ?Reference value on field: ProductID of type: Product does not exist or is invalid? in ?DLL method: UpdateOpportunityEX()? was received. This was because the default Product in Autotask was disabled in Autotask. This product is required to update an opportunity via the Autotask API. The message returned when attempting to update an opportunity now returns the specific ProductID and the Name for the Product that must be set to Active in Autotask. [Service Release: 8.12] | ||
12. For ConnectWise users, when adding products to a ConnectWise Opportunity Bundle, the Cost and Price would be the Cost and Price from the Catalog Item in ConnectWise and not the Cost and Price from the QuoteWerks Document. [Service Release: 8.12] | ||
13. For ConnectWise users, when creating a Recurring Forecast on a ConnectWise Opportunity, the following error would be returned from ConnectWise when the Cost was $0.00: "The recurring/recurringCost field is required. [ resource: forecast - field: recurring]". This is an issue with the ConnectWise API. To workaround until a fix, QuoteWerks now sends a $0.0001 Cost to ConnectWise when the Cost is $0.00. [Service Release: 8.12] | ||
14. When selecting items from Etilize for use in Required Items, the item would not be found. [Service Release: 8.12] | ||
15. For ConnectWise users, when retrieving an Opportunity to create a new Quote via the QuoteWerks Dashboard, Opportunity Line Item Descriptions would not retain Line Formatting. [Service Release: 8.14] | ||
16. For ConnectWise Users, when converting to an Order/Invoice in QuoteWerks and winning the Opportunity in ConnectWise, if the ConnectWise Opportunity was not found/deleted, the user would be prompted if they would like to create a new or link to an existing Opportunity. If the user selected "Yes", the Opportunity Window would not appear and an Opportunity would not be created or linked to in ConnectWise. [Service Release: 8.14] | ||
17. For ConnectWise users, when requesting quantity on hand for products/catalog items in ConnectWise, there was an issue when there were inactive warehouses. A message would be returned containing: 'Object reference not set to an instance of an object.' [Service Release: 8.14] | ||
18. For QuickBooks Online users, when exporting a Purchase Order, a message box was not shown confirming the Purchase Order Number created. [Service Release: 8.14] | ||
19. For QuickBooks Online users, the confirmation message after exporting an Estimate, Invoice, or Sales Receipt did not have correct instructions for finding the document in QuickBooks Online. [Service Release: 8.14] | ||
20. For ConnectWise users, addressed an issue when converting opportunities to Agreements where the Agreements in ConnectWise contained unexpected Null values. The Agreement window was not shown and the Agreement was not created in ConnectWise. [Service Release: 8.15] | ||
21. For QuickBooks Online users, when the option was set to use the "Document Date" as the transaction date in QuickBooks Online, there were times the date exported would be used incorrectly. [Service Release: 8.18] | ||
22. For QuickBooks Online Users, the QtyMultiplier fields for items were not accounted for when writing products to QuickBooks Online Documents. [Service Release: 8.18] | ||
23. For QuickBooks Online Users, when using the integration with Canadian QuickBooks Online, there was an issue validating the 'Non-Taxable' Tax Code. [Service Release: 8.18] | ||
24. For QuickBooks Online Users, when changing the After Export Document Status in the QuoteWerks QuickBooks Online Setup, if QuoteWerks was not restarted, the previous status would be used for export. [Service Release: 8.18] | ||
25. For QuickBooks Online users, the Quantity for items on documents would only use whole numbers. Decimal Numbers would be rounded to the nearest whole number and used as the quantity. For example, a quantity of 0.25 would be rounded down to 0. [Service Release: 8.18] | ||
26. For QuickBooks Online users, when creating a Purchase Order in QuickBooks and the option to update item cost/price was enabled, an error would be returned and the Purchase Order would not be created in QuoteWerks or QuickBooks Online. [Service Release: 8.18] | ||
27. For ConnectWise users, When requesting inventory on hand for a ConnectWise Product an 'Index was outside the bounds of the array.' message was returned. This was due to changes in the way ConnectWise returns data in an update to their REST API. [Service Release: 8.18] | ||
28. Would receive error "subscript out of range" when using the File->Login as another user and then opening a quote. [Service Release: 8.19] | ||
29. Would receive error "Object variable or With block variable not set" when using File->Login as another user and then holding down SHIFT when pressing ENTER, and then clicking on the [Event Viewer] button. [Service Release: 8.19] | ||
30. For ConnectWise users, when attempting to retrieve an existing ConnectWise Activity to update that had a Reminder of "0 minutes", an error would be returned and the Activity would not be available to update in QuoteWerks. [Service Release: 8.19] | ||
31. For ConnectWise users, when updating an existing opportunity that had Custom Fields, the Custom Fields would revert to the default value (possibly empty or blank). This fix will work with ConnectWise version 2017.5 and higher. ConnectWise 2017.5 or higher is required because there was an issue with updating ConnectWise Opportunity Custom fields in earlier versions of the ConnectWise API. [Service Release: 8.19] | ||
32. For ConnectWise users, when the first or last name of the ConnectWise Member contained parentheses, QuoteWerks would not be able to determine the correct ConnectWise Member ID. Opportunities, Activities, and other integration points where the sales rep name was selected would not be able to be created if the user with parentheses in the name was selected as the sales rep. [Service Release: 8.19] | ||
33. For ConnectWise users, when adding a Shipping item to a ConnectWise Opportunity, would receive a Runtime error 9 - subscript out of range. [Service Release: 8.21] | ||
34. For ConnectWise Users, the ConnectWise REST API currently does not support setting Custom Fields on the ConnectWise Opportunity with a Custom Field Entry Method of List or Option. If QuoteWerks or any other API integrated solution attempts to update these, an error will be returned. Ticket #9431461 has been submitted to ConnectWise regarding the issue with their API. Rather than an error, the Custom fields are sent over without a value so they will revert to the default values when QuoteWerks updates an Opportunity. Custom Fields with an Entry Method of EntryField are written without issue. [Service Release: 8.25] | ||
35. When creating a new product and before saving the new product tried to add a QuoteValet video and error would occur. [Service Release: 8.25] |
©1993-2024 Aspire Technologies, Inc.
407-248-1481 (9am-5pm ET M-F)
Please Wait...