Pass Data from report to .NET

89 views
Skip to first unread message

Mark Mitchell

unread,
Jan 20, 2022, 4:29:48 PM1/20/22
to myfyireporting
Any way to do this?

Kernel Klink

unread,
Jan 21, 2022, 5:55:49 AM1/21/22
to myfyireporting
Taking one step back, and not knowing the details of the requirements, I would setup the data in a query or object and use that as the source for either .NET or the report.

You can render the report in an application if that was the goal of the question.

The Kernel

On Thursday, January 20, 2022 at 4:29:48 PM UTC-5 mark.m...@rooam.co wrote:
Any way to do this?

Mark Mitchell

unread,
Jan 21, 2022, 11:22:44 AM1/21/22
to myfyireporting
Thanks Kernel. The goal was to reuse data that was rendered from the report in a dropdown combo box in .NET. For example, my report shows employee names, and transactions for a certain date range (a parameter I'm sending in). I want to put these names in a drop down so they can be used to further filter the data. I was hoping to avoid sending another query but if thats the only way then I will make it so. So there is no public access to cached data?

If I go the query route, do you know a way to extract the query and dataset names that are embedded in the RDL file? Trying to make my app flexible.

Thanks in advance.

Mark

Joe Jorgens

unread,
Jan 21, 2022, 12:19:06 PM1/21/22
to myfyire...@googlegroups.com
I might still be missing something, but I would flip-flop it: populate the Employee and Date Ranges in .NET (via query, stored procedure, or C# object).  You can then pass either the filters to the report to query the DB or possibly directly bind the C# objects.  Disclaimer, I haven't done the latter, so don't know the challenges there.

I would keep the separation of concerns and modularity, meaning, let the report handle reporting.  Let the app handle "app-ing."  If you have such a load that a few more queries is going to cause performance problems, then maybe a more robust (i.e. paid) reporting system is needed.  Don't get me wrong, I am all for performance as long as it doesn't sacrifice complexity, modularity, maintainability, etc.

The Kernel





--
You received this message because you are subscribed to a topic in the Google Groups "myfyireporting" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/myfyireporting/CXN0lWlVmQc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to myfyireportin...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/myfyireporting/4ba7c192-d1ac-429c-869d-bc0c73e565can%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages