I have a Customer statement report in which there are two stored procedure one is for the actual transaction level records and the other one is for PDC’s.
I have taken PDC section into a subreport,
Now the issue here is when for a particular customer there is no Transaction (Means No Data from the main stored procedure) but it has some PDC’s The report prints Blank.
my RDl mechanism is that one tablix connected to the main dataset in which i have attached a subrport into a row.
Any help on the RDL level will be usefull as i dont want to modify the StoredProcedures.
My findings are that the main tablix has not initialized yet to give/pass parameters to the subreport .
What does PDC mean / how is it related to the upper level report (e.g. what parameters are you passing)? Usually when you use a sub report there is some hierarchical relationship such that it makes little sense to have a scenario where the sub report has data but the upper level does not…
That said, maybe in your upper level stored procedure you could try doing a Union where you are inserting a dummy row into the dataset for customers that have no “Transaction” data but do have “PDC” data. That way you can get the appropriate parameters passed into the sub report. And then you can code the RDL to do appropriate formatting when it encounters the dummy rows.
PDC’s are Post Dated Cheques and in my scenario a customer has only few Post dated cheques against him.
the one thing i tried with the query was added a customer table and left joined the Main Dataset Query so this will give me atleast a custID which is usefull for initializing the Tablix. But the performance has been impacted with this . initially without using the Customer table the query returned result in 3 seconds after adding it almost takes 1 minute.
So dont we have any property on RDl level to initialize the tablix if no data in Main dataset.
He’s got an example of 2 related datasets, showing side-by-side. Maybe not exactly what you are doing, but shows how 2 unique datasets could be used in 2 unique tables to show related data. An interesting example nonetheless: