Feature Release 2.22.0

 

 WHAT’S NEW?

  • New feature – New and improved Tax Management screen.  This new screen makes it easier to manage tax rates and tax codes.  It also separates them based on where they are used, either in selling or purchasing transactions
  • New feature – Implemented restrictions to ensure that the assignment of a tax code to a record in Blackpurl aligns with the type of tax ie: selling vs purchasing tax.  This will ensure that a purchase tax is not assigned to a product and will also ensure that a selling tax is not assigned to a vendor as their purchase tax
  • New feature – All Fee codes will now be assigned a Type value of either Selling or Purchasing.  Restrictions have also been implemented to ensure that a Fee designated as a purchase fee cannot be used on a selling transaction and visa versa.  It will also restrict which tax codes can be used on a fee based on the Type assigned to the fee code.
  • New feature – Implemented the ability to Blackpurl to limit the number of technicians that can be created in any org.  Deployment of the feature to existing customers will set this to equal the total number of existing technicians

      

IMPROVEMENTS AND FIXES:

  • Correction – Resolved issue with the Part Movement report which was providing inconsistent results
  • Correction – Resolved issue with Product History report giving incorrect totals
  • Correction – Resolved issue where occasionally a customer order would contain two deals
  • Correction – Resolved issue with default mileage type being set incorrectly causing unit ordering issues
  • Correction – Further correction of issues related to importing SOM files
  • Correction – Resolved issue where only 10 categories were being listed in the add/edit unit record screen
  • Correction – Resolved issues with the sorting of line items in vendor receiving

Patch release 2.22.x

  • 2.22.0 – Correction – Resolved issue where invoice could not be finalized due to CO containing two deals
  • 2.22.0 – Correction – Resolved issue with unit ordering when default odometer type was set to Hrs
  • 2.22.0 – Correction – Resolved issue where first item from SOM file would not import
  • 2.22.0 – Correction – Resolved issue where the product history report would give totals that did not match the items listed in the search results
  • 2.22.0 – Correction – Resolved issue where the category dropdown for unit records would not list more than 10 categories
  • 2.22.0 – Correction – Resolved issue with sorting vendor receiving line items by the Item column
  • 2.22.1 – Correction – Additional corrections for incorrect totals in the product history report
  • 2.22.1 – Correction – Resolved issue which would not allow the user to enter a negative rate while creating a new price level
  • 2.22.1 – Correction – Resolved issue where birth date for a customer was not being properly saved to the customer record
  • 2.22.1 – Correction – Resolved issue where Force Oversold action on a cash sale was not obeying the workflow for superceded parts to display the View Related window
  • 2.22.1 – Correction – Resolved issue which would not allow a user to access Location Management
  • 2.22.1 – Correction – Resolved issue where the profitability would be incorrect when a part was not in-stock and needed to be ordered
  • 2.22.2 – Correction – Resolved issue where customer record could not be saved if the birth date was not populated
  • 2.22.2 – Correction – Resolved issue in Firefox and Brave browsers which prevented report csv exports from being generated

Back to all