407-248-1481
QuoteWerks Update Center
Version 5.6 Summary
| 176 New, 163 Fixes, and 37 Miscellaneous features | ||
| New Features - Version 5.6 | ||
| 1. Added new "Enable individual Resource security" option on the Security tab of Tools->Options. When this option is set, you can specify File Access Rights for individual files like Cover Pages, Print Layouts, and Literature. Print Layouts support View and Modify. Cover Pages and Literature support View only. To set these File Access Rights, right click on a Print Layout or Literature file and choose "Set Access Rights...". This right click menu is not available on the 'Additional' Layouts tab, all Access Rights for layouts must be set through the 'Primary' tab. For a Cover Page, select the Cover Page, and click on the [Set Access Rights] button next to the Cover Page drop down list. You will be able to set these File Access Rights if you are a user with Master Rights or if you have the new Misc Access right of "NonMasterRightsUser_CanAdministerDeliverables". When this "Enable individual Resource security" option is activated, no users will be able to see any Cover Pages, Print Layouts or Literature files. To see these files and assign Access Rights, you will need to be a user with Master Rights (or have the Misc Access right of "NonMasterRightsUser_CanAdministerDeliverables"), and you will need to check the "[] Administration Mode" checkbox on the Print window. This will show all the Cover Pages, Print Layouts and Literature files. In this mode, any files that do not have any Access Rights set for them will be displayed in red (meaning they will not be visible by any users). For Files that do have Access rights set for them, you will see an indicator prefix like [ 02 ] in front of the name of the Cover Page, Print Layout or Literature file. This will indicate how many different users or groups have access to see this Cover Page, Print Layout or Literature file. When the "[] Administration Mode" checkbox is checked, you will be able to select multiple layouts at the same time by holding down the SHIFT or CTRL key while clicking on each individual Layout. The Access Rights that you set will be applied to all the selected layouts. Any previous rights set for these selected files will be replaced. The default rights to apply to all the files will be the ones for the layout that you right clicked on. [Build: 1] | ||
| 2. You can now show/hide individual toolbar buttons on the Document Items tab Grid Toolbar. These buttons can be hidden per user under the Menus tab of the User Properties window. There is a new "Grid Toolbar" hive in the treeview. Of note, some of the actions are available through a Menu and a Toolbar button. You will need to Show/Hide these actions separately. [Build: 1] | ||
| 3. For Maximizer users, Maximizer CRM 2020 R2 is now supported [Build: 1] | ||
| 4. For MS CRM users (Microsoft Dynamics), OAuth2 authentication is now supported. This is helpful for Microsoft Dynamics CRM customers that have Multifactor Authentication (MFA) / Two Factor Authentication (2FA) enabled in Dynamics. [Build: 1] | ||
| 5. For QuickBooks Desktop and QuickBooks Online users, you can now re-export Purchase Orders to QuickBooks. On the Purchase Orders tab of the Purchase window, right click on a Purchase Order and choose "Re-Export PO to 'QuickBooks'". [Build: 1] | ||
| 6. For Peachtree/Sage 50 US Edition users, you can now re-export Purchase Orders to Peachtree/Sage 50 US Edition. On the Purchase Orders tab of the Purchase window, right click on a Purchase Order and choose "Re-Export PO to 'Peachtree'". [Build: 1] | ||
| 7. For ConnectWise Manage users, you can now re-export Purchase Orders to ConnectWise Manage. On the Purchase Orders tab of the Purchase window, right click on a Purchase Order and choose "Re-Export PO to 'ConnectWise'". [Build: 1] | ||
| 8. For Autotask users, you can now re-export Purchase Orders to Autotask. On the Purchase Orders tab of the Purchase window, right click on a Purchase Order and choose "Re-Export PO to 'Autotask'". [Build: 1] | ||
| 9. For Product Content Subscribers using Etilize as a Product Source, the Etilize "My Favorites" now supports Folders. This will enable you to organize your commonly quoted products in folders and sub-folders instead of scrolling through an unorganized list of products. [Build: 1] | ||
| 10. For Product Content Subscribers using Etilize as a Product Source, under the Etilize Product Source, there is now a "Public Favorites" folder. This feature is similar to the Etilize "My Favorites", but can be seen by all users. At a site level, you can organize your commonly quoted products in folders and sub-folders to make it easy for your sales people to quote the items you want them to quote without having to search Etilize for them. [Build: 1] | ||
| 11. For Product Content Subscribers using Etilize as a Product Source, there is a new Etilize "Workspace" feature. The new feature is very useful when doing research. You can easily add products that you are considering selling to your customer, or products that you might want to sell, but need to do some more research on. Products that you add into the Workspace folder are remembered the next time you run QuoteWerks, so you can easily come back to the products you have been working with. Each user has their own Workspace. This Etilize Workspace folder is different than the Etilize "My Favorites" folder and Etilize "Public Favorites" folder. [Build: 1] | ||
| 12. The Product Content Subscription now has PartLocator support for Arlington. We've negotiated an arrangement with Arlington to host their parts list to provide our mutual customers with a better ability to locate Arlington part numbers when quoting. For Toner and other related searches both the Brand Name item and the Remanufactured item will be available in the results. [Build: 1] | ||
| 13. For QuickBooks Online users, on the Mappings.Items tab of the setup there is now an option to choose which field from the QuoteWerks line item that is used for the QuickBooks Item Description. You can choose Description, CustomMemo01, CustomMemo02, CustomMemo03, CustomMemo04, CustomMemo05. [Build: 1] | ||
| 14. For QuickBooks Online users, on the Mappings tab of the setup, there is now an option to choose which field from the QuoteWerks line item that is used for the QuickBooks Purchasing Description on Purchase Orders (POs). You can choose Description, CustomMemo01, CustomMemo02, CustomMemo03, CustomMemo04, CustomMemo05.
[Build: 1] | ||
| 15. For QuoteWerks Web users, there is now a [Refresh] button on the File Links tab of the Quote WorkBook. Use this to synchronize layout, cover page, literature, spec sheet, image, lease rate files, etc. to/from QuoteWerks Web. After the synchronization is performed, the File Links list will be reloaded so that you can see any new files as a result of the synchronization process. Having this button located on the File Links tab is very useful as it lets regular users easily initiate the synchronization of the files when they need to. The Misc Access Rights of "CannotUseQuoteWerksWebSyncUp" and "CannotUseQuoteWerksWebSyncDown" have been added as a way to control user access to this feature. This synchronize and refresh feature can also be accessed with the new [Sync QuoteWerks Web] button on the Print window. [Build: 1] | ||
| 16. Added new Product->Lookup window, right click menu "Associate item(s) with Folder..." This will now prompt you to choose a product database folder from a folder selection dialog. This can make this activity faster than the existing way of selecting products, then Copying them, then navigating to a folder and right clicking and choose the "Associate copied items with this folder". [Build: 1] | ||
| 17. On the Product Lookup window, when right clicking on a native product database folder, the option to "Associate copied item(s) with this folder" will now indicate how many copied items are in the clipboard. The Disassociate feature has the same improvement. [Build: 1] | ||
| 18. Added new Product->Lookup window, right click menu, "Disassociate selected items from this Folder..." [Build: 1] | ||
| 19. For Tech Data customers in USA, using the "Import Tech Data SAP Quote" feature, there is now an additional "Import Tech Data SAP Quote (JSON)" feature if you setup your Tech Data JSON API credentials. Using this newer JSON API version you will be able to see Tech Data quotes that start with a '1', in addition to the Tech Data quotes that start with the number '4'. [Build: 1] | ||
| 20. For Tech Data customers in USA, there is a new "Import Tech Data CCW Quote (JSON)" feature if you setup your Tech Data JSON API credentials. With this new feature you can retrieve Cisco CCW Deals, CCW Estimates, CCW Quotes, and CCW Renewal Quotes. When you request these Cisco CCW quotes, behind the scenes the Tech Data API requests them from Cisco and copies them into a Tech Data SAP quote which is then returned to be imported into QuoteWerks. QuoteWerks automates this entire workflow. Your CCW account must be linked to your Tech Data account to use this functionality. On the Tech Data Website, go to the 'Buy -> Cisco 1' Source Menu. Under the 'Quote Creator' Section, if you see 'Connect To CCW' in a big yellow button, your account is not linked to Cisco. [Build: 1] | ||
| 21. For Tech Data Online Ordering users, the special instructions field length was increased from 55 to 132 characters. [Build: 1] | ||
| 22. Dicker Data Realtime Pricing and Availability now available for customers in Australia and New Zealand. A Dicker Data API Token is required to use this feature. If no API token is entered, the Part Locator Price will be used when performing an Etilize search. Real-time Module required for Realtime Pricing and Product Content Subscription required for PartLocator. [Build: 1] | ||
| 23. For SYNNEX Users in USA and Canada, you can now Import quotes from SYNNEX. These can be Quotes that you create on the SYNNEX website or that your SYNNEX Sales Rep creates for you. Simply enter your quote number and you can preview the quote items before importing them into your QuoteWerks Quote Workbook. [Build: 1] | ||
| 24. For ConnectWise Manage Users in Canada, there is a new mapping on the ConnectWise Setup Window for Taxable Products in the ConnectWise Manage Product Catalog. The mapping enables a taxable item to be set as PST Only, GST Only, or Both GST and PST. For users outside of Canada, the only option is 'Y' for taxable. [Build: 1] | ||
| 25. When a document is locked, you will now be able to select text in the individual fields so that you can copy text out of the fields on the Quote WorkBook. [Build: 1] | ||
| 26. Added new "Zoom Description" button to the grid toolbar on the Document Items tab of the Quote WorkBook. [Build: 1] | ||
| 27. In the Vendor Import Wizard, you can now import into the "Notes" field. [Build: 1] | ||
| 28. When a user deletes a products folder, it there will now be an Audit Trail record of it in the event.log.
[Build: 1] | ||
| 29. There is a now an Edit->Paste Line Attributes menu. To use this, select a single line item, and right click and choose copy. Then you can select one or many line items, and right click and choose 'Paste Line Attributes' to paste the line attributes from the copied line item into the selected line items. This will paste all the Line Attributes as seen on the Edit->Edit Line Attributes window. [Build: 1.03] | ||
| 30. For QuickBooks Desktop and Online users, on the Export to QuickBooks window, when clicking on the [Find DocNo] button, you can now enter the % symbol for "Begins with" (AAAQ1%), "Ends with" (%100), or "Contains" (%Q%) searches. [Build: 1.03] | ||
| 31. Peachtree/Sage 50 US Edition users, on the Export to Peachtree window, when clicking on the [Find DocNo] button, you can now enter the % symbol for "Begins with" (AAAQ1%), "Ends with" (%100), or "Contains" (%Q%) searches. [Build: 1.03] | ||
| 32. When inserting/adding Section Header or Heading Line, when you are prompted for the description, you can now double-click in the description field to bring up the F2 Lookup in addition to pressing the F2 key. This is activated as long as the user preference of "Enable double-click to bring up F2 Lookup in text boxes" is set.
[Build: 1.03] | ||
| 33. For QuoteValet users, when sales rep uploads a file to the Upload Area on the QuoteValet document the customer will receive a notification e-mail alerting them to this new upload for them. Since sales reps may upload multiple files before delivering the quote to the customer, the customer will only receive notifications of file uploads AFTER the customer has viewed the quote at least once. [Build: 1.04] | ||
| 34. There is now a Payment Option Recurring Phrase Display Macro setting on the Payment tab of the Tools->Options menu called "Payment Option Recurring Phrase display macro". The default is ", [plus %RecurringCycleSubtotalWithTax% %RecurringCycleWord%]". You can use this to customize the recurring portion of the text that appears in the Payment Options text. While the words for the "%RecurringCycleWord%" macro default for English users to weekly, monthly, quarterly, and annually, you can change these in the Settings Manager with these settings: SystemSettings\System\PaymentOptionWeeklyRecurringCycleWord, SystemSettings\System\PaymentOptionMonthlyRecurringCycleWord, SystemSettings\System\PaymentOptionQuarterlyRecurringCycleWord, and SystemSettings\System\PaymentOptionAnnuallyRecurringCycleWord. [Build: 1.04] | ||
| 35. The Configurator now has a description preview panel (with scrollbar), so now can see the entire description of a product when selected. [Build: 1.04] | ||
| 36. For QuoteValet users, to provide context, the PAYMENT notification email subject line will now display the payment reference (like Deposit), and also the remaining balance. For Example: QuoteValet: PAYMENT: 'Deposit' Payment of $106.95 made (remaining balance is $536.05) - ABC Computer #AAAQ1001. [Build: 1.04] | ||
| 37. On the Send E-mail window there is now a toolbar button [Copy QuoteValet Customer Facing URL from] button. This will let you search for another quote to copy the QuoteValet Customer Facing URL from so that you can paste it into the current e-mail you are composing. In the situation where you have prepared more than one quote for your customer relating to the same project, and you want to just send them one QuoteValet notification email that contains the QuoteValet links to all of these quotes, this new feature helps you do this efficiently. [Build: 1.04] | ||
| 38. Added [Copy Customer facing URL] button to the QuoteValet tab. [Build: 1.04] | ||
| 39. In the Configurator, the prompt text display area now has a scrollbar. [Build: 1.04] | ||
| 40. On the Apply Multi-line changes window, the customized label names for all fields, not just Custom fields will be displayed. These changes have also propagated to other areas. [Build: 1.04] | ||
| 41. For QuoteValet users, there is a new search option for "DocNo contains" on the Reporting tab of the QuoteValet Dashboard. [Build: 1.04] | ||
| 42. When using the built-in QuoteWerks contact database as the CRM, you can now search for contacts by "Postal Code". [Build: 1.04] | ||
| 43. For QuoteValet users, when adding/editing a QuoteValet video, the Title and Video URL text boxes now support the F2Lookup ( F2 key and double-click). [Build: 1.04] | ||
| 44. On the Misc.General tab of the Tools->My Preferences window, there is now a new option of "<None>" for the "Document Search Defaults". The benefit of this option is that the time it takes to load the Open Document window will be reduced dramatically since it will not run a default query every time it loads, before you have even entered in search criteria that you want to search for. [Build: 1.04] | ||
| 45. On the Purchase Orders tab of the Purchasing window, adding and removing tracking numbers is handled more robustly now. When deleting the last tracking number, the ShipVia (Carrier), is also cleared so that you can specify it when adding the first tracking number back. There is now also a warning about manually adding tracking numbers to a realtime order. [Build: 1.04] | ||
| 46. On the Purchase Orders tab of the Purchasing window, the right click "Change ShipVia" menu for a PO Item now will warn you, but then let you change the ShipVia (Carrier), even for a realtime order.
[Build: 1.04] | ||
| 47. You can now use the DataLink to retrieve a field value into the SoldToCompany, SoldToAddress2, and SoldToAddress3 fields. [Build: 1.09] | ||
| 48. When on the Product Lookup grid, you can now press the F5 key to refresh the grid with the underlying data in case that was just changed outside of QuoteWerks. This now works for Native Product Databases, MS SQL, ODBC, OLEDB, Excel, and Access data sources, in addition to QuickBooks, Peachtree, Zoho, and Salesforce.com. [Build: 1.09] | ||
| 49. The Act! Desktop search now remembers the last contact search method, either current contact, or search contact, per user. [Build: 1.09] | ||
| 50. The Paste Special Wizard now has a new step of "Additional Data Mappings". Here you can map in some static values or expressions. So if the data that you are pasting from the clipboard does not have a Vendor column, you can use this new capability to specify a static value like "Tech Data" to be set as the Vendor for all the pasted rows. Also, you can enter an expression like "The color of item <Column3> is <Column6>" and the values for Column3 and Column6 will be inserted into the text as it is pasted into the quote. [Build: 1.09] | ||
| 51. When creating a PO in QuoteWerks manually or through an electronic order, there is now a new "PO Created" dialog that appears. On this dialog you can choose to [Save PO as PDF] or [E-mail PO]. You no longer have to find the PO after you create it to then save it as a pdf, etc. The result text can be highlighted and copied to copy PO# from QuoteWerks, Distributor, and Accounting systems from this dialog. [Build: 1.09] | ||
| 52. There are now Audit Trail entries for when a User is deleted, a Group is deleted, a Group is created, or when a Group is renamed. [Build: 1.09] | ||
| 53. On the Save as Revision window, the "Delete previous revision" and "Update Expiration Date" checkboxes now remember their last setting per user. [Build: 1.09] | ||
| 54. On the Product Price History window, if the user has the Misc Access Right of "CannotSeeCostOnAddItemAssistant", then the Cost column data will only show "n/a".
[Build: 1.09] | ||
| 55. OAuth 2.0 Authentication is now supported when sending emails through Gmail/GSuite mail servers. [Build: 2.07] | ||
| 56. OAuth 2.0 Authentication is now supported when sending emails via SMTP through the Microsoft Office 365 mail server. [Build: 2.07] | ||
| 57. OAuth 2.0 Authentication is now supported when sending emails via SMTP through a Microsoft Live mail server. Microsoft Live mail servers host email addresses ending in '@hotmail.com', '@live.com', and '@outlook.com'. [Build: 2.07] | ||
| 58. Added MAPI support for sending emails. This will send emails created in QuoteWerks via the default Windows Mail Client. A limitation of the MAPI protocol is that the message body in an email can only be plain text - not HTML. There is a setup option to display the email in the email client before sending the email. MAPI support is useful for those that do not use Outlook and do not want to send via SMTP - like Groupwise and Thunderbird. [Build: 2.07] | ||
| 59. For Product Content Subscribers, when searching Etilize or using the Etilize Panel with the Multiple Database Search via the Product Lookup window, you can now choose to also have Native and External Product Data Sources also searched for the same product and the results will be displayed along with the returned real-time vendor results. The Manufacturer Part Number is used to find the product. If a product is not returned from Etilize or the PartLocator, a Product Data Source search will not occur. On the Product Content Subscription tab of the Real-time setup window, the QuoteWerks Administrator can specify which Product Data Sources to use with the Etilize Search, this setting is a site wide setting. [Build: 2.07] | ||
| 60. For Kaseya BMS users, you can now create a new Kaseya BMS Company 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 Kaseya BMS. Also, the Company, Contact, Email, and Phone fields 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.07] | ||
| 61. For QuickBooks Online users, if the option to "[ ] Convert grouped items to single item" is not set on the Mappings.Items tab of the QuickBooks Setup window, and the new option "[] Include Group Header as a Comment when not converting grouped items into a Single Item." is set, the description of the Group Header line will be inserted as a comment line above the group member lines when exported to QuickBooks. [Build: 2.07] | ||
| 62. For QuickBooks Online users, when exporting to QuickBooks, if the option to "[x] Convert grouped items to single item" was set on the Mappings.Items tab of the QuickBooks Setup window, and the new option "[x] Include Group Items as Comments" is set, then the descriptions of all the group member line items will be added as comment lines below the group header line when exported to QuickBooks. [Build: 2.07] | ||
| 63. For Ingram Micro users that use the Quote Importer, the Ingram Micro Quote Number, Expiration Date, and the Line Item Comments can now be mapped to the imported QuoteWerks line item's CustomText or CustomMemo fields. [Build: 2.07] | ||
| 64. For Tech Data users that use the Quote Importer (including the Cisco Quote Importer), the Tech Data Quote Number and Expiration Date can now be mapped to the imported QuoteWerks line item's CustomText or CustomMemo fields. [Build: 2.07] | ||
| 65. For SYNNEX users that use the Quote Importer, the SYNNEX Quote Number can now be mapped to the imported QuoteWerks line item's CustomText or CustomMemo fields. [Build: 2.07] | ||
| 66. For ConnectWise Manage Users, there are new options on the ConnectWise Setup Window to include all Document Attachments and include all Notes from the Opportunity when converting a ConnectWise Opportunity to a ConnectWise Service Ticket. This does not affect creating one off Service Tickets in ConnectWise. [Build: 2.07] | ||
| 67. For Zoho users, there is now a "View Sold to" link on the Links tab of the Quote WorkBook that you can click to view the Contact in Zoho CRM. [Build: 2.07] | ||
| 68. For Zoho 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: 2.07] | ||
| 69. For Zoho users, you can now create a new Zoho Company 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 Zoho. 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.07] | ||
| 70. For MS CRM users, the tax amount now comes over for a line item on a Quote. [Build: 2.07] | ||
| 71. For MS CRM users, if you select a different contact for an existing Opportunity, you are now given the option to clear out the existing Opportunity link data. [Build: 2.07] | ||
| 72. For MS CRM users, you can now choose the Status for new Opportunities. The default Status can be set with the MSCRMOppStatusCodeOpen setting. [Build: 2.07] | ||
| 73. For MS CRM users, you can choose the owner of an Opportunity on the Create Opportunity window in QuoteWerks. [Build: 2.07] | ||
| 74. For MS CRM users, you can choose the default owner for an Opportunity in the MS CRM Setup Window. The Owner can either be the logged in user or the Sales Rep. The Sales Rep name must match the MS CRM user name to be selected.
[Build: 2.07] | ||
| 75. For SugarCRM users, a Call will now be saved to a contact if an account is not selected. [Build: 2.07] | ||
| 76. For SugarCRM users, there is now a "View Call" link on the Links tab of the Quote WorkBook that you can click to view the Call in SugarCRM. [Build: 2.07] | ||
| 77. For SugarCRM users, there is now a "View Opportunity" link on the Links tab of the Quote WorkBook that you can click to view the Opportunity in SugarCRM. [Build: 2.07] | ||
| 78. For SugarCRM users, there is now a "View SoldTo" link on the Links tab of the Quote WorkBook that you can click to view the Contact in SugarCRM. [Build: 2.07] | ||
| 79. For SugarCRM users, files can now be attached to opportunities from the Opportunity creation window. [Build: 2.07] | ||
| 80. For SugarCRM users, Opportunities can now have their name set by the user. [Build: 2.07] | ||
| 81. For SugarCRM users, the SugarCRM connection will be reconnected automatically if the session is expired. [Build: 2.07] | ||
| 82. For Maximizer CRM users, Enum fields in Maximizer CRM are now supported in the QuoteWerks DataLink. [Build: 2.07] | ||
| 83. When entering a PO NUmber when creating an Online Order or a Manual PO, you will now be warned if you are entering a PO number that already exists in QuoteWerks. It is not recommended to use the same PO Number for multiple purchase orders.
[Build: 2.07] | ||
| 84. SugarCRM 10.3 is now supported! [Build: 2.07] | ||
| 85. HubSpot CRM integration! The integration with HubSpot CRM includes the ability to search for contacts, create/update Deals, and upload quote attachments to HubSpot CRM. DataLink is supported for Contacts, Accounts, Deals and LineItems. The HubSpot CRM Product Database is available on the Product Lookup. You can attach files to the HubSpot CRM Deal 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 HubSpot CRM, and also a link on the Links tab that you can click to view the HubSpot CRM Deal in HubSpot CRM. Additionally, emails sent from QuoteWerks are logged in HubSpot CRM history. QuoteWerks integrates with all editions of HubSpot CRM, however, if you want to integrate with the HubSpot Deal Line Items, then HubSpot Professional edition or higher is required. The Professional or Corporate Edition of QuoteWerks is required to integrate with HubSpot CRM. [Build: 3.19] | ||
| 86. ACT! Desktop version 23 is now supported! [Build: 3.19] | ||
| 87. ACT! for Web version 23 is now supported! [Build: 3.19] | ||
| 88. Added new Tools->View/Edit Item in Product Database menu. You can use this to select a line item on a quote and quickly display the product definition in the Product Database for this item. From there you can just view all the details of the item or you can make changes to it. You can select multiple line items in the quote, and the Edit Item window will be displayed for each selected item, one by one. This new feature enables you to skip so many steps. Previously you would have to open the Product Lookup window, choose the Product Database, type in a search value and click search, then double click on the Item to view it. [Build: 3.19] | ||
| 89. When editing a Report Layout in the Report Layout Designer, you can now select the "Save & Preview" toolbar button to preview your changes. Once you close the preview you will be placed back into Report Layout Designer for you to easily make more changes. [Build: 3.19] | ||
| 90. On the Edit Report window, the [Save, Close, & Preview] action no longer has to close the Edit Report window, so it has been renamed to [Save & Preview] or [Save & Export] depending upon the report type. This is huge time saver, it lets you make changes and view the output and leaves you in the Edit Report window for you to easily make more changes. [Build: 3.19] | ||
| 91. When placing online orders, the QuoteWerks PO Item now records the StandardUnitCost which is populated from realtime pricing. It also records the UnitCost from the QuoteWerks order or the negotiated price override that you enter when placing the electronic order. If the UnitCost does not match the StandardUnitCost, there will be an additional display in the Cost column on the Purchase Orders and Ordered Items tabs of the Purchasing window. It will display, for example, "
$179.83 ($539.49)" on the first line, and "$199.95 ($599.85) STD" on the second line. The number in the parenthesis is the extended Cost, and the second line that has the "STD" postfix indicates this is the standard price. [Build: 3.19] | ||
| 92. For MS CRM users, you can now retrieve account level OR contact level DataLink values for a SoldTo, ShipTo, or BillTo contact through QuoteWerks Datalinking. [Build: 3.19] | ||
| 93. There is now a [New Line] button on the Edit Required Items window. You can use this to create Required Items that are not from a product database, like comments, headings, etc. [Build: 3.19] | ||
| 94. On the Email tab of User Preferences, you can now setup QuoteWerks Web Oauth email options. [Build: 3.19] | ||
| 95. For salesforce.com users, you can now specify the backend login url to use. This is helpful for any user that is having problems logging into salesforce with the Salesforce "My Domain" feature enabled. You can specify this url in the Settings Manager, by setting SystemSettings\Contact Managers\SFLoginOverrideURL={your url} [Build: 3.19] | ||
| 96. For Product Content Subscribers, the Manufacturer Part Number will be copied to the Windows Clipboard when Double-Clicking on the Manufacturer Part Number below the Product Image on the Etilize View. [Build: 3.19] | ||
| 97. For Product Content Subscribers, when performing an Etilize search and returning results from Native Product Sources, the Last Modified date for the item Definition will be displayed. [Build: 3.19] | ||
| 98. For TechData, Ingram Micro, SYNNEX, and D&H Online Ordering users, added F2Lookup (including a button) for the End User Email address. This can be a great time saver if you often choose to supply the distributor with your email address rather than the End User's. [Build: 3.19] | ||
| 99. When a Master Installation has its database hosted through the QuoteWerks Database hosting subscription, it is now possible for a Remote Site or Remote PC to synchronize with it. [Build: 3.19] | ||
| 100. For Arbitech and Westcon users there is now a "Disable" option. This is useful in debugging.
[Build: 3.19] | ||
| 101. ConnectWise 2020.4 is now supported! [Build: 3.19] | ||
| 102. When running Management Reports with the DocumentItems table, the &Picture field is now available. [Build: 4] | ||
| 103. When running Management Reports with the DocumentItems table, the &Picture field is now available. [Build: 3.20] | ||
| 104. For QuoteValet users, all operation initiations now take one second less. [Build: 3.22] | ||
| 105. The Select Special search field now supports all visible columns, and lists the fields with their customized name first. [Build: 3.22] | ||
| 106. For Zoho and Maximizer Web users, when searching for a contact, the search field is now remembered. [Build: 3.22] | ||
| 107. There is now a "View/Edit Item in Product Database" grid toolbar button. This toolbar button can be hidden just like the Tools->View/Edit Item in Product Database menu. [Build: 3.22] | ||
| 108. The DepositAmount column will now be displayed in the Open Document window grid. [Build: 3.22] | ||
| 109. For QuoteWerks Web users, added new email template macro &DH_&URLToOpenDocumentInQWW. This can be used to include a link in emails (typically for peer review and approval) to open the document in QuoteWerks Web. [Build: 3.22] | ||
| 110. The DocumentHeaders->&QuoteValetTotalPaymentsMade field is now available in Management Reports. [Build: 3.22] | ||
| 111. On the Edit E-mail signature window, there is now a [Reset to Default] button. [Build: 3.22] | ||
| 112. -New: The "Select E-Mail Recipient(s) default list" option on the Email.Defaults tab of the Tools->My Preferences menu has been removed. In the Select Email Address window, the last selected list is now remembered per user and per context of what type of email is being sent. [Build: 3.22] | ||
| 113. Added [Export to Clipboard] button in Event Viewer. [Build: 3.22] | ||
| 114. For ConnectWise Manage Users, there is a new 'QuoteValet' subtab in the ConnectWise Setup. This setup Tab is located on the main 'Opportunities' Tab. There are new options that control what QuoteValet Links to attach to the ConnectWise Manage Opportunities. There are options for 'Attach QuoteValet EXTERNAL Viewing Link', 'Attach QuoteValet INTERNAL Viewing Link', and 'Attach QuoteValet Sales Rep Facing Page Link'. By default, the option to attach all of the links will be set for backwards compatibility. [Build: 3.22] | ||
| 115. For ConnectWise Manage Users that also have a QuoteValet subscription, the QuoteValet Acceptance Package can automatically be uploaded and attached to the ConnectWise Manage Opportunity when the QuoteValet quote is accepted and converted to an Order in QuoteWerks. This setting is on the QuoteValet tab on the ConnectWise Manage setup in QuoteWerks under Opportunities. [Build: 3.22] | ||
| 116. For Kaseya BMS Users that also have a QuoteValet subscription, the QuoteValet Acceptance Package can automatically be uploaded and attached to the Kaseya BMS Opportunity when the QuoteValet quote is accepted and converted to an Order in QuoteWerks. This setting is on the QuoteValet tab on the Kaseya BMS setup in QuoteWerks. [Build: 3.22] | ||
| 117. For Maximizer CRM users, Maximizer CRM 2021 R1 is now supported. [Build: 3.25] | ||
| 118. For HubSpot CRM users, if the contact address is empty, the company address will be used when doing a search on the Lookup window. [Build: 3.25] | ||
| 119. For ACT! users, the Opportunity field Name can now be written to ACT! with DataLinking from QuoteWerks. [Build: 3.25] | ||
| 120. For ACT! users, the Opportunity Line Item field Name can now be written to ACT! with DataLinking from QuoteWerks. [Build: 3.25] | ||
| 121. For Autotask users, the Opportunity fields Rating, Title and Promotion Name can now be written to Autotask with DataLinking from QuoteWerks. [Build: 3.25] | ||
| 122. For Autotask users, the Quote Line Item fields Description and Name can now be written to Autotask with DataLinking from QuoteWerks. [Build: 3.25] | ||
| 123. For MSCRM users, the Opportunity fields RatingCode, Name and Description can now be written to MSCRM with DataLinking from QuoteWerks. [Build: 3.25] | ||
| 124. For MSCRM users, the Quote Line Item field Description can now be written to MSCRM with DataLinking from QuoteWerks. [Build: 3.25] | ||
| 125. For Zoho CRM users, the Deal fields NextStep, Title, Description, CampaignSource, Type and LeadSource can now be written to Zoho CRM with DataLinking from QuoteWerks. [Build: 3.25] | ||
| 126. For SugarCRM users, the Opportunity fields Name, Type, LeadSource, LikelyCase, NextStep, Campaign and Team can now be written to SugarCRM with DataLinking from QuoteWerks. [Build: 3.25] | ||
| 127. For SugarCRM users, the Revenue Line Item fields Name, Type, LeadSource, LikelyCase, NextStep, Campaign and Team can now be written to SugarCRM with DataLinking from QuoteWerks. [Build: 3.25] | ||
| 128. In the Paste Special Wizard, if you had set a default CostModifier or default Price modifier for Document Items, if you map a UnitCost or UnitPrice in the Paste Special Wizard, these respective Modifiers will now be cleared. Also if you are importing a line that has both a UnitPrice and a PriceModifer value mapped, the UnitPrice will be used and the PriceModifier will be cleared. Similarly, if you are importing a line that has both a UnitCost and a CostModifer value mapped, the UnitCost will be used and the CostModifier will be cleared.
[Build: 3.25] | ||
| 129. Kaseya BMS v5.1
is now supported! [Build: 3.36] | ||
| 130. For Zoho CRM users, quotes can now be created from inside Zoho from a create button. [Build: 3.36] | ||
| 131. For salesforce.com users, if the contact address is empty, the account address will be used when doing a search on the Lookup window. [Build: 3.36] | ||
| 132. The Event Log will now record when a user runs the Product Import Wizard, and will record when the user confirms the option to 'Confirm DELETION of ALL existing products'. The Event Log will now record when a user runs Contact Import Wizard, and will record when the user confirms the option to 'Confirm DELETION of ALL existing contacts'. The Event Log will now record when a user runs Vendor Import Wizard, and will record when the user confirms the option to 'Confirm DELETION of ALL existing vendors'. [Build: 3.32] | ||
| 133. For Access backend users, When importing products into an existing product database, a backup is always made of the product database. The backup file name will have the same base name as the product database file but with a .bxx extension. This backup feature now also happens for SQL backend users but is implemented a little differently. The backup is a tab delimited text file backup of the database and will be saved to a file with the same base name as the product database SQL table name like "Products_OurProducts" and will have a .bxx file extension. This is not a replacement for proper full SQL database backups, but rather an extra resource in case accidental changes are applied to a product database. [Build: 3.32] | ||
| 134. Kaseya BMS v5.0.0 is now supported!
[Build: 3.32] | ||
| 135. For Autotask users, if the contact address is empty, the company address will be used when doing a search on the Lookup window. [Build: 3.32] | ||
| 136. For Autotask users, there is a new 'QuoteValet' tab in the Autotask Setup. There are new options that control what QuoteValet Links to attach to the Autotask Opportunities. There are options for 'Attach QuoteValet EXTERNAL Viewing Link', 'Attach QuoteValet INTERNAL Viewing Link', and 'Attach QuoteValet Sales Rep Facing Page Link'. By default, the option to attach all of the links will be set for backwards compatibility. [Build: 3.32] | ||
| 137. For Autotask users that also have a QuoteValet subscription, the QuoteValet Acceptance Package can automatically be uploaded and attached to the Autotask Opportunity when the QuoteValet quote is accepted and converted to an Order in QuoteWerks. This setting is on the QuoteValet tab on the Autotask setup in QuoteWerks. [Build: 3.32] | ||
| 138. For SugarCRM users, SugarCRM version 11.0 is now supported. [Build: 3.32] | ||
| 139. For SugarCRM users, if the contact address is empty, the company address will be used when doing a search on the Lookup window. [Build: 3.32] | ||
| 140. For Tech Data customers, using the "Import Tech Data SAP Quote (JSON)" feature, when importing the Tech Data quote that contains Sub Items that are not a "Zero Dollar SKU", will be displayed in the preview and added to the quote in QuoteWerks. [Build: 3.32] | ||
| 141. ConnectWise 2021.1 is now supported! [Build: 3.25] | ||
| 142. GoldMine 2021.1 is now supported! [Build: 4.06] | ||
| 143. For Maximizer CRM users, Maximizer CRM 2021 R2 is now supported. [Build: 4.06] | ||
| 144. For GoldMine users, there is now an option to have QuoteWerks close the GoldMine opportunity as Won for you when completing the forecasted sale to a completed sale. At that time you can specify the Status and Win reason. Similarly, when converting to a Lost Sale, there is now an option to have QuoteWerks close the GoldMine Opportunity as Lost. [Build: 4.06] | ||
| 145. For GoldMine users, when manually creating a GoldMine Opportunity through the QuoteWerks "Create/Update Forecasted Sale" window or the "Create/Update Completed Sale" window, if you create a new GoldMine Opportunity, but then choose to cancel the creation of the Forecasted or Completed Sale respectively, you will be warned that you will be orphaning the GoldMine Opportunity you just created, it will not be linked to the QuoteWerks document. [Build: 4.06] | ||
| 146. For GoldMine users, when the SoldTo is already linked to contact in GoldMine and you try to link a different GoldMine contact to the SoldTo, you will now receive a warning that if you do this, it will orphan an existing records in GoldMine related to this SoldTo (like linked documents, follow up calls, forecasted sales, etc). [Build: 4.06] | ||
| 147. For GoldMine users, on the Forecasted/Completed Sales tab of the GoldMine Integration Setup window there is now a "Update Goldmine Opportunity Name" option. When selected, the GoldMine Opportunities are renamed when the docno or docname changes. [Build: 4.06] | ||
| 148. For GoldMine users, on the complete sale window the opportunity status will now default to Won or Lost depending upon the action. [Build: 4.06] | ||
| 149. For GoldMine users, if you save changes to an order after the Completed Sale was created, the GoldMine Opportunity Closed amount will now be updated. [Build: 4.06] | ||
| 150. For Zoho CRM users, when searching for a contact, if selecting a contact and the contact address is empty, the address will be filled out with the address from the Account. [Build: 4.06] | ||
| 151. For HubSpot users, you can now select a Deal Pipeline on the HubSpot Deal window. [Build: 4.06] | ||
| 152. For HubSpot CRM users, you can now create a new HubSpot CRM Company 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 HubSpot CRM. 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: 4.06] | ||
| 153. For HubSpot users, you can now select a default Deal Pipeline on the Deal tab in the HubSpot Integration Setup window. [Build: 4.06] | ||
| 154. The Product Import wizard now displays an estimated number of total records to be imported and also displays the estimated remaining time until import completion. [Build: 4.06] | ||
| 155. For ConnectWise Manage users, when retrieving recurring products from ConnectWise Manage, there is a new setup option to choose if the First Payment should be included in the Document Totals. In the QuoteWerks ConnectWise Manage setup, this option is found by navigating to the Product Tab and then to the Product List sub-tab. There check box is named "First Payment Included in Document Totals for Recurring Products". [Build: 4.06] | ||
| 156. When editing the cell contents in the Document Items grid, pressing CTRL+RIGHT ARROW will move the cursor to the beginning of the next word and similarly, pressing CTRL+LEFT ARROW will move the cursor to the beginning of the previous word. If the entire contents of the cell is selected, this will not happen. [Build: 4.06] | ||
| 157. On the Misc.General tab of the Tools->My Preferences window, there is now a new option of "Select contents when clicking in grid cell". When this set and you click in a grid cell on the Document Items tab, the entire contents of the cell will be selected. If this is not set, the cell contents will not be selected, and the cursor will appear in the cell at the position you clicked. [Build: 4.06] | ||
| 158. When Saving a PDF file from the File->Print window, when choosing the option to "Attach to CRM", there is now an option to set the Title for the CRM file attachment. The default Title will be the DocName. [Build: 4.06] | ||
| 159. From the Print Preview window, when clicking on the "Attach to CRM" toolbar button, there is now an option to set the Title for the CRM file attachment. The default Title will be the DocName. [Build: 4.06] | ||
| 160. For QuoteValet users, there is now an option on the General tab of the QuoteValet Setup window, for "[] On QuoteValet Page, Auto-Update Totals on changes". [Build: 4.06] | ||
| 161. Real-time Pricing and Availability is now available for UK Distributor ProVu Communications ( www.provu.co.uk ) if you have an account with this distributor and credentials are entered into QuoteWerks. Also, this real-time pricing is displayed on the Etilize Panel. [Build: 4.06] | ||
| 162. Added macro &PaymentOptions_SelectedType. Use this macro to return the Type of payment option that is selected. [Build: 4.06] | ||
| 163. Added macro &PaymentOptions_LeaseApplicationID. This macro is useful for GreatAmerica Financial customers that submit Lease Applications via QuoteWerks. Use this macro to return the Application ID returned from GreatAmerica when submitting a Lease Application.
[Build: 4.06] | ||
| 164. On the Synchronization tab of the Tools->Options menu, if the "Look for synchronized data in dtf files" is checked, but you have not linked a contact/company to the quote, the "[] Create/update linked document" checkbox on the save window will not be checked and disabled like it normally would be if the quote is linked to a company/contact. [Build: 4.06] | ||
| 165. On the SoldTo/ShipTo tab toolbar, in addition to the "View Contact in Contact Manager" button there is now a "View Company in Contact Manager" button. [Build: 4.06] | ||
| 166. On the Links tab of the Quote WorkBook in the Auto-Links area, in addition to the "View Contact in CRM", there is now an additional link to "View Company in CRM".
[Build: 4.06] | ||
| 167. 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. [Build: 5.10] | ||
| 168. 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. [Build: 5.10] | ||
| 169. 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. [Build: 5.10] | ||
| 170. 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. [Build: 5.10] | ||
| 171. 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.
[Build: 5.10] | ||
| 172. SugarCRM 11.1 is now supported! [Build: 5.10] | ||
| 173. Act! v24 is now supported! [Build: 5.10] | ||
| 174. ConnectWise 2021.2 is now supported! [Build: 4.06] | ||
| 175. Sage 50 Accounting 2022 (Peachtree) is now supported! [Build: 5.12] | ||
| 176. Act for Web v24 is now supported!
[Build: 5.12] | ||
| Misc Features - Version 5.6 | ||
| 1. The grid toolbar on the Document Items tab of the Quote WorkBook has been moved below the "Totals for All items" frame. [Build: 1] | ||
| 2. On the Product->Lookup window, right click menu, renamed menu "Copy to Folder..." to "Associate item(s) with Folder..." [Build: 1] | ||
| 3. In the Product Data Source wizard, renamed the "Security" step to "Set Access Rights" [Build: 1] | ||
| 4. For ConnectWise Manage users with ConnectWise Manage 2020.3 and higher, clicking on the [Test] Button on the ConnectWise Manage Setup in QuoteWerks for the Credentials would return a false negative for 'Cannot Access ConnectWise Report Names'. This relates to ConnectWise ticket#13866467. If this issue is encountered, QuoteWerks will query ConnectWise Manage for a list of entities that the API user does not have access to. [Build: 1] | ||
| 5. For QuoteWerks Web users, the siteboot.in file is now uploaded to QuoteWerks Web during upload synchronization. [Build: 1.01] | ||
| 6. In the Add Item Assistant, the "Under" dropdown now lists the Sections and Headings like "Family Room (Section)" vs "Section: Family Room" so that you can press a key to quickly seek to the letter of the section you want to find.
[Build: 1.09] | ||
| 7. Removed support for SalesLogix/Infor CRM version 5.0, 5.2, 6.0, 6.1, 6.2, and 7.0. [Build: 2.07] | ||
| 8. For SugarCRM users, when doing a contact search for the fields name, contact first name, contact last name, and account name, it will now be a "Contains" search. [Build: 2.07] | ||
| 9. For SugarCRM users, the SugarCRM QuoteWerks forms were moved to .NET framework. [Build: 2.07] | ||
| 10. Implemented better error messaging for when credentials not entered for OpenIceCat [Build: 2.07] | ||
| 11. For Tech Data Users, implemented better error messaging when an unknown Tech Data Excel file import error is encountered. [Build: 2.07] | ||
| 12. When an order type document is open in QuoteWerks and you open the Purchasing window, the "Currently Open Order" scope will be set in the filter on the Purchasing tab. When this is set, and the [Place Online Order->Create PO] button is clicked, the PONumber for the online order would default to, for example, POAAAO1244, where "AAAO1244" was the document number that is currently open. Now, it will default to being empty. This change makes this now consistent with the behaviour when selecting items from multiple order documents where the PONumber starts out blank and then you press the [...] button to obtain the next PONumber. Under the Utilities->Vendor Maintenance when editing a vendor you can specify a "Vendor PO Prefix/suffix" field. It can be a maximum of 3 characters, so for "Tech Data" you can specify "TD" and then the auto generated next po number for a Tech Data online order would be, for example, 20-1534TD. If QuoteWerks is configured to export purchase orders to QuickBooks, Peachtree, or ConnectWise, this same PO number will be used when creating the purchase order in the accounting software. You will want to reset the unique numeric sequence each year and this can be done on the Installation tab of the Tools->Options menu. The short nature of the PO number format takes into account that QuickBooks has a very small 11 character max po number and Ingram Micro being the next at 18 characters. [Build: 2.07] | ||
| 13. The Vendor table now has a RecGUID field. [Build: 3.19] | ||
| 14. For SugarCRM users, the Product ID Mapping fields were duplicated in the combo dropdown control on the SugarCRM Setup window. [Build: 3.19] | ||
| 15. The [Edit Output] button has been removed from the Management Reports window. [Build: 3.19] | ||
| 16. Startup time was decreased by optimizing the LoadSchemas process.
[Build: 3.19] | ||
| 17. When in demo mode, the sample quote will be automatically opened. [Build: 3.22] | ||
| 18. For SugarCRM users, the search textbox is now focused after selecting a search option on the Lookup window. [Build: 3.25] | ||
| 19. For HubSpot CRM users, the search textbox is now focused after selecting a search option on the Lookup window. [Build: 3.25] | ||
| 20. QuoteWerks was updated with ShareWerks rebranding to ClarityWerks. [Build: 3.25] | ||
| 21. The QuoteWerks Demo Sample Quote was updated. [Build: 3.26] | ||
| 22. When a Demo/Trial expires, there is now a prompt to request an extension. [Build: 3.32] | ||
| 23. The Demo version no longer has a limit on the number of line items, but is still limited to 8 quotes, and a 30 day period. [Build: 3.32] | ||
| 24. When a Demo/Trial expires, there is now a prompt to request an extension. [Build: 3.32] | ||
| 25. Renamed DocumentHeaders and DocumentItems ExtraXXX fields to replace the word "Extra" with "Addon", and the ExtraLogic01 field was dropped. These "AddOn" fields are now available in print layouts and reports, also macros like &DH_AddOnText01. These fields are accessible through the QuoteWerks API. These fields are not visible anywhere on the quote, they are meant to be a behind the scenes data storage area for developers. [Build: 4.06] | ||
| 26. The 'Utilities->Merge Remote Documents' menu was renamed to 'Merge Document Transport Files". Also the 'Utilities->Rebuild CM Transport Files' menu was renamed to 'Rebuild Document Transport Files'. [Build: 4.06] | ||
| 27. For the last 20 years, QuoteWerks has mostly relied upon the DocumentHeaders.SoldToCMAccountNo field to store the linked CRM contactID value in. Over the years as we have supported newer and different CRMs, it required that we also stored a SoldToCMCompanyRecID value which contained the record id of the CRM Company/Account. This SoldToCMCompanyRecID value has been stored in xml in the DocumentHeaders.DynamicStorageDH field. Additionally for salesforce.com and GoldMine the data stored in these fields is actually reversed. Changes have been made in this build. The DocumentHeaders.SoldToCMAccountNo field has been renamed to DocumentHeaders.SoldToCMContactRecID. There is now a DocumentHeaders.SoldToCMCompanyRecID field. There is now a DocumentHeaders.SoldToCMSecondaryContactRecID field. These same changes were applied to the "ShipTo" and "BillTo" counterpart fields. The "reversed" data for GoldMine and Salesforce.com has been corrected.
[Build: 4.06] | ||
| 28. The MS CRM integration to version of MS CRM earlier than MS CRM 6.0 has been discontinued. [Build: 4.06] | ||
| 29. For Kaseya BMS users, when Creating/Updating a BMS Opportunity, if the list of available opportunities returned from Kaseya BMS for the Account exceeds 100, a label will appear as a visual indicator. [Build: 4.06] | ||
| 30. Activated beta testing support for SugarCRM 11.1 [Build: 4.06] | ||
| 31. For users rehosted to SQL, when importing products into an existing product database, the automatic backup of the existing data will be skipped if the product database has more than 150,000 records. Unfortunately, when a product database table contains this many records, it takes a long time to export all the data out, and the usual method of returning all records and then writing them all out causes "out of memory" issues. As a reminder, this automatic backup is not a replacement for proper full SQL database backups, but rather an extra resource in case accidental changes are applied to a product database. Normally, the backup is a tab delimited text file backup of the database and will be saved to a file with the same base name as the product database SQL table name like "Products_OurProducts" and will have a .bxx file extension. [Build: 4.06] | ||
| 32. There is now an [Event Viewer] button under the Utilities->View Logs window [Build: 5.10] | ||
| 33. SYNNEX moved/renamed one of their warehouses from Grove City, OH to Columnbus, OH. Applied necessary changes. [Build: 5.10] | ||
| 34. Activated beta testing support for Sage 50 Accounting 2022 (Peachtree) [Build: 5.10] | ||
| 35. On the Send Email window, when selecting a file to attach, the file name and path were being forced to lower case characters. [Build: 5.10] | ||
| 36. Activated beta testing support for ACT! for Web version 24. [Build: 5.12] | ||
| 37. The Act installer helper GetAct64bitInfo.exe is now only installed when the user chooses to install Act.
[Build: 5.12] | ||
| Fixes - Version 5.6 | ||
| 1. For ConnectWise Manage Users, when using the QuoteLink to bring the ConnectWise Opportunity with Line Items into QuoteWerks, if the mapped QuoteWerks field to match to the ConnectWise Product ID was the ManufacturerPartNumber, the imported product would incorrectly have the ConnectWise Manufacturer Part Number rather than the Product ID. This would cause issues when writing back to ConnectWise. The Manufacturer Part Number in QuoteWerks for these instances will now have the Product ID. [Build: 1] | ||
| 2. For ConnectWise Manage users, in the ConnectWise Manage Setup within QuoteWerks, the Item Type Mappings for Map Bundle "IsPhasedProject" would incorrectly set the 'Is Serialized' Mapping in the setup and the 'IsPhasedProject' mappings would not be saved. [Build: 1] | ||
| 3. For QuickBooks Online Users, when creating a new customer in QuickBooks Online, the new customer would not be created and the following error would be returned. "A business validation error has occurred while processing your request Business Validation Error: Tax Exemption Reason should be specified incase customer is marked as not taxable." This is due to a change in QuickBooks Online. [Build: 1] | ||
| 4. For Tech Data USA customers using the Excel Quote Import, there was an issue with one of the Excel Formats where the Unit Price was in a different column. This Excel Quote format is now handled. [Build: 1] | ||
| 5. For MS CRM users, when resaving an opportunity in QuoteWerks after opening and closing the Setup Window, the Name would be blank. [Build: 1] | ||
| 6. For MS CRM users, when updating an MS CRM Opportunity, if the amount being sent over to the MS CRM Opportunity from QuoteWerks was negative and you changed a line item in the quote and the total was still negative, when the MS CRM Opportunity was updated, the MS CRM Opportunity Revenue Amount would change to positive when it should have remained negative.
[Build: 1] | ||
| 7. For Maximizer CRM users, when resaving an opportunity in QuoteWerks after performing a Rename and then setting the 'Update Opportunity Name with Document Name' option, the Objective field would not be renamed. [Build: 1] | ||
| 8. For Zoho users, when resaving a deal in QuoteWerks after performing a Rename and then setting the 'Update Deal Name with Document Name' option, the Name field would not be renamed. [Build: 1] | ||
| 9. For Salesforce users, when resaving an opportunity in QuoteWerks after performing a Rename and then setting the 'Update Opportunity Name with Document Name' option, the Name field would not be renamed. [Build: 1] | ||
| 10. For Act! users, when the 'Write a single summary line item into the Act! Opportunity' option is checked, separate recurring line items were included in the Act! Opportunity. [Build: 1] | ||
| 11. For Act! users, when the 'Write a single summary line item into the Act! Opportunity' option is checked, the Opportunity total did not include the recurring line item amounts. [Build: 1] | ||
| 12. For SugarCRM users, when the 'Write a single summary line item into the SugarCRM Opportunity' option is checked, the Opportunity total did not include the recurring line item amounts. [Build: 1] | ||
| 13. For Autotask users, when the company search value contained an ampersand, any matching companies that have an ampersand would not be returned. [Build: 1] | ||
| 14. For Maximizer CRM users, the create and update deal window will no longer show closed deals in the dropdown [Build: 1] | ||
| 15. When using the Compare feature, if the Compare Assistant was displayed and you searched for a different part number and selected to use it would receive "Error, column key 'Description' not found in ListViewAddSubItem()" [Build: 1] | ||
| 16. When double clicking on a folder in the Product Lookup window, it was not expanding or collapsing the folder. [Build: 1] | ||
| 17. When using the Edit->Apply Multi-Line Changes menu feature, and setting the QtyBase, CostModifier, or PriceModifier field, and a line type like a Section Header is one of many lines selected, it was correctly not applying the change, but it would display a message to that affect for each such line type it encountered. [Build: 1] | ||
| 18. On the Open Document window, when selecting the <Custom> date range for date fields, would receive error about the From date being empty. [Build: 1] | ||
| 19. On the Document Items tab, when clicking on a Grid Toolbar button that had drop down menu, would receive an error that you did not have the rights to perform this default action. [Build: 1.01] | ||
| 20. When hiding Grid Toolbar buttons, the tooltips for the buttons would be incorrect. [Build: 1.01] | ||
| 21. When a document was locked, the QuoteValet Videos area on the Links tab were not disabled. [Build: 1.01] | ||
| 22. If there was a problem loading or creating the new default document on startup, the Most Recently Used File menu when no documents were open would be empty. [Build: 1.01] | ||
| 23. For QuickBooks Desktop users, when exporting as an Estimate and the Cost of a line item was 0.00, the default markup % from the item definition in QuickBooks Desktop would be applied causing the Estimate totals not to match the QuoteWerks document total. [Build: 1.03] | ||
| 24. When setting up a CRM based product data source, if you checked the "Disable the Product Data Source", it would remain enabled. [Build: 1.03] | ||
| 25. For Purchasing users, on the Ordered Items tab, if there was a PO Item with more than 8 serial numbers, the PO Item would not display at all. [Build: 1.03] | ||
| 26. For QuoteValet Auto Reminder notifications options for "Remind SalesRep when document is accepted but NOT PAID after" and "Remind Recipient when document is accepted but NOT PAID after" were cross-linked. [Build: 1.03] | ||
| 27. For QuoteValet users, when setting up Activity Notifications it did not list inactive users, so you could not remove them from notifications once they were set as inactive. [Build: 1.03] | ||
| 28. For Tech Data online ordering users would receive error "MyOrderTrackerResellerEvents maximum length '11' exceeded." [Build: 1.03] | ||
| 29. For API users, when setting the AlternateCurrency like Application.DocFunctions.SetDocumentHeaderValue("AlternateCurrencyIdentifier", "USD", True), the UI of the document was not getting updated. [Build: 1.03] | ||
| 30. For Ingram Micro online ordering users, if you check the option "[] Include End User information (End User information is required in some licensing or warranty orders)." This submits a DTYPE order to Ingram Micro. This type of order does not allow you to specify a warehouse for each line item on the order which was causing an error so the order could not be submitted. [Build: 1.04] | ||
| 31. On the Purchase Orders tab of the Purchasing window, when adding a tracking number for the first time on a Manual PO, it would prompt you to select the ShipVia (Carrier), but if you cancelled entering the tracking number, then the ShipVia would remain even after you deleted the only tracking number. [Build: 1.04] | ||
| 32. For D&H Online Ordering users, in order status updates, D & H started returning the Carrier as "US Postal" instead of "USPS". [Build: 1.04] | ||
| 33. For Zoho CRM users, when creating a Deal, the DTF file was not attached. [Build: 1.04] | ||
| 34. On the Set File Access rights window, when choosing the De-Select All button would receive runtime error 13. [Build: 1.04] | ||
| 35. When the "Enable Indivudual Resource Security" was enabled and the logged in user has the security right of "MasterRights or "NonMasterRightsUser_CanAdministerDeliverables", Print Layouts would be listed that should not. [Build: 1.04] | ||
| 36. For Tech Data users, if a Realtime P&A request returned that this item was not orderable ("can't order"), then the realtime price would not be displayed.
[Build: 1.04] | ||
| 37. When editing a layout file and choosing Insert->Field menu, and choosing "Document Items" you would receive errors about all of the DocumentItems macro fields that begin with the "&" character. [Build: 1.09] | ||
| 38. For ConnectWise Manage Users, in the ConnectWise Manage Setup, the Default Taxable Status for Products could be blank. Depending on the configuration, the user may or may not have had the blank drop down. This resolves the issue. [Build: 1.09] | ||
| 39. For Great America users, "Error Submitting Lease Credit Application: Error 1001 - Invalid DealerKey was provided". [Build: 1.09] | ||
| 40. For Zoho users, the DataLink action of RetrieveShipTo and RetrieveBillTo were returning blank data. You will have to re-select the ShipTo/BillTo contact for this fix to take effect. [Build: 1.09] | ||
| 41. For Kaseya BMS Users, when creating or updating an Activity in QuoteWerks for Kaseya BMS, if the Cancel button was clicked, the Activity would still be created or updated. [Build: 2.07] | ||
| 42. For QuickBooks Online users, when exporting a Purchase Order to QuickBooks Online and using a Macro for the QuickBooks Item Name, the macro was not being evaluated and QuoteWerks would attempt to create a new QuickBooks Online Item with a blank Item Name.
[Build: 2.07] | ||
| 43. For SugarCRM users, when a Contact was selected for the SoldTo instead of an Account, when you saved the quote, an error would be displayed, and the DTF file would not be saved. [Build: 2.07] | ||
| 44. For SugarCRM users, the 'Test' button on the Contact Manager Setup window was not working correctly for the URL. [Build: 2.07] | ||
| 45. For SugarCRM users, the DataLink would not work for a Contact type if no Account was associated with it. [Build: 2.07] | ||
| 46. For Salesforce users, when a user without login credentials clicks on a "View" link on the Links tab of the Quote WorkBook, they would receive several login errors. [Build: 2.07] | ||
| 47. For Salesforce users, multiline field values in Salesforce were coming over as a single line when using DataLink. [Build: 2.07] | ||
| 48. For MS CRM users, you were not able to Authenticate a different MS CRM user if you went to that user's preferences through the User Maintenance window. [Build: 2.07] | ||
| 49. For Maximizer CRM users, when creating an Opportunity, the DTF file was not getting attached. [Build: 2.07] | ||
| 50. When placing an Online Order, the ShipTo information was not getting saved into the QuoteWerks Purchase Order. [Build: 2.07] | ||
| 51. QuoteWerks was only supporting a maximum of 1000 windows users for Active Directory login. [Build: 2.07] | ||
| 52. For Goldmine users, if when searching for a contact, if "User Contact currently displayed in Goldmine" was selected, any changes to the "Also Display secondary Contacts" checkbox would not be remembered. [Build: 2.07] | ||
| 53. If a user with the Misc Access right CannotManuallyModifyFieldValue:DI_ManufacturerPartNumber set, uses the ManufacturerPartNumber column drop down list on the Document Items tab of the Quote WorkBook, then types changes into that ManufacturerPartNumber cell, and then tabs away from the cell would receive "Run Time Error '381': Invalid property array index" error. [Build: 2.07] | ||
| 54. For MS CRM users, if a '/' was not at the end of the Server/URL field on the Contact Manager MS CRM Setup window, users would receive an error if there was no activity with MS CRM for over an hour when attempting to re-connect. [Build: 2.07] | ||
| 55. For Zoho CRM users, after pulling in a contact and a Zoho Datalink is present, there would be an error. [Build: 2.07] | ||
| 56. If no Open Icecat credentials have been specified, the Tools->Get Real-time Product Content menu was visible. Same for the Product Lookup right click menu for Open Icecat. [Build: 2.07] | ||
| 57. For QuickBooks Desktop users received error about '' MajorVersion. [Build: 2.07] | ||
| 58. When sending an email, in rare cases QuoteWerks would become non-responsive. [Build: 2.07] | ||
| 59. For QuickBooks Online users, the Tax Code for "Convert Grouped Items to a Single Item" was not used when sending a Grouped Item to QuickBooks Online. The Single Item representation of the Group Header Item would always be a non-table status. [Build: 2.07] | ||
| 60. For Zoho CRM users, if an administrator was setting up a user and performed the Zoho [Manage User Access to Zoho] function, then that users authentication would be saved for the currently logged in administrator. [Build: 3.19] | ||
| 61. When using the "Copy To" feature on the Sold to / Ship to tab to copy contact details, the CompanyRecID field was not being copied over which would cause problems when integrating with Zoho, salesforce.com, MS CRM and SugarCRM. [Build: 3.19] | ||
| 62. For SugarCRM users, some users were receiving a "Nullable object must have a value." error when attempting to create or update an Opportunity. [Build: 3.19] | ||
| 63. For QuickBooks Online users in the UK, the Shipping Amount did not have a tax code applied which would cause an error for some users. The following error would be returned "A business validation error has occurred while processing your request Business Validation Error: Please select a tax code for the shipping line.". [Build: 3.19] | ||
| 64. For QuickBooks Online users, when creating a Purchase order, the Ship To Contact was not being populated on the PO. [Build: 3.19] | ||
| 65. For ConnectWise Manage Users, when creating a purchase order in ConnectWise manage with multiple line items, the following error could be returned: 'The line number '1' already exists [ resource: purchaseOrderLineItem - field: ]". This is a timing issue in the ConnectWise Manage API "/procurement/purchaseorders/{id}/lineitems/count" endpoint. QuoteWerks development has implemented a workaround to address the ConnectWise issue documented in ConnectWise tickets 14460914 and 13694355. If ConnectWise fixes the issue, the workaround will not be used in favor of a proper method. [Build: 3.19] | ||
| 66. For ConnectWise Manage Users, when creating a Sales Order in ConnectWise when converting an Opportunity to 'Won', the Sales Order in some cases would not be created even when items were on the ConnectWise Opportunity. This is a timing issue in the ConnectWise Manage API "/procurement/products/count" endpoint. QuoteWerks development has implemented a workaround to address the ConnectWise issue documented in ConnectWise ticket 12798352 that was submitted to ConnectWise in 2019 and is still open. If ConnectWise fixes the issue, the workaround will not be used in favor of a proper method. [Build: 3.19] | ||
| 67. For Gmail users, when authenticating with Gmail for Email oAuth, the option to allow authentication was disabled in the browser for some users. [Build: 3.19] | ||
| 68. For SugarCRM users, when attempting to create or update an Opportunity and custom Sales Stage items existed, would receive error. [Build: 3.19] | ||
| 69. For Tech Data customers, using the "Import Tech Data SAP Quote" feature, when importing the Tech Data quote, the error "Conversion from String "$N/A" to type 'Double' is not valid." could be received in some circumstances and the quote would not be imported into QuoteWerks. [Build: 3.19] | ||
| 70. For Zoho users, when saving and using a DataLink to populate the Deal description, users would receive an error. The description field along with many others are restricted fields that can not be updated through Datalinking since QuoteWerks already updates them. [Build: 3.19] | ||
| 71. For Autotask users, when using the field &TaxRate in the DataLink and there were multiple tax categories for a tax region, the values were added together. [Build: 3.19] | ||
| 72. For SugarCRM users, sales stage was not being set on the Opportunity or Revenue Line Items [Build: 3.19] | ||
| 73. For SugarCRM users, the sales stage was disabled for some users on the Create/Update Opportunity window. [Build: 3.19] | ||
| 74. On the PO Created window, the PO Number was not displaying if a Ingram Micro, SYNNEX, D&H, or Dell Online order was placed. [Build: 3.19] | ||
| 75. When the option for "Warn if document is UNSAVED when printing/emailing." was set, you would not be prompted if you were on the Preview window and choose to Email, Print, or Attach to CRM. [Build: 3.19] | ||
| 76. When performing an action, for a document that has never previously been saved, when prompted to save, and choosing to cancel, in certain conditions, it would continue as if you selected NO. [Build: 3.19] | ||
| 77. On the Print window, if choosing to email, but then cancelling instead of sending the email, the Print window could close, even if the "Auto-close Print window after a print, preview, peer review, approval, or quotevalet operation." option was set. [Build: 3.19] | ||
| 78. The Email Template macro '&DH_LocalTaxRate' was being rasterized as the tax amount with the word "rate" appended to the end. [Build: 3.19] | ||
| 79. For Maximizer CRM users, when emailing a quote from QuoteWerks that another user created, a user could receive an error message when the email history note was being created in Maximizer CRM. [Build: 3.19] | ||
| 80. For UPS realtime rates users, UPS changed their server API URL causing error "Error: ErrorCode: Function: GetShippingRateUPS" [Build: 4] | ||
| 81. In the management reports, for a DocumentItems table, many "&" macro fields were listed as available which should not have been including &LineNumberXXX fields. [Build: 4] | ||
| 82. For UPS realtime rates users, UPS changed their server API URL causing error "Error: ErrorCode: Function: GetShippingRateUPS" [Build: 3.20] | ||
| 83. In the management reports, for a DocumentItems table, many "&" macro fields were listed as available which should not have been including &LineNumberXXX fields. [Build: 3.20] | ||
| 84. For Kaseya BMS users, when searching for Kaseya BMS products from the Product Lookup window in QuoteWerks, if the search parameter(s) contained special characters (like ‘#’ or ’%’ as examples), an error would be returned from Kaseya BMS containing “There is an unterminated string literal”. [Build: 2.07] | ||
| 85. For MS CRM users, a change in v5.6 build 2.07 stopped the DataLink from working. [Build: 3.19] | ||
| 86. When uploading a quote to QuoteValet for Peer Review, if a peer selected some options on the quote while reviewing the quote, then the sales rep opened the quote and changed the options back to the defaults the sales rep wanted the customer to see, when they clicked on File->Print to attempt to re-upload the quote to QuoteValet, the peer's changes would be applied back to the quote, making it impossible for the sales rep to change it back. [Build: 3.22] | ||
| 87. From the purchase Orders tab of the Purchasing window, the right click "Email PO..." feature would sometimes cause the html code to appear in the email signature area. [Build: 3.22] | ||
| 88. The default E-mail signature html code had a problem in it that would cause rasterizing problems in certain conditions. [Build: 3.22] | ||
| 89. In the Event Viewer, clicking on the EventOn column heading to sort, was not sorting correctly. [Build: 3.22] | ||
| 90. If 'Check for In-Use Documents' is selected on the Installation tab of the Tools->Options menu, and if a document is opened in QuoteWerks, and takes sufficiently long to fully load the document (slow network, large quote), while the quote was opening and before it has fully loaded, if another user opens the quote at the same time, they could open an editable version of that quote, which can cause duplication issues with Convert to Order and 'Winner take all' issues with saving. [Build: 3.22] | ||
| 91. For Amazon Business Online Ordering users, when creating the Online Order, there is now a new "Amazon PO#" field in addition to the QuoteWerks PO Number field. With this, you can leave the QuoteWerks PO number blank (which is allowed if using QuickBooks, and the option to retrieve PO number from the QuickBooks created PO is set), but you will have to fill in the "Amazon PO#". Previously without the distinction of these two different fields, you could not use the QuickBooks PO option to retrieve the PO number from QuickBooks. [Build: 3.22] | ||
| 92. When creating a QuoteWerks PO, if you left the QuoteWerks PO Number blank (which is allowed if using QuickBooks, and the option to retrieve PO number from the QuickBooks created PO is set), you might be told that the PONumber '' was already in use. [Build: 3.22] | ||
| 93. The Email Template macro '&POI_CustomerPONumber' was being rasterized as the &POI_Customer value with the word "PONumber" appended to the end. [Build: 3.22] | ||
| 94. For script users, if there was a script set in the BeforeSaveDocument event, and the auto-save option was enabled, and the auto-save period of time had elapsed and the next user input was to click the [Save] toolbar button, it would result in the document being saved twice causing issues including a duplicate document number in two different documents. [Build: 3.22] | ||
| 95. When customizing the Document Items tab columns, any change to the title of columns would not be seen in areas were the column field name was listed with its customized title like in the Find window. Issue was introduced in v5.6 build 1.01. [Build: 3.22] | ||
| 96. For Dell Premier Punchout Users, if the CostModifier was set by default in QuoteWerks (Tools->Options), then when importing a Dell configured punchout quote, the Cost in QuoteWerks would use the calculated Cost based on the CostModifier rather than the cost returned from Dell. The CostModifier is now ignored when using Dell Punchout. [Build: 3.22] | ||
| 97. For QuoteValet users, in the QuoteValet Dashboard, if the user is in a region that uses the comma as a decimal separator, and if the decimal value of the quote is a non-zero amount (€1.387,00 vs €1.387,21), the value of the quote would be displayed multiplied by 100. If the value of the total has no decimals, then it would display properly. [Build: 3.22] | ||
| 98. For ConnectWise Manage users, when saving a new Opportunity to ConnectWise as a Won or Lost Document (skipping a document conversion), the Default Document Status for the "Status' setup in QuoteWerks was not used. This did not affect conversion to an Order or Invoice. [Build: 3.22] | ||
| 99. For SugarCRM users, the home number was being used instead of the office phone number when doing a contact search on the Lookup window. [Build: 3.25] | ||
| 100. For SugarCRM users, doing a phone lookup search would cause an error if no results were found. [Build: 3.25] | ||
| 101. If 'Check for In-Use Documents' is selected on the Installation tab of the Tools->Options menu, when opening a document, if it was determined that there was a dtf file that contained newer information, and needed to update the document in the database, would receive a message that the document was already in use by the logged in user. Issue introduced in v5.6 build 3.22. [Build: 3.25] | ||
| 102. In Paste Special, if both the UnitPrice and PriceModifier columns were mapped, the PriceModifier field would not import. Issue introduced in v5.6 build 1.09. [Build: 3.25] | ||
| 103. In certain circumstances, the small message status display would stay open. [Build: 3.26] | ||
| 104. For HubSpot CRM users, on the Deal window, if the data in a combobox is too wide to display in the combo box, when you click the dropdown list, the drop down list will be wider to allow you to see the full text. [Build: 3.36] | ||
| 105. For Zoho CRM users, custom DataLink field names that contained a parenthesis "(" would throw an error when attempting to review or save the value. [Build: 3.36] | ||
| 106. For Zoho CRM users, on the Deal window, if the data in a combobox is too wide to display in the combo box, when you click the dropdown list, the drop down list will be wider to allow you to see the full text.
[Build: 3.36] | ||
| 107. For salesforce.com users, searching with an apostrophe (') would cause an error on the Lookup window. [Build: 3.36] | ||
| 108. For salesforce.com users, if a salesforce.com instance does not support PriceBooks, the setup window would error and not load in QuoteWerks. [Build: 3.36] | ||
| 109. For salesforce.com users, the description control was cut off on the Opportunity window if the salesforce.com instance did not support Multiple Currency and Pricebooks. [Build: 3.36] | ||
| 110. For salesforce.com users, on the Opportunity window, if the data in a combobox is too wide to display in the combo box, when you click the dropdown list, the drop down list will be wider to allow you to see the full text.
[Build: 3.36] | ||
| 111. For MS CRM users, the contact was not being written into an Opportunity. [Build: 3.36] | ||
| 112. For MS CRM users, on the Opportunity window, if the data in a combobox is too wide to display in the combo box, when you click the dropdown list, the drop down list will be wider to allow you to see the full text.
[Build: 3.36] | ||
| 113. For SugarCRM users, when converting a quote in QuoteWerks, the close date was not using Today's date. [Build: 3.36] | ||
| 114. For SugarCRM users, on the Opportunity window, if the data in a combobox is too wide to display in the combo box, when you click the dropdown list, the drop down list will be wider to allow you to see the full text. [Build: 3.36] | ||
| 115. For ConnectWise Manage Users, when Converting a Quote to an Order and winning the Opportunity, the QuoteWerks Linked Document in ConnectWise would not be deleted when saving. The end result would be an extra DTF file for the original quote on the Attachments tab on the ConnectWise Manage Opportunity. [Build: 3.36] | ||
| 116. For ConnectWise Manage Users, when converting a Quote to an Order and wining the Opportunity, if the "All Items except Agreement" option was selected under Agreement, the error "Error (-2147467261) Value cannot be null. Parameter name: source" would be returned and the Agreement and any other conversions would not be made from the ConnectWise Opportunity like tickets and sales order. [Build: 3.36] | ||
| 117. For ConnectWise Manage Users, when saving a Customer PO number greater than 25 characters back to the ConnectWise Opportunity, an error would be returned. The PO Number will now be truncated to 25 characters if it exceeds 25 characters. [Build: 3.36] | ||
| 118. When doing a contact import, and trying to import the contact's name, if you mapped the "First Name" and "Last Name" fields, it would work, but not if you mapped the "Contact" mapping. [Build: 3.36] | ||
| 119. When copying and then Paste Appending a product from one native product database to another, the InternalPartNumber field would not be paste Appended.
[Build: 3.36] | ||
| 120. For MS CRM users, the contact was not being written into the Opportunity. [Build: 3.36] | ||
| 121. For HubSpot CRM users, the first 100 existing Deals were being shown on the Create/Update Deal window in QuoteWerks instead of all the Deals that were created by the contact. [Build: 3.36] | ||
| 122. For SugarCRM users, non professional versions of SugarCRM would not have the Opportunity window appear when saving an Opportunity in QuoteWerks. [Build: 3.36] | ||
| 123. For Autotask users, duplicating a quote and then uploading to QuoteValet would the QuoteValet links in the Autotask opportunity. [Build: 3.36] | ||
| 124. For ConnectWise users, duplicating a quote and then uploading to QuoteValet would the QuoteValet links in the ConnectWise opportunity. [Build: 3.36] | ||
| 125. For SugarCRM users, no account results were found on the Lookup window when 'Also display Account Contacts' was unchecked. [Build: 3.32] | ||
| 126. For SugarCRM users, account and contact datalinking in QuoteWerks could return an error in SugarCRM version 6.5. [Build: 3.32] | ||
| 127. For SugarCRM users, the expected close date was not being populated when resaving or closing an Opportunity in QuoteWerks. [Build: 3.32] | ||
| 128. For Tech Data customers using the "Import Tech Data SAP Quote (JSON)" or "Import Tech Data CCW Quote (JSON)" features, Tech Data made a breaking change to the JSON object which would return a "400: Bad Request" Error.
[Build: 3.32] | ||
| 129. When sending an email, if the TO list ended with an errant ";" or "," then the email would not be sent to any of the CC or BCC recipients. [Build: 3.32] | ||
| 130. After creating a Manual PO for 'Current Order' in the purchasing window, after you clicked 'Close' on the confirmation window, the Purchasing window would be left behind the main QuoteWerks window. [Build: 3.32] | ||
| 131. For SQL backend users, when running a Management Report on a product database would receive an error about the 'PRODUCTS' table was not included in the filter expression. [Build: 3.32] | ||
| 132. For Goldmine users, when converting a quote to an order and converting the forecasted sale to a completed sale, if the forecasted sale was linked to an Opportunity, the amount would still be displayed in the opportunity as forecasted. [Build: 4.06] | ||
| 133. For Zoho CRM users, when saving a new quote with 'Offline' selected on the save dialog, if a contact wasn't pulled from Zoho, a Run-time error '91' would occur. [Build: 4.06] | ||
| 134. For SugarCRM users, if a comma is used as a decimal separator, the value of the opportunity is multiplied by 100. [Build: 4.06] | ||
| 135. For SugarCRM users, the call status of "Planned" was showing instead of "Scheduled" on the SugarCRM Call form dropdown control. [Build: 4.06] | ||
| 136. For Autotask users, a QuoteWerks Datalinked Autotask Quote Item field could have the same value set as the previous QuoteWerks line item. [Build: 4.06] | ||
| 137. When running a management report with the option to export the data would receive an error like "Error opening recordset in ConnOpenRecordset():
QuoteWerks trapped Error (-2147217900) Incorrect syntax near the keyword 'ORDER'."
[Build: 4.06] | ||
| 138. Under the Tools->My Preferences menu, When pasting your password into the Change password box (versus typing it in) would receive error that your password was not valid. Also if you tab back into a password box that has data in it, it will be auto-selected. [Build: 4.06] | ||
| 139. When editing User Preferences through the Utilities->User Maintenance menu, the "New Document Default Template" would always get changed to the value for the logged in user. [Build: 4.06] | ||
| 140. When importing a Text file into the QuoteWerks Contact Database, and mapping the First and Last name fields, this information was not getting imported. [Build: 4.06] | ||
| 141. Setting the default order/invoice literature along with the "Apply this literature to documents that are converted to an Order/Invoice" was not working. [Build: 4.06] | ||
| 142. When Importing Contacts, if starting the import by loading an Import Template, the Line Delimiter and sample data was not getting set. [Build: 4.06] | ||
| 143. For Kaseya BMS users, when Creating/Updating a BMS Opportunity, the Drop-down list of available BMS Opportunities to select from included all Kaseya BMS Opportunities associated with the Account. Only Opportunities in the Kaseya BMS Pipeline will be returned. The Pipeline Opportunities are equivalent to Open Opportunities (Not Lost or Won). [Build: 4.06] | ||
| 144. For QuickBooks Online Users, the available Tax Rate list would be blank in some cases when using a non-period decimal separator such as a comma. [Build: 4.06] | ||
| 145. For SYNNEX users, when requesting Real-time Pricing and Availability, an error 173 could be returned. TLS 1.2 will now be used when making XML calls to SYNNEX. [Build: 4.06] | ||
| 146. For Salesforce.com users, changes made in the Salesforce Setup window were not being saved. This issue was introduced in v5.6 b3.36 [Build: 4.06] | ||
| 147. For MS CRM users, the contact was not being updated for an existing MS CRM Quote when the Sold To contact information was updated on an existing QuoteWerks quote. [Build: 4.06] | ||
| 148. For ConnectWise Manage users, when QuoteWerks was creating a Contact in ConnectWise and the ConnectWise Manage field used for "Mobile Phone" could not be determined, the contact creation would fail. If there is not a Communication Type in ConnectWise Manage as a "phone type" named "Cell" or "Mobile", the mobile field filled out in QuoteWerks will not be sent to ConnectWise Manage when creating a new contact. This fix will work for ConnectWise Manage v2020.1 and higher. [Build: 4.06] | ||
| 149. For Etilize users, the "Item Detail" tab was visible on the Product Lookup window and should not have been. [Build: 4.06] | ||
| 150. For GoldMine users, when searching for a contact and then selecting it, the email address was not being pulled into the quote. [Build: 4.06] | ||
| 151. In the Product Lookup window, on the Etilize panel, the [Update] button was appearing and should not have. If clicked caused runtime 9 to occur. [Build: 4.06] | ||
| 152. Blank error messages during new build data conversion. [Build: 4.06] | ||
| 153. 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. [Build: 5.10] | ||
| 154. 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. [Build: 5.10] | ||
| 155. InUseDocuments tracking between QuoteWerks Desktop and QuoteWerks Web. [Build: 5.10] | ||
| 156. In the File->Print window, when selecting [Save as PDF] the "Make PDF Ready Only" and "Add To File Links" options were missing. [Build: 5.10] | ||
| 157. When loading the purchasing window received error "VendorSourcing" field not found. [Build: 5.10] | ||
| 158. 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. [Build: 5.10] | ||
| 159. 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. [Build: 5.10] | ||
| 160. For HubSpot CRM users, the deal pipeline combobox was disabled on the Setup and Deal window for the free tier HubSpot CRM accounts. [Build: 5.10] | ||
| 161. 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. [Build: 5.10] | ||
| 162. 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. [Build: 5.12] | ||
| 163. For SugarCRM users, when doing datalinking, error messages about unrelated datafields could appear. [Build: 5.12] | ||
©1993-2024 Aspire Technologies, Inc.
407-248-1481 (9am-5pm ET M-F)
Please Wait...