218.486.5095

Implementation Specialists

Microsoft Partner providing ERP solutions, support and consulting.

Home / Business Central / Use Configuration Packages in Business Central to Update Salesperson Codes and Prices
a woman sitting at a desk coding on two computer screens

//

Microsoft Dynamics 365 Business Central offers powerful tools to streamline business processes, and one of the most effective is Configuration Packages. This feature allows users to efficiently manage and update data across multiple records, saving time and reducing errors. In this blog, we’ll explore how to use Configuration Packages to update the Salesperson Code for multiple customers and modify sales prices in bulk, ensuring your business data remains accurate and aligned with your operational needs.

What Are Configuration Packages?

Configuration Packages in Business Central are tools designed to import, export, and apply data configurations for various tables, such as customers, items, or sales prices. They are particularly useful for mass updates, migrations, or setting up new companies with predefined data. By exporting data to Excel, making changes, and re-importing, you can efficiently manage large datasets without manual, one-by-one updates. 

For example, Configuration Packages can help: 

  • Update master data like customer or vendor details.
  • Modify sales prices or discounts for items.
  • Apply consistent settings across multiple records.

This blog focuses on two common scenarios: updating the Salesperson Code for a group of customers and adjusting sales prices for items. 

Scenario 1: Updating Salesperson Codes for Multiple Customers

When reassigning customers to a different salesperson, manually updating each customer card is time-consuming and prone to errors. Configuration Packages simplify this by allowing bulk updates via Excel.

Step-by-Step Guide to Update Salesperson Codes

  • Create a Configuration Package:
    • Navigate to Configuration Packages in Business Central (search for it using the search bar).
    • Click New to create a new package.
    • Assign a meaningful Code and Package Name, e.g., CUST_SALESPERSON_UPDATE and “Customer Salesperson Update.” 
    • In the Table ID field, select 18 (Customer table). You can search for “Customer” to confirm the table ID. 
    • Verify the fields included by clicking the number in the No. of the Fields Available column. Ensure the Salesperson Code field is included (it should be by default.)

  • Export Customer Data to Excel: 
    • On the Configuration Package Card, select Excel > Export to Excel.
    • This generates an Excel file containing customer data, including the Salesperson Code field.
    • Optionally, apply filters (e.g., for specific customers) by selecting Table > Fields and setting rules, such as filtering by a specific region or customer group.
  • Update Salesperson Codes in Excel: 
    • Open the exported Excel file.
    • Locate the Salesperson Code column (field ID 5050).
    • Replace the existing codes with the new salesperson code (e.g., change JR to SM). Ensure the new code exists in the Salesperson/Purchaser table to avoid validation errors.
    • Save the file.
  • Import and Validate the Updated Data:
    • Back in the Configuration Package Card, select Excel > Import from Excel.
    • Upload the modified Excel file.
    • Check the No. of Package Errors field. If errors appear, click the number to view details (e.g., invalid salesperson codes) and correct them in the Config. Package Records page.
    • Select Actions > Functions > Apply Package to update the customer records in the database.
  • Verify the Changes:
    • Navigate to the Customers list or individual customer cards to confirm the new salesperson codes are applied. 
    • If errors persist, review the Config. Package Records page and use the Show Error action to troubleshoot. 

Best Practices

  • Test in a Sandbox – Always test the Configuration Package in a sandbox environment to avoid unintended changes in your live database. 
  • Check Permissions – Ensure the user importing the package has Insert and Modify permissions for the Customer table. Using a Super permission ID is recommended for smooth execution.
  • Validate Data – Before applying, use the Validate Package action to check for issues like invalid salesperson codes or data formatting errors.

By following these steps, you can efficiently reassign salesperson codes for hundreds or thousands of customers in minutes. 

Scenario 2: Updating Sales Prices in Bulk

Updating sales prices for items, especially when prices change due to market conditions or new agreements, is another task where Configuration Packages shine. This is particularly useful when you need to update prices for specific customers, customer groups, or all customers without affecting existing sales orders.

Step-by-Step Guide to Update Sales Prices

  • Create a Configuration Package for Sales Prices: 
    • In Configuration Packages, create a new package (e.g., SALES_PRICE_UPDATE, “Sales Price Update”).
    • Set the Table ID to 7002 (Sales Price table).
    • Confirm the included fields, such as Item No., Sales Type, Sales Code, Unit Price, Starting Date, and Ending Date. 
  • Export Sales Price Data to Excel:
    • Select Excel > Export to Excel to generate a template with existing sales prices.
    • Filter the data if needed (e.g., for specific items or customer groups) via Table > Fields. 
  • Update Prices in Excel:
    • Open the Excel file and locate the Unit Price column.
    • Update the prices as needed. For example, increase prices by 10% or set new prices for specific items.
    • Optionally, add Starting Date and Ending Date to control when the new prices take effect (e.g., 01/01/2026 to 12/31/2026).
    • To avoid affecting existing sales orders, ensure the Starting Date is set to a future date. Existing orders will retain their original prices if the order date is before the new price’s starting date.
    • Save the file.
  • Import and Apply the Updated Prices:
    • Import the modified Excel file using Excel > Import from Excel.
    • Check for errors in the No. of Package Errors field and resolve any issues (e.g., invalid item numbers or dates).
    • Apply the package using Actions > Functions > Apply Package
  • Alternative: Use the Sales Price Worksheet:
    • For more control, consider using the Sales Price Worksheet (Table 7032) instead of directly updating the Sales Price table. 
    • Create a Configuration Package for Table 7032, import the updated prices, and review them in the worksheet.
    • Set Starting Date and Ending Date to ensure new prices apply only to future orders.
    • Once verified, select Process > Implement Price Change to apply the updates.
  • Verify Price Updates:
    • Create a test sales order to confirm the new prices are applied correctly.
    • Check the Sales Price List page to ensure the updated prices are active and assigned to the correct customers or groups.

Best Practices

  • Set Date Ranges – Always use Starting Date and Ending Date to prevent new prices from affecting existing orders. For example, set an Ending Date for old prices (e.g., 12/31/2025) and a Starting Date for new prices (e.g., 01/01/2026).
  • Use the New Pricing Experience – If enabled (available since 2020 release wave 2), the Sales Price List feature offers a streamlined interface for managing prices. Ensure it’s activated in Feature Management for enhanced functionality.
  • Avoid Overwrites – When importing, avoid using the Delete Table Record option unless you intend to replace all existing data, as it can delete critical information.

For more information on Configuration Packages contact: support@iscorp.biz