Some SAP CDS analytical views and OData entities require parameters before they will return any rows — for example, a fiscal-year view that needs P_FiscalYear. Power BI Connector renders these parameters as a dedicated section on the entity, with the same metadata-driven validation the SAP service applies on the back end.
When the Parameters section appears #
The Parameters section is shown automatically when the entity’s OData metadata declares parameters (sap:semantics="parameters"). Plain entities do not show this section. Inside the data source editor, expand the entity panel — if the entity is parametrized, the Parameters section is the first block inside.
Fill in the parameters #
Each parameter is rendered with its display label, technical name, type, and a required marker if applicable. Default values declared in metadata are pre-populated so you can preview immediately. Edit them to scope the query the way you want.
What to expect in the editor
- Text and numeric parameters accept free input with type-appropriate validation.
- Date parameters open a date picker; the value is passed in the format the SAP service expects.
- Boolean parameters render as a toggle.
Preview is gated on mandatory parameters #
The entity-level preview button is disabled while at least one mandatory parameter is empty. A tooltip explains the missing prerequisite. Fill every mandatory parameter and the button enables.
The OData URL the connector generates encodes the parameter values into the path (for example, /EntitySet(P_FiscalYear='2026')/Set). When Power BI refreshes, the values you saved are sent back to SAP each time — so the dataset always reflects the same scope.
Round-trip #
Parameter values are persisted with the data source and re-loaded into the editor when you open it again. Cloning copies the parameter values along with everything else.
