Buymanager Version 5.3: Enhanced Compliance and Security

This article introduces the latest Buymanager update, Version 5.3, released in October 2024.

What is this update?

Buymanager 5.3 introduces significant new features, including a Risk Substances Report for compliance and enhanced support for MySQL 8.4 for improved security. It also marks a critical change: the discontinuation of 32-bit version support.

Why do you need this update?

• For Users: Gain better insights into component compliance (RoHS, REACH) and benefit from a more secure and robust database environment.
• For Administrators: Ensure your Buymanager installation is up-to-date with the latest security standards and database technologies. This update is crucial for maintaining system stability and preparing for future compatibility.
• See our article here for update instruction 

Who is this for, and what are the prerequisites?

This update is relevant for all Buymanager users who wish to leverage new features and improved stability.
Administrators are responsible for installing and configuring this update. Administrative rights are required for installation and making necessary system changes (e.g., updating task scheduler paths, managing MySQL upgrades).

Download and Release Notes

The latest version of Buymanager 5.3 is now available.

• Download Buymanager 5.3 here.
• Now available the version 5.3.c.06

What's New in Buymanager 5.3?

Buymanager 5.3 brings key enhancements to help you manage your data more effectively and securely.

1. New Risk Substances Report

• Feature: This new report provides detailed information about hazardous substances present in your components.
• Benefit:  It helps you ensure compliance with critical regulations like RoHS and REACH, allowing you to make informed decisions regarding product safety and environmental standards.
• More Information: For a comprehensive guide on using this feature, please consult our dedicated help page on the [Risk Substances Report]

2. Enhanced MySQL 8.4 Support

• Feature: Buymanager is now fully compatible with MySQL 8.4.
• Benefit:  MySQL 8.4 is a long-term maintenance (LTM) version that offers enhanced password protection and improved data security, aligning your Buymanager environment with the latest database security trends.
• Important Note for Administrators: We strongly advise against performing the MySQL 8.4 upgrade yourself due to its complexity and potential for errors. If you have questions about upgrading to MySQL 8.4, please contact our sales team for assistance ([e-mail])

3. No More 32-bit Version Support

• Critical Change: Starting with Buymanager V5.3.c.03 and all subsequent releases, the 32-bit version of the software is no longer supported.
  Action Required for Administrators: When updating to Buymanager 5.3, you must update the executable path in your task scheduler for ERP imports. Change the path from `Buymanager.exe` to `Buymanager_64.exe`. This change is essential for the service to function correctly with the new version.

4. Improved Database Configuration Page

• Feature: The database configuration page has been updated for clarity. Instead of a "MySQL/HFSQL" option, there is now a new checkbox.
• How it works: This checkbox allows you to specify if you are connecting to MySQL version 8 or an earlier version (e.g., MySQL 5).
• Important Note: For most clients who have not yet migrated to MySQL version 8, this checkbox should remain unchecked. Only select it if you are explicitly using MySQL 8.x.

Buymanager 5.3.c.06: Bugs Fixed & Version Summary

Buymanager has evolved to version 5.3.c.04, incorporating several important fixes since the initial 5.3 release.

• Farnell API Improvement
  • Issue: Previously, searching for Manufacturer Part Numbers (MPNs) with special characters (like "/") via the Farnell API could be problematic.
  • Fix: You can now successfully search for MPNs that include special characters, enhancing search capabilities and accuracy.
  • Integrated in: Version 5.3.c.01 (October 2024)

• Trace Window Fix
  • Issue: A yellow trace window would sometimes appear when sending RFQs (Requests for Quotation) and generating final reports, interrupting the user experience.
  • Fix: This yellow window will no longer appear, providing a smoother workflow.
  • Integrated in: Version 5.3.c.02 (November 2024)

• DLL Files Generation Fix
  • Issue: There were issues with the install.exe file on the Buymanager client side in properly generating the newest DLL files during installation.
  • Fix: The install.exe has been improved to ensure the correct generation of the latest DLL files, leading to more reliable installations.
  • Integrated in: Version 5.3.c.02 (November 2024)

• Digikey Minireel Fees Correction
  • Issue: The calculation of Digikey minireel fees in sub-deals was incorrect.
  • Fix: The calculation for Digikey minireel fees has been corrected, ensuring accurate financial reporting.
  • Integrated in: Version 5.3.c.04 (March 2024)
• Enhancement Avnet WebQuote Capabilities
  • Enhancement: We´ve implemented improvements within WebQuote, specifically designed to deliver even more accurate results when utilizing the Avnet API.
  • Benefit: This optimization ensures you get the most precise data from Avnet, improving your sourcing process.
  • Integrated in: Version 5.3.c.05 (July 2025)
• ERP Import Data Assignment Fix
  • Issue: When performing specific data imports (e.g., changing supplier code using a composite key), ERP code could be changed, but FourCode failed to change in some cases. This happened because fields used as part of the composite key for lookup were inadvertently overwritten with the new value during the assignment process.
  • Fix: This logic for assigning values during import has been refined. The system now correctly distinguishes between fields used for lookup (as part of the composite key) and fields intended for update. This ensures that the new FourCode is correctly assigned without being reverted by the lookup value.
  • Benefit: Accurate and reliable data imports, especially when updating critical supplier information linked to composite keys
  • Integrated in: Version 5.3.c06 (August 2025)