Skip to Main Content
ProPricer Ideas Portal
Status Planned
Workspace BOE Pro
Created by Guest
Created on Apr 23, 2026

External System Integration (ESI) need to support multiple results per query

|Feature Request: Support multiple results per ESI query

Summary:
Extend External System Integration (ESI) to support multiple aggregated results per query so users can totalize multiple columns in a single returned result set. This will enable scenarios such as calculating both total dollars and total non‑labor hours from the same external data table in one query.

Problem Statement:
Currently, ESI only supports returning a single result per query. When users need multiple aggregates (e.g., total dollars and total non‑labor hours) from the same result table, they must either run multiple queries or manually calculate and combine values outside the system. This creates extra steps, increases the chance of inconsistencies between totals, and makes it harder to use ESI effectively for complex, table-based calculations such as skill-mix analyses.

Proposed Solution:
Allow a single ESI query to define and return multiple result values derived from the same underlying result table.
Support configuring multiple aggregations (e.g., SUM, AVG) on different columns within the same query definition.
Return all configured results together in a structured response that downstream logic can easily reference (e.g., named fields for “Total Dollars” and “Total Non‑Labor Hours”).
Ensure configuration UI clearly shows each result, its source column, and aggregation type so users can manage and validate multiple outputs per query.
Maintain backward compatibility so existing single-result queries continue to behave as they do today.

Benefits:
Reduces the need for multiple ESI queries to retrieve related totals from the same dataset.
Improves accuracy by keeping all related aggregates in a single, consistent query definition.
Streamlines workflows for scenarios like skill mix tables that require multiple financial and effort totals.
Enhances ESI’s flexibility, making it more suitable for complex external data integrations and reporting use cases.

  • Attach files
  • Guest
    Jun 17, 2026

    As the submitter of this request, I'm am requesting that we withdraw this enhancement request from consideration. We have determined that we should use separate ESI queries for Labor and Non-Labor cost elements.

  • Guest
    Apr 23, 2026

    Attached Screen shot showing grayed out Field Type that shows Result. Query already has one result. Functionality is disables when adding a a second result...or third....or fourth.