Suggestion: config-based datasources

[TonyG]

The general-purpose, stand-alone designer allows a user to choose from all of the possible data sources: SQL, Cube, Object, Entity, and OpenAccess.

I've been creating a custom data source which extends ObjectDataSource, and all reports that a user would use with my tools would be based on this component, and no other.

I'd like to see config-file options that allow us to eliminate the default Data Sources from the UI, and replace them with options which we provide. So for example, under <AssemblyReferences> perhaps we could include an assembly that conformed to an API defined by Telerik, which defines all Data Sources. The code in there might do something like this:

[DataSourceExtender]
public void ModifyDesignerDataSources(Context context) {
  DesignerDataSources sources = context.getDataSources();
  sources.clear();
  sources.add("My Source", "myNameSpace.myClassDerivedFromDataSource");
}

With that, my designer users would never see a SQL data source, for example, they'd only see my source(s).

Does this have any merit?

Thanks.

[Elian]

Hi Tony,

Thank you for that suggestion, we will have it mind when considering the further development of the product.
Meanwhile please take a look at the Report Template capabilities that we provide. Extracting a template allows you to easily establish a base for creating new reports. 
 
Greetings,
Elian
the Telerik team

[TonyG]

I appreciate the consideration for a future enhancement.

Your response leaves the impression that you're thinking I'm talking about a report feature with templates. But I'm suggesting that you give developer/distributors more control over the features exposed in the designer itself for any end-user that receives our value-add package.

In my case, I want to provide a designer that does not offer alternative data source mechanisms. The end-user sites using my software will not be using this tool for anything but the datasource types I provide - that's part of my unique value-add in my segment of the industry. So we don't want report designers to have options in the static toolbar/ribbon for XML and Cube datasources that we need to tell them to avoid. We want to tell these end-users to click the one button that's there, where they will get the datasource type that we provide (derived from Object). I'm hoping this can be managed via the config file, where name/value pairs are consulted during the process of generating a dynamic toolbar/ribbon.

HTH
Thanks again.

[Elian]

Hi Tony,

Thank you for your feedback, again. We understood your inquiry the first time and we find it meaningful so we will surely have it mind. However, currently there are no means of controlling this behaviour, neither there are any workarounds that can fulfill you requirements. 
 
Greetings,
Elian
the Telerik team

[TonyG]

Thanks again. With this in mind, my current approach is to provide users with report templates with a pre-defined ODS. Unless that needs to be changed for more complex reports (and I expect it will), users shouldn't feel compelled to click the buttons for new data sources, so modifying the UI in this case isn't necessary.

This can be filed with a number of other requests for putting the designer into a container and customizing it. There seem to be a number of others who have asked for this over time.

No response required. Thanks.