Link to home
Start Free TrialLog in
Avatar of billinb
billinbFlag for United States of America

asked on

Using XML data source for primary and multiple subreports - impact of.

This is a follow up to Q_22981434.  I would like to pursue using XML as a datasource for some of our reports to compensate for 1. Reports that hit the database upon refresh/prompt for date range, and 2. If possible, to create a navigable hierarchy.

I'm wanting to be sure I understand the concepts and objectives.  The accepted response and use cases that would solve the bulk of the problems associated with large (in data) hierarchical and grouped reports.

'... create the report while physically connected to the Database, ... then create a XML Schema of the Data ... need and ... use that one Data source for the main report and all sub reports.  The linking should automatically stay intact as long as the column names remain the same and keys are respected in the schema... '  


What I think I want to find out is the following:

What is the intended content assuming no problems creating the report with an xml data source.?
Assume no problems creating a schema that matches the original data set.

The XML Source file, as example Sales.xml, is used as the data source for both
the primary (main) report and all subreports.  What then does the resulting report do or not do that would justify using an xml source.  Assume that the primary objective achieved would be a dataset that does not tickle the database.

-- is the primary benefit the utilization of hierarchical data?
-- is the primary benefit a report that doesn't need / require a refresh until the next scheduled run?
-- assume that all linking stays intact, and that all of the column names remain the same, and that all keys are respected in the xsd schema.
-- assume that there are two processes of development, the designing of the report while connected to the database and the alteration of all primary and subreports for an xml dataset.

Am I correct to assume here that the report becomes a navigavable hierarchy for purposes of viewing large amounts of data from a database in a Crystal report.

Note that although this scenario is one for Crystal.net, that I am using Enterprise Crystal report instances on Infoview, having scheduled the reports each morning.

Any suggestions and comments welcome.  I will gladly sent files and code upon request.

Thanks in advance,

Bill

Remove the word Not from the 2nd comparison in the code snippet - my bad.
Cross reference to
https://www.experts-exchange.com/questions/22981434/Problem-with-Refresh-button-on-Crystal-subreport-hits-database-despite.html
'' Takes too long!! Too many records !!  Too much Grouping !!  Crystal wants to refresh !!
DIM RESULT1 AS BOOLEAN
DIM RESULT2 AS BOOLEAN
DIM RESULTDev AS BOOLEAN
DIM blnIsAdmin AS BOOLEAN
DIM strFilter As String
DIM X AS DATE RANGE
 
blnIsAdmin = True
 
strFilter   = totext(CurrentCEUserName)
 
If strFilter <> "Administrator" Then
 
   RESULT1 = not ( strFilter in   {Command.Matching} )
 
End If
 
 
X = funDateRange(MAXIMUM({Command.DIM_CALENDAR_DT},{Command.STORE_ID}),"Daily")
 
RESULT2 = {Command.DIM_CALENDAR_DT} IN X
 
formula = NOT(RESULT1 AND RESULT2)

Open in new window

ASKER CERTIFIED SOLUTION
Avatar of Mike McCracken
Mike McCracken

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of billinb

ASKER

The users are not needing to hit the database.  In fact, I'll go one step further and say that it takes some crafty design in order for the end user to know that they have, indeed by design hit the database when changing a prompt or hitting refresh.

I wonder if there's anything to your implied suggestion of using an xml report to navigate a serieas of pdf files.  Maybe the way to work around the slow return / link with an xml source is to keep it small.

Thanks for your reply.