Skip to Main Content
ProPricer Ideas Portal
Status Planned
Workspace BOE Pro
Created by Guest
Created on May 14, 2025

Summary Field Mapping and Summary Field List Values Sync

Feature Request: Summary Field Mapping and List Value Synchronization

Summary:
Enable administrators to centrally define and maintain mappings between BOE Pro summary fields and corresponding CE fields, including their list values. The feature should synchronize changes to these mappings and list values between systems to keep configurations aligned and reduce manual maintenance.

Problem Statement:
Currently, users must manually maintain summary fields and their mappings in both BOE Pro and CE. List values also need to be added, updated, or retired separately in each system. This duplicated effort is time-consuming, prone to human error, and often results in configuration drift between BOE Pro and CE. When mappings or list values fall out of sync, it can cause inaccurate reporting, broken workflows, and confusion for users relying on consistent field definitions.

Proposed Solution:
Provide a dedicated configuration capability for “Summary Field Mapping” that:

  • Allows admins to define and view mappings between BOE Pro summary fields and CE fields.

  • Supports mapping of list-based fields, including one-to-one alignment of list values (codes/keys, display labels, and active/inactive status).

  • Synchronizes changes to mapped summary fields and list values between BOE Pro and CE based on configurable rules (e.g., CE → BOE Pro, BOE Pro → CE, or bidirectional).

  • Validates mappings and highlights incomplete or conflicting configurations (e.g., unmapped values, duplicate codes, mismatched types).

  • Provides clear feedback and logging for sync results, including errors and items that could not be updated.

Benefits:

  • Reduces manual effort and risk of error in keeping summary fields and list values aligned between BOE Pro and CE.

  • Improves data integrity and consistency across systems, leading to more reliable reporting and downstream processing.

  • Minimizes configuration drift over time by providing a controlled, auditable sync mechanism.

  • Increases administrator efficiency and confidence when introducing new fields or updating existing ones.

  • Attach files