The other day, I was puzzled by a weird problem coming from a “Go to URL” action in a CRM sub-report.
Congratulations to my colleague Mathieu and I as we have successfully passed the TCS exam and are now proud to announce that we can deliver TARGIT trainings in French to customers in Belgium (French part) and Luxemburg!
One of my client asked me the other day to produce a report containing all the cases (incidents) in the system… OK, this is pretty easy and it already exists somewhere
But the hardest part was the filtering of this report: he wanted to be able to put a parent subject in the filter and the report should take care of getting all the child under this subject!
So, after a long time, I’ve decided to end my how-to series by explaining how to embed a subreport in a custom report.
So the purpose of this last post of the series is to explain how-to embed a subreport in a parent report and how-to pass parameters to this subreport (for example: pass the account ID from the parent report to the subreport).
In this article, I deal with the reporting drill-through and with the report pre-filtering to display the list of elements that are currently in queues.
This is the second part of this “how-to” series regarding the creation of a custom report in Microsoft CRM 4.0. For those who want to read the first part, you can go here: How-to series: Create a custom report (part 1)
Well, in the first post, we looked at how to create a new report using the “Report Wizard” provided by Microsoft CRM and, honestly, this report looked awful!
In this part, I will show you the internal stuff behind the scene and how you can add your own TSQL query to return the data you really want to see.
This is the first part of my “how-to” series covering the creation of a custom report for Microsoft CRM 4.0.