Skip to main content

Blackpurl Release Notes — Version 2.45

A summary of new features, improvements, and bug fixes included in the Blackpurl 2.45 release.

What's New

Version 2.45 introduces three new features: multi-technician scheduling on a single appointment, supersession notifications on part line items, a new Order Fulfillment document, and several Vendor Receiving (VR) performance improvements.

Scheduling Multiple Technicians on a Single Appointment

The add/edit appointment screen now supports scheduling more than one technician on a single appointment. A single technician can also be scheduled multiple times on the same appointment when needed.

Supersession Notification

When a part record that has been superseded is added to a Customer Order (CO), Vendor Order (VO), or Vendor Receiving (VR), a notification now displays on that line item indicating the part number it has been superseded to. Acting on the notification remains at the user's discretion. The notification appears on the Customer Order in the Parts & Accessories section whenever a superseded part is added.

Shows a Parts & Accessories section with an orange header displaying 'Total: $12.00 Internet Sales'. Below is a table sh


New Order Fulfillment Document

A new Order Fulfillment document is available from the Customer Order. It includes the items on the current invoice, items from previous invoices for the same CO, and items that have yet to be fulfilled. You can also enter tracking numbers during the checkout process. For more details, see Order Fulfillment Document (no longer available).

Vendor Receiving (VR) Performance Improvements

Several changes have been made to how Vendor Receiving works to improve performance and usability:

  • When a VR is generated, the user's focus is now placed in the Packing Slip# field by default.

  • VRs no longer automatically attach all unreceived Vendor Orders (VOs) and VO items when generated. VOs are not selected by default — you must select only the VOs you want to receive against.

  • A search field is now available to find a specific VO, which is helpful when there is a long list of unreceived VOs.

  • Fixed an issue where the Expected date was not being correctly populated in the VO listing.

  • The sort order of VOs has been updated: selected VOs appear first, followed by unselected VOs ordered by expected date — currently due first, then overdue, then future due.

  • You can now receive against unreceived VOs even when none have been selected, allowing users who prefer to receive by part number to still match items against unreceived VOs.

For more details, see How to Receipt / Receive Parts into your Inventory (including Sublets) (no longer available).

What's Improved

The following improvements and bug fixes are included in this release.

  • Improvement — Performance of the Make / Model management screens when Blackpurl contains a large number of makes, models, and/or submodels.

  • Resolved — Issue syncing customers to QuickBooks (QB) / Xero caused by invalid characters in the customer name field.

  • Resolved — QB sync failures caused by an "unable to lock row" error while syncing invoice payments and part adjustments.

  • Resolved — Issue that caused a VR to be synced to QB/Xero multiple times (specific dealership only).

  • Resolved — Issue that caused incorrect values on the Scheduler > Week View when a technician has an extended leave time entry.

  • Resolved — Issue that caused FEE line items from KITS in Deal Service to not be properly reflected in the accounting journal entries (specific dealership only).

  • Resolved — Issue that incorrectly caused a third-party claim invoice to attempt to send to QB/Xero even when all items had been removed from the CO > Service Job.

  • Resolved — Issue with the resyncing script that incorrectly reposted journal entries that were already posted (specific dealership only).

  • Resolved — Issue that prevented users from creating a new transaction type in Accounting Integration.

  • Resolved — Issue that caused an invoice posted to Xero to not include sales taxes (unique scenario for specific dealership only).

  • Resolved — Issue with syncing job clocking entries to Xero that was not posting in all scenarios (specific dealership only).

  • Release — Custom Forms that have been mapped and made available for specific dealerships.

  • Correction — Deployment issues with 2.45.0 regarding the new scheduler feature.

  • Resolved — Issue with submitting a site-specific export file.

  • Correction — Issue that caused tracking numbers to not always save with the invoice.

  • Correction — Grammar in the VR notification relating to parts being on an unselected VO.

  • Resolved — Issue that prevented creating a CO due to customer name restrictions that were incorrectly implemented.

  • Resolved — Issue where the CO Picklist could not print with a Service Job until a unit was assigned to the Service Job.

  • Updated — Subject line for the notification email regarding site-specific file uploads.

  • Resolved — Issue that allowed part records to be deleted even when they were still in use on active COs.

  • Resolved — Issue with receiving units without populating the stock number field.

  • Resolved — Issue with unit reporting by status caused by the introduction of the consignment unit feature.

  • Resolved — Issue with back-end tags on service jobs caused when a part has a very long description.

  • Correction — Issue on customer invoices where the date shown on the document was one day prior to the actual invoice date.

  • Correction — Issue that prevented a deal from being set to Approved due to active service jobs.

  • Correction — Issue where packaged information was not shown for a line item when the package unit was blank.

  • Release — Additional Custom Forms that have been mapped and made available for specific dealerships.

  • Improvement — New process for automatically resolving Xero Access Denied and Read Timeout sync failures.

  • Resolved — Issue that caused the return quantity on Vendor Returns to be reset to zero when the approved action was completed.

Did this answer your question?