The Pricefx Copilot can select one or multiple Datamarts that best match the user’s business objective instead of being limited to a single Datamart from Sales Insights mapping.
Support for Multiple Datamarts per Agent
When creating an Agent via Copilot, the user can now ask for one or more specific Datamarts in the prompt (by name or label). Copilot passes the selected Datamarts as the data source list to Agent Generator, so different series in the Agent can use different Datamarts (for example, one series on Transactions and another on Quotes or Competition Data).
Prompt-driven Datamart Specification
Users can either rely on the Pricefx Copilot’s automatic best match or explicitly name Datamarts in the prompt (e.g. “Create Agent with Datamarts TransactionDM, Forecasted Budget DM…”). Copilot then sends the full selected Datamart list as input to Agent generation.
Default Fallback
If no specific Datamarts are inferred, Copilot falls back to the existing behavior of using the single Datamart from the Sales Insights mapping. The fallback choice is now per‑request and is no longer affected by Datamarts used in previous Copilot answers in the same session.
Explicit Datamart Selection
If the user specifies one or more existing Datamarts in the prompt, Copilot uses those Datamarts and shows them in the standard Agent‑creation confirmation step so the user can see which sources will be used.
Non‑existing Datamarts
If the user asks for a Datamart that is not available on the partition, Copilot now returns a clear error / unsupported‑scope message, instructing the user that such data cannot be found and should be checked, instead of silently picking another source.
Limitations
Copilot currently chooses Datamarts primarily based on their names/labels and does not use Datamart or field‑level meta descriptions to drive the selection.