I have this working on a different page, so I know it works.. I just can't get it working here:

Master SQL:

SELECT idReportPrinterThruConsumer_Title      
,[title]
FROM ReportPrinterThruConsumer_Header
where contentOwnerRoleID in (
 SELECT  r.RoleId
 FROM [OneSite2].[dbo].dnn_UserRoles r
  INNER JOIN [OneSite2].[dbo].dnn_Users on r.UserId = [OneSite2].[dbo].[dnn_Users].UserId
  INNER JOIN [OneSite2].[dbo].dnn_Roles on r.RoleId = [OneSite2].[dbo].[dnn_Roles].RoleId
 WHERE  [OneSite2].[dbo].[dnn_Users].UserId = @UserId
  AND    [OneSite2].[dbo].dnn_Roles.PortalId = @PortalId
  AND    (EffectiveDate <= getdate() or EffectiveDate is null)
  AND    (ExpiryDate >= getdate() or ExpiryDate is null))

Detail Grid SQL:

SELECT idReportPrinterThruConsumer_Title
      ,[OriginRoleID]
      ,[ContentOwnerRoleID]
      ,[title]
      ,[version]
      ,[originName]
      ,[originJobNum]
      ,[totalMailed]
      ,[totalCarrierRte]
      ,[inHomeStart]
      ,[inHomeEnd]
  FROM ReportPrinterThruConsumer_Header

But the DETAIL grid doesn't seem to get the linkage.. ie. the where clause that should be created by the grid control to link master and detail.. 

I thought that the grid would make the following where clause on the detail grid..

Where <Master>.idReportPrinterThruConsumer_Title = <Detail>.idReportPrinterThruConsumer_Title

Thoughts or assistance would be greatly appreciated.

ok.. must have been something like that. Interestingly, it appears that I can set a detail grid to use another detail grid as it's master, for cascading grids..

Hi! I'm glad you fixed your problem.

About cascading grid, this is a feature not much used but quite powerful. You can for example set a Details module rendered as a GridView and one rendered as a DetailsView.

About how to use a stored procedure, just use the same query as you do in the module. Actually the append of the query clause is done on the recordset and not on the database. The module fetch all the records, put it in the module cache, and filters the cached data. This must be improved but still works quite good for most of the cases.

Kind Regards,
D.

Hi!

This feature has been changed on users requests to use the @MasterID parameter. Actually the grid itself doesn't do anymore any filtering. The user should do it using it. For this reason you should have a stored procedure which accept the above parameter for making the filter at database level.

As always we're open to suggestion to improve this feature.

Kind Regards,
D.