QuoteWerks Update Center

Update Center home

Version 23.0 Summary
61 New, 54 Fixes, and 7 Miscellaneous features
New Features - Version 23.0
 1. QuoteWerks Web now has a Setup->CRM Integrations area and the ability to completely setup the ConnectWise integration from within QuoteWerks Web. Also there is a Setup->Users area which has a full implementation of the user maintenance; you can add, edit and delete users, complete with all the security settings. QuoteWerks Web now has support for multifactor authentication including support for top Authenticator Apps (Google, Microsoft, etc.) and also Duo Push verification via the Duo Mobile App. QuoteWerks Web can also now run Reports with the Export option. [Build: 1.03]

 2. GoldMine version 2022.4 is now supported! [Build: 1.03]

 3. SugarCRM version 12.2 is now supported! [Build: 1.03]

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

 5. Real-time Pricing and Availability is now available for USA Distributor ADI ( www.adiglobal.com ) if you have an account with this distributor and credentials are entered into QuoteWerks. Also, this real-time pricing is displayed on the Product Sourcing Panel. [Build: 1.03]

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

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

 8. For QuoteValet Users, you can now have a custom Alias/CNAME in the QuoteValet URL. So, instead of www.quotevalet.com, the URL could be yourcompany.quotevalet.com. This feature is helpful, so your customers that are not familiar with QuoteValet will see your company name in the URL. This setting is on the General Tab of the QuoteValet Setup. [Build: 1.03]

 9. Replace has been added to the Edit->Find feature. You can select the Edit->Find menu (or press CTRL-F) which launches the find window and sets the Find Column to <All> which will search all the columns. While on that window you can choose to just search a single column. Alternatively, you can CTRL click on the column heading to search that specific column. You can search for things like, search for lines with a profit margin less than 10, search for lines with an empty cell, search for dates greater than specified date. When the search is run, it will find and highlight the first match, then you can successively press the [Find Next] button to highlight the next match. As matches are found, this is also a great opportunity to press the highlight button to set a highlight color for the row the match is on. [Build: 1.03]

 10. You can now clone Required Items, Optional Items, and Substitute Items. [Build: 1.03]

 11. The Expires field (ExpirationDate) on the Sale Info tab of the Quote Workbook now contains a time portion. This is useful for specifying that a quote expires at 5pm on a certain day. This changed is also supported in QuoteValet. You can specify the default expiration number of days and time on the Documents.General tab under Tools->Options menu. In the time text box if you enter, for example, +5:35 then it will add 5 hrs and 35 minutes to the current time. Without a + symbol the time will be a fixed time. [Build: 1.03]

 12. Text Library. For Memo fields, the F2lookup now lets you store a text library of large chunks of text that are searchable enabling you to easily compose your statements of work, terms and other text intensive composition. Additionally the F2lookup now has a separate column that can contain a description of the value for reference purposes. As a result of these changes you no longer need to use the //in the F2Lookup value to include a description, but when importing a list of values from the F2lookup window you can use the // to import the description for the value. The F2Lookup can do more than store static text. See the help file about these F2 Lookup functions: SALESFORCE_MACRO, QW_MACRO, RUNAPPANDRETURNCLIPBOARD, REQUESTDDEVALUE. [Build: 1.03]

 13. Data Manager for Advanced Import, Export, and Mass updating under the Utilities->Data Manager menu. You can now Import/Export Bundles, Configurations, Required Items, Optional Items, Substitute Items (BCROS). You can also Import/Export Contacts and Vendors. This new advanced Export will save the DataSet in a CSV file format with the column headings. This enables you to easily open up this file in excel and make changes. Then you reverse the process and Import this file. No mapping is required. The option to backup your data before the Import is available (and highly recommended). This is an advanced feature that you must be very careful with. In addition exporting data, changing it in Excel, and then importing the changes, you can also just export out a formatted CSV file that only has the column headings in it so that you can enter new data to import. You can do this with Bundles, Configurations, Required Items, Optional Items, and Substitute Items. Import and Export activities are recorded in the Event Log for audit trail tracking. The use of the Data Manager is restricted to users with MasterRights and also the Misc Access Rights of "NonMasterRightsUser_CanExportFromDataManager", and "NonMasterRightsUser_CanImportFromDataManager". All the BCROS entities now have RecGUID, CreatedOn, and LastModifiedOn fields making it easy to see which records were recently imported in case you made a mistake when importing new records you know which records you would need to delete to undo your error. [Build: 1.03]

 14. The Data Manager also has a Mass Update tab. Currently you can use this to increase prices by a percentage for all Fixed Price products in a Native product database. [Build: 1.03]

 15. On the Flowchart tab of the Edit Configuration window there is now a [Find] button. This will do a contains search of the Selection Container Names. When a match is found, it will ensure the node is visible, highlight it in yellow, and ask if you would like to find the next occurrence. You can also press CTRL-F to initiate the Find. [Build: 1.03]

 16. Purchase Orders now have a POConfirmed field. Often customers email a purchase order to a Vendor, but have not yet received confirmation of the receipt of the purchase order from their vendor. There is also a "Non-Confirmed POs" filter on the Purchase Orders tab of the Purchasing window so you can easily see which Purchase Orders have not been confirmed so you can ping the vendor about it. [Build: 1.03]

 17. PO Items now have an ETADate field so that you have a place to store and stay on top of the Estimated Time of Arrival of the Purchase Order items as your vendor gives you updates. To manage this field, there is now a right click "Update PO ETA..." for a Purchase Order. This will update the ETA date to the same date for all the items in the PO. For more granular control, the right click menu for a PO Item, has a "Change ETA.." menu. With this you can update the ETA date for and individual PO Item. You can use this with manual orders and online orders. [Build: 1.03]

 18. PO Related HTML templates now have new macros available which are &POI_&TrackingInfo?, &POI_&ETADate, and &POI_&SerialNumbers. [Build: 1.03]

 19. On the Purchase orders tab of the Purchasing window, there is a new right click menu "E-mail Internal PO Status...". You can use this to email status information about the purchase order internally. The HTML template and email can be fully customized and including tracking and serial numbers. On the E-Mail Template Manager window, there is a new button [Edit SYS_PurchasingInternalPOStatus HTML]. Additionally on the Templates tab, under the owner of (System) there is a new email template of "SYS_EmailPurchasingPOInternalStatus". [Build: 1.03]

 20. On the Purchase orders tab of the Purchasing window, there is a new right click menu "E-mail PO status to customer(s)...". You can use this to email status information to your customers about the items ordered for them on the Purchase Order. The HTML template and email can be fully customized and including tracking and serial numbers. On the E-Mail Template Manager window, there is a new button [Edit SYS_PurchasingCustomerOrderStatus HTML]. Additionally on the Templates tab, under the owner of (System) there is a new email template of "SYS_EmailPurchasingCustomerOrderStatus". Since your Purchase Orders can contain items from different customers, this feature will send each of those customers status updates on only their items on the Purchase order related to them. There is also a grid toolbar button for this action in addition to the right click menu. [Build: 1.03]

 21. On the Purchase orders tab of the Purchasing window, building on the new right click menu "E-mail PO status to customer(s)...", there is a toolbar button "E-mail PO status to customer(s) for all updated POs". This is very powerful. With this you can update ETA dates, and receive inventory of multiple Purchase Orders, and when you click this button emails will be sent out to all customers that are affected by the PO changes you made since the last time you clicked this button! This is a huge time saver and reduces many of the "where is my order?" type of questions you receive by email and phone from your customers. [Build: 1.03]

 22. The Tools->Export Items to Excel menu will now format the Excel columns with the data type that the data is. Previously, all the columns were just formatted as "General". [Build: 1.03]

 23. For Product Content Subscribers, there is a new checkbox on the Product Content Subscription tab of the Real-time Setup Window labeled "Do Not Download Product Images from Etilize". This option is helpful for those users that do not include Etilize Pictures on their quotes and proposals. If this option is checked, when retrieving an Etilize products, the Etilize picture will not be downloaded. This will save network space and time retrieving products from Etilize for those users. [Build: 1.03]

 24. On the E-Mail Template Manager window, on the Templates tab, under the owner of (System) there is a new email template of "SYS_EmailDistributorNonStandardPricing" enabling you to customize the email that is sent after an Online Order when you have specified non-standard or discount pricing that you have previously negotiated with your distributor sales rep. [Build: 1.03]

 25. The Tools->Export Items to Excel menu will now format the Excel columns with the data type that the data is. Previously, all the columns were just formatted as "General". [Build: 1.03]

 26. SoldToEmail, ShipToEmail, and BillToEmail columns are now included in the Open Document window results grid. This is useful for doing a search and then exporting the list to your favorite email blasting service to send out notifications to your customers or leads. Examples like which customers purchased an HP server in the last year and send them an email about a new limited time discount. Or which customers have you sent a quote to in the last 6 months, etc. [Build: 1.03]

 27. When looking for a field or macro to insert into a layout, insert into a email template, insert into a text box, select as a filter field, etc there is now a lookup button that you can click on to do a contains search to quickly locate the field that you are looking for. [Build: 1.03]

 28. The times stored in the QuoteWerks databases and dtf files were always stored in the local time. Starting with v23 the date/time values (including the AddOnDate01) stored in the database will always be stored in UTC time. For most users they will not have to do anything differently. If you externally read or write to the QuoteWerks database directly you will need to account for this change in UTC time. If you use the QuoteWerks API, when reading a value it will be in local time, and you can pass local time into the API, the conversion to UTC only happens at the instant of the time value being saved into the database. In the v6.0 upgrade all time values in the databases will be changed from local to UTC. [Build: 1.03]

 29. The CustomDate fields could store a time component, but when exiting the field, QuoteWerks would always format as a date, stripping out the time. Now, if there is a time component in the CustomDate, it will be preserved. [Build: 1.03]

 30. Management Reports now have a Category field to make it easier to organize different types of reports. [Build: 1.03]

 31. Management Reports now track LastModified, LastModifiedBy, CreatedOn, and CreatedBy so you know who created and last modified your reports. [Build: 1.03]

 32. Various backups (like when importing products, etc) are now stored in the \QuoteWerks\Backups folder. Each day a backup is made a new folder will be created in the \Backups folder like "2022-09-25", and then any backup files created that day will be stored in that folder. The file name will contain the data type and the time in UTC 24 hour format. For a SQL backend, the backup feature for contact and vendors import now stores the backup data in the \Backups folder as (described above ) which is in a different location and format that previously used. If is the Access backend, the backup is saved as contacts.b01, vendors.b01, etc. [Build: 1.03]

 33. Added a button on the 'Other Realtime' tab of the Real-time Setup to Collapse or Expand the List of Other Real-time Vendors, making it easier to navigate to the vendor you are looking for in the long list. [Build: 1.03]

 34. In the Settings Manager, you can now control the height of the rows on the Document Items tab per user. The range is 285 to 1425. The default is a single row at 285. The setting is UserSettings\UserConfig\QuoteSheetRowHeight=285 [Build: 1.03]

 35. For Autotask users, Products will now map over the Period attribute from QuoteWerks. [Build: 1.03]

 36. Added support for new SYNNEX warehouse "Chicago, IL". [Build: 1.03]

 37. The Active Quotes panel indicator is now red if the quote is expired, and the currently open quote is indicated with a cyan color background. [Build: 1.06]

 38. Microsoft SQL Server 2022 is now supported! [Build: 1.11]

 39. For Goldmine users, when e-mailing a PO from the File->Print window, there is now an option to "Log sen e-mail in CRM Under e-mail Recipient record". [Build: 1.11]

 40. Act! for web v24.1 is now supported! [Build: 2.01]

 41. Autotask 2023.1 is now supported! [Build: 2.01]

 42. Autotask 2022.3 is now supported! [Build: 2.01]

 43. GoldMine 2023.1 is now supported! [Build: 2.01]

 44. SugarCRM version 12.3 is now supported! [Build: 2.01]

 45. The Bundles window has been redesigned. You can now see the Bundle Items for each Bundle as you select it. Also you can now search for a Bundle Item Manufacturer Part Number making it much easier to find items you are looking for. There is also a right click "Copy Part Number" menu on the Bundle Items list. [Build: 2.01]

 46. The Required Items window has been redesigned. You can now see the Required Items for each item as you select it. Also you can now search for a Required Item Parent or Required Item Child making it much easier to find items you are looking for. There is also a right click "Copy Part Number" menu on the Required Items list. [Build: 2.01]

 47. The Optional Items window has been redesigned. You can now see the Optional Items for each item as you select it. Also you can now search for an Optional Item Parent or Optional Item Child making it much easier to find items you are looking for. There is also a right click "Copy Part Number" menu on the Optional Items list. [Build: 2.01]

 48. The Substitute Items window has been redesigned. You can now see the Substitute Items for each item as you select it. Also you can now search for a Substitute Item Parent or Substitute Item Child making it much easier to find items you are looking for. There is also a right click "Copy Part Number" menu on the Substitute Items list. [Build: 2.01]

 49. On the Required Items tab of the Edit Product window, if you remove the last Required Item, you will now be asked if you want to remove the Required Item Header record. Also on this tab it will now display if the Required Items list is shared with the same part number in other product databases. [Build: 2.01]

 50. On the Product Lookup window, when you delete a product, if this product has a Required Item Header record, the Header record and all the Required Items records will be deleted also. [Build: 2.01]

 51. Added LineNumber and LineNumberActual fields to the DocumentItems database table. Previously they were only in-memory macros and not available in Reports or for QuickBooks exports. These fields will be empty for any existing documents, but will be populated when you open and re-save the document. [Build: 2.01]

 52. For Autotask users, Autotask can now be used as a Secondary CRM. The Secondary CRM feature makes it possible for you to use your Primary CRM to create quotes and do all the back and forth, and then when the Quote becomes an Order, then you can use the Secondary CRM feature to integrate the Order including creating the customer, opportunity, products, etc in the Secondary Contact Manager. The benefit is that you can fill one CRM system with all quotes, leads, and products that you may never sell, and then only push orders, actual customers, actual products you have sold into the Secondary CRM system. The Secondary CRM can be selected on the Contacts->Setup Contact Manager window. There is a setup option of "Display Secondary CRM Export Window on each Save" which, if checked, will automatically pop up this export window after conversion to an Order, and after each save. You can access this feature using the Tools->Export to Secondary CRM menu. [Build: 2.01]

 53. For ConnectWise and Autotask users, now that there are two CRMs supported for the Secondary CRM feature, the Tools->Export to ConnectWise menu has been renamed to Tools->Export to Secondary CRM. Also the setup for this Secondary CRM feature is now located on the Contacts->Setup Contact Manager window. [Build: 2.01]

 54. In the Paste Special Wizard when selecting a field to map there is now a search feature so you can find a field to map faster. [Build: 2.01]

 55. Added DataManager support for PRICING.PricingProfileNames, PRICING.PricingProfiles, PRICING.PriceModifers, EXRATES.ExchangeRates, and LOOKUP.LookupItems tables. In the process added RecGUID, CreatedOn, and LastModifiedOn fields to these tables. [Build: 2.01]

 56. For QuoteWerks Contact database users, you can now search for a QuoteWerks Contact Database contact by the CustomText01 and CustomText02 fields. [Build: 2.01]

 57. For SYNNEX online ordering users, added new warehouses, "Suwanee, GA", "Swedesboro, NJ", "South Bend, IN", "Fontana, CA", also changed warehouse code from #14 to #50 for "Columbus, OH". [Build: 2.01]

 58. For API users, added AddonText01 field to the PRICING.PricingProfileNames, PRICING.PricingProfiles, PRICING.PriceModifers, EXRATES.ExchangeRates, and LOOKUP.LookupItems tables. [Build: 2.01]

 59. For QuoteValet users, added support for Opayo payment gateway, this is the replacement for Sage Pay. [Build: 2.05]

 60. For online ordering users for SYNNEX, Ingram Micro, and D&H, when the distributors change their warehouses, there is now a mechanism in place to receive the updated warehouse list without having to update the desktop version of QuoteWerks. [Build: 2.05]

 61. For SYNNEX Canada online ordering users, added "MISSISSAUGA, ON" warehouse and changed HALIFAX, NS" warehouse to "DARTMOUTH, NS". Also the "RICHMOND, BC" warehouse code changed. [Build: 2.05]

Misc Features - Version 23.0
 1. The "E-mail tracking number(s)..." right click menu for a Purchase Order has been removed as the new right click menus of "E-mail Internal PO status..." and "E-mail PO status to customer(s)..." are more robust and both include the tracking information. The PO Item right click "E-mail tracking number(s)..." has also been removed for the same reason. [Build: 1.03]

 2. The SalesLogix Integration has been discontinued in QuoteWerks v23 (November 2022). You can continue using the SalesLogix integration with QuoteWerks as long as you do not update to QuoteWerks version 23 or higher. [Build: 1.03]

 3. The Report definition .rcf files have been moved into a Reports table (stored in the REPORTS.MDB database if access backend). This was a necessary step for reports to be accessible in QuoteWerks Web. Since the RCF file data is now in a database, you cannot simply attach an RCF file to send to QuoteWerks technical support, or to receive reports from technical support. To address this, there are now right click menus in the Reports list of "Import Report from DataSet File..." and "Export Report from DataSet File...". You can also set Misc Access rights for these actions of "CannotImportReportsDefinition" and "CannotExportReportsDefinition". The command line /r option for running a report will now accept the RecGUID for the Report instead of the old RCF file name, for example, "/r E39B8128AA9D46999385FAB16C4FF598.rcf,1". You can obtain this using the [Generate Command Line Option] button on the General tab of the Edit Report window. For Remote users, when synchronizing there is now a Reports Data Group option in addition to the Reports File Group, both will need to be selected to rollout the complete report data (database record and fpc file) to a remote. [Build: 1.03]

 4. The QuoteWerks Contact Database contact record now requires that you enter a Company name. [Build: 1.03]

 5. For Autotask users, the Autotask API now has a version property that is now being checked to help ensure compatibility between Autotask and QuoteWerks. [Build: 2.01]

 6. Renamed the ExchangesRates.ExchangeRate field to ExchangeRates.ConvertToRate and renamed the ExchangeRates.WeightedOffset field to ExchangeRates.ConvertFromRate for clarity. [Build: 2.01]

 7. In Settings Manager, when selecting UserSettings, the user will now default to the logged in user vs the first user name in the list. [Build: 2.05]

Fixes - Version 23.0
 1. On the File->Import window when you selected the file type dropdown, the expected file types would not be displayed. [Build: 1.03]

 2. When exporting a native product database in the tab delimited format, the quote character was not getting doubled up, so if you opened it up in Excel the data would appear in the wrong columns for rows affected by this. [Build: 1.03]

 3. When cloning a user that had OAuth tokens like Maximizer Web, Zoho, HubSpot CRM, MS CRM, or OAuth SMTP, these tokens would be copied to the cloned user causing login problems for the source user. [Build: 1.03]

 4. On the Purchase orders tab of the Purchasing window, if you right clicked on a PO and choose to Cancel PO, the POItems status was not getting changed to Canceled. [Build: 1.03]

 5. Every year when Daylight savings changes happened in the fall, there was a problem where any documents changed within a time differential inside the daylight savings shift, like 35 minutes later when Daylight savings is a one hour shift backward. When the DTF file was opened, it would incorrectly think the DTF file was newer. This is now corrected with the change to store all date/times in the databases in UTC. [Build: 1.03]

 6. On the Product Lookup window, when right clicking and choosing compare, then selecting product databases to compare and clicking the OK button would receive "Subscript our of range" error. [Build: 1.03]

 7. For some of the grids, the Export to Clipboard button was not exporting the last column. Also, if the grid was in a horizontal scrolled position, it was only exporting columns starting with the first currently visible column on the left. [Build: 1.03]

 8. With QuoteWerks as your contact manager, under Contacts->Setup Contact Manager, if you clicked the [Export Contacts] button, then clicked Cancel, it would continue anyway. [Build: 1.03]

 9. For Act for Web users, PostalCode was not being displayed on the lookup window. [Build: 1.03]

 10. For Act for Web users, product names over 256 characters in length were causing an error. [Build: 1.03]

 11. For ConnectWise Manage users, when exporting a QuoteWerks Purchase Order to ConnectWise Manage with a PO number longer than 11 characters, a warning would appear saying that it is too long for ConnectWise Manage. [Build: 1.03]

 12. For Zoho CRM users, when saving to a Deal and attaching a Quote, if a part number has parenthesis an error will occur. [Build: 1.03]

 13. For Act for Web users, the link to the Act Opportunity on the QuoteWerks Links tab was redirecting some users to the Act for Web home screen instead of the Opportunity in Act. [Build: 1.03]

 14. For Zoho CRM users, the loading of the Deal window in QuoteWerks when creating or updating a Deal was longer and longer to open. [Build: 1.03]

 15. When a product had a required items and one of those items was missing, on the prompt to find a replacement or skip, if you clicked [Skip] would receive 'type mismatch' error. [Build: 1.03]

 16. Error Invalid Key when opening a quote that had a file link in it that had a file extension that was only numbers. [Build: 1.03]

 17. For salesforce.com users, when saving a PDF and choosing the option to "Attach to CRM", when the option "Use SalesForce Files instead of Attachments" is unchecked, the file extension of the file will now be added to the File title when it is uploaded to salesforce.com. Without this extension, in salesforce.com when you would try to download and save the file, there would be a blank file extension. [Build: 1.03]

 18. When cloning a Product in a Native Product Database, the Created date was not getting changed. [Build: 1.03]

 19. The feature to host a QuoteWerks Native Product database on Microsoft Azure needed to be updated to support latest Azure. This is a great feature to use if you have remote installations all installed locally on laptops, for example, and they can all search for and edit a centralized product databases that will always be up to date with no needed to synchronize the product database down locally to the laptop. [Build: 1.03]

 20. If a subscription was cancelled, QuoteWerks would not honor the remaining days left in the subscription period. [Build: 1.03]

 21. Issue in the UK with a time zone offset of "+00:00". Would cause error about invalid date uploading quote to QuoteValet. [Build: 1.03]

 22. Fresh installations of v23 were missing the CreatedOn fields in the QWContacts and Vendors tables. [Build: 1.04]

 23. For ADI Users, would receive the following error when communicating with ADI with valid credentials: 401{"ReturnCode":99,"ReturnMessage":"Unauthorized client. (API header authentication failed!)"} [Build: 1.05]

 24. For MSCRM users, updating an existing Opportunity's Status Reason on the QuoteWerks Opportunity window would not up save the change to MSCRM. [Build: 1.05]

 25. For API users, using .LineItemSetValue() to set some item fields in the first line of a new document and then using .AddLineItemToDocument(), the first line is overwritten instead of a new line added. [Build: 1.05]

 26. When using the Edit->Find, and searching, for example, the UnitPrice field, when the Find came to a line type of Subtotal, Running Subtotal, Percent Charge, Percent Discount, or Summary Line would receive Run-time error '13' Type mismatch error. [Build: 1.05]

 27. Error: This Version.Build of QuoteWerks requires the QWMSCRMInt6.dll with a .InterfaceVersion=53. An InterfaceVersion=54 was detected. [Build: 1.06]

 28. In rare situations, when adding items in a listview grid could receive an Overflow error. [Build: 1.11]

 29. When deleting a Configuration Selection Container would receive errors about 'ContainerID' field. [Build: 1.14]

 30. When the option to Preserve Quote (or Order) when converting to Order was not set, the DTF file for the quote/order should have been deleted but it was not. Also when running the Merge Document Transport Files process and QuoteWerks was first installed before v23 build 1.14 and either of these options are not set, you will be warned that "it will errantly add these DTF documents of (not preserved quotes) into your database which is not what you would want" and to contact technical support on how to proceed. [Build: 1.14]

 31. For Act for Web users, the PostalCode was not being displayed on the lookup window for online users. [Build: 2.01]

 32. For ZohoCRM users, when retrieving an existing ZohoCRM deal on the Deal window, the owner combobox would default to the first user. [Build: 2.01]

 33. When entering Tools->Options, and then exits the Options window, returning to Tools->Options Document tab, the Due Date number of days was reduced by a day. [Build: 2.01]

 34. For API Users, the qw.dll backend dll would display error about an empty TenantAccountNumber_Readyonly entry when accessing the .Installations property and one of the installations was using DBHosting. [Build: 2.01]

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

 36. When creating a new document from a template, the template's transaction log was being copied into the new document. [Build: 2.01]

 37. For SYNNEX online ordering users, when an order was placed and you requested that an item be shipped from a specific warehouse but SYNNEX could not oblige, SYNNEX would create a duplicate line in the order status with the only difference being the "Code" of QO vs SO. Now, the QO coded data will be ignored. [Build: 2.01]

 38. For SYNNEX online ordering users, when order status was requested, SYNNEX would first return a QO code with an Order Number, but then later change the code to SO and return a different SO number and possibly change the OrderedQty. Now, the QO coded data will be ignored. [Build: 2.01]

 39. For Autotask users, the Labor search was showing inactive items. [Build: 2.01]

 40. For SugarCRM users, the Phone search on the Contact Lookup was not bringing back search results if the phone number did not match up perfectly. [Build: 2.01]

 41. When cloning a report, if you clicked [Save] and then clicked [Save & Close] the report would be cloned again. [Build: 2.01]

 42. When attempting to delete a report would receive an error about 'unknown database'. [Build: 2.01]

 43. For salesforce.com users, when doing a Product Lookup search in QuoteWerks, you would receive a non-nullable column error if a CustomDate field was set for the products. [Build: 2.01]

 44. For MS CRM users, creating a new Order and saving would cause an error. [Build: 2.01]

 45. For MS CRM users, if a custom OptionSetValueCollection field was used for datalinking a contact or an account, the field in QuoteWerks was not being updated. [Build: 2.01]

 46. For MS CRM users, creating a new Order and saving would not populate the Actual Revenue or Estimated Revenue fields on the opportunity. [Build: 2.02]

 47. For API users, the method ItemFunctions::MLIBufferAppendPaste would silently fail if called on a locked document. [Build: 2.02]

 48. Newer Windows versions such as windows 11 or windows server 2022 were not being detected (the version detection issue was not causing an issue for QuoteWerks users). [Build: 2.02]

 49. For QuickBooks Desktop users, overflow error 6 On the QuickBooks Integration Setup window. If the QuickBooks file had more than 32,767 Non-Inventory Items, would receive an overflow error when attempting to load a list of all the Items for you to choose which item name to map the QuoteWerks Shipping Item to. Now any Items after the first 32,767 will not be included in the list. [Build: 2.02]

 50. If you opened the print window, and you had more than just a layout selected in your print selections, and then you did the sequence of editing the layout, choosing Save and Preview, then closing the Preview, then closing the layout editor, then closing the Print window. If you opened the Print window again, all your print selections would be missing except for the layout you edited. [Build: 2.05]

 51. On the GetSaveFile window, if Append Subfolder feature was not activated and you chose a file directly with the windows file selection dialog button, then the folder path combobox value would not be changed on the GetSaveFile window. [Build: 2.05]

 52. From the Purchase orders tab on the Purchasing window, right clicking on a Purchase Order and choosing "Save PO as PDF", for customers in the UK, the GBP symbol is not displaying correctly in the PDF. [Build: 2.05]

 53. The date/time columns on the Open Document window and File->Insert Document window were displaying the times in UTC instead of local time. [Build: 2.05]

 54. Would receive SQL query error when filtering on a date field with the operators of 'Greater than', 'Greater or Equal', 'Less than' , or 'Less or Equal' and leaving the search value blank. This would happened on the Open Document window and also the Opportunities Dashboard. Also when filtering by only a date when the field was a date/time field, sometimes expected results would not be returned due to UTC offset. [Build: 2.05]