Shared Data Source Parameter Issue in 2 different Reports

[Wadiya]

Hello Telerik Team,

We are currently working with Telerik Report Server and leveraging shared data sources that use SQL parameters (e.g., @StartDate, @CustomerID) mapped from report parameters.

While the shared data source model is helpful for reusability, we are facing the following challenges and have some enhancement inquiries:

---

❗Current Issue: Parameter Name Coupling

When reusing a shared data source in multiple reports:

• The SQL parameters (e.g., @CustomerID) require exactly matching report parameter names in every report.

• This limits flexibility — as we cannot remap SQL params like @CustomerID to a differently named report parameter like CustomerFilter within the report context.

---

🔍 Our Use Case & Requirements

We would like to explore one or more of the following options:

✅ Option 1: Manual Mapping Support Per Report

Allow a report designer to map differently named report parameters to the SQL parameters of a shared data source without requiring parameter renaming across all reports.

✅ Option 2: Override Shared Data Source in Report Context

Enable overriding SQL parameter bindings for shared data sources within a report, without modifying the shared data source globally.

This would be similar to inline data sources — but using shared DS assets with local overrides or duplicating it.

✅ Option 3: Make Shared Resources Read-Only

We would like to allow usage of shared data sources across teams without allowing edits:

• Is it possible to make shared resources (like data sources and reports) usable but not editable by most users?

• Ideally, only admins or asset managers should be able to modify shared resources, while consumers can use them as-is (e.g., bind, preview, clone).