Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XmlDataConnection DataSet Improvement #669

Open
chad-albrecht opened this issue Jan 26, 2024 · 1 comment
Open

XmlDataConnection DataSet Improvement #669

chad-albrecht opened this issue Jan 26, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@chad-albrecht
Copy link

chad-albrecht commented Jan 26, 2024

Is your feature request related to a problem? Please describe.
If you build your report based on an XmlFile (think report template), then try to use the FRX in code to populate the report with data that cannot be found on disk (streams, message queues, webhook, etc.) it fails. This is due to a limitation of the XmlDataConnection being bound to a file or URL only.

Describe the solution you'd like
Allow the XmlDataConnection to be populated with a DataSet from an unknown source. This could be as simple as allowing the connection string to be the actual XML similar to the JsonDataSourceConnection.

Describe alternatives you've considered

  1. Using the JsonDataSourceConnection and serializing my XML to JSON. This creates undesirable index/array/fieldname conditions in the report designer.
  2. Modifying the open source code to allow DataSet to be settable in DataConnectionBase
  3. Implement a LoadDataSet event on the DataConnectionBase that would allow the DataSet to be injected by code (most promising path)

Additional context
None.

@chad-albrecht chad-albrecht added the enhancement New feature or request label Jan 26, 2024
@Alekarfes
Copy link

Thank you for the suggestion, we'll look into it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants