Report Designer and external data

Permanently deleted user

16. Februar 2012 05:37

I am having probelms bringing in external data into Report designer. There is no problem in displaying data-link data that has been made in the Geocortex manager and then displayed using subreports - this was quite straightforward. The issue relates to bound external data that is brought in via the Report Designer itself using Report Data Source. The data is displayed OK when previewing, bit not when the report is published. Any pointers or suggestions would be greatly appreciated. Unfortunately the documentation is somewhat lacking.

0

• 

  Permanently deleted user

  17. Februar 2012 08:34

  Dominic,

  There is a thread which provides some more information on this subject:

  https://support.geocortex.com/Forums/Thread.aspx?thread=46252&mid=2&pageid=0&ItemID=7

  In short, data sources you set up in the designer will be replaced by the dynamic data when the template is run in Essentials.

  John

  0
• 

  Permanently deleted user

  15. Mai 2018 16:00

  The suggested thread above no longer exists.  I think this post should be removed.

  0
• 

  Permanently deleted user

  15. Mai 2018 16:14

  Hi Lisa,

   

  We changed our Support Center software a few years ago and unfortunately it caused some older links to no longer be valid.  The link mentioned above is from 2011 and I will paste the relevant post from it, hopefully it helps :

   

   

  Louie,

   

  When using the TemplateReport or the Report task in Essentials (including from within a Workflow), Essentials handles the binding of data to the report dynamically at runtime.  What this means is that any data sources you may have set from within Report Designer will be replaced with the data from Essentials.  Creating a workflow activity that processes a report that respects data sources set in Report Designer may be possible, but it would certainly be a custom activity with no examples to help you along; in short, difficult.

   

  Though I've heard some rumours (on the forum) of issues with subreports in the TemplateReport activity, how I expect it to work is as follows.  The properties for the subreport control (located in your main report) will include, among others, a ReportName and a Tag property.  The Tag property, as you may have determined already, points to the path of the subreport rpx file relative to the location of the main report.  The ReportName property typically will be filled in with the ID of a DataLink which is tied to a layer, but what ultimately it comes down to is that this ReportName property references the name of a DataTable in the DataSet supplied to the report.  When Essentials runs a template report (using the Report activity or through the REST endpoint) it will construct a DataSet containing a DataTable for the spatial data, plus another DataTable for each of the DataLinks associated with the layer.  Depending on your template report, it may also create another DataTable containing bitmaps for the current map image (if you have added a Map subreport).  Essentials figures out which DataTable is to be passed to which subreport based on the ReportName property.  If you are creating your own DataSet in a workflow to pass to the TemplateReport activity, you'll want to create your own DataTables in your DataSet, and programmatically name these DataTables to reflect the ReportName property of the subreport - what Essentials does automatically with the other report invocation types.  I'm not sure off the top of my head what the name of the "main" DataTable ought to be, or if Essentials just uses the first DataTable in the set for this...I'll look into that if you have any troubles in that regard.

   

  This unfortunately brings up the need to query your SQL Server database on your own inside a Workflow - if you can publish this table in an ArcGIS Service (as just a plain table) and query it using the Query workflow activity, this might be the easist thing.  Creating a DataTable out of those results inside a workflow is likely easier than manually querying SQL Server, though if you're comfortable creating a custom Workflow activity it probably wouldn't be too much of a challenge.

   

  It would be best to first create a DataTable with some test data programmatically and wire it up, to make sure that it all works as expected before creating the bit which queries SQL Server.

   

  John

   

   

  Wayne Richard

   

  Latitude Geographics Group Ltd.

   

  Head Office: 300 – 1117 Wharf Street  Victoria, BC Canada V8W 1T7

   

  Tel: (250) 381-8130 | Fax: (250) 381-8132 | wrichard@latitudegeo.com 

   

  Developers of Geocortex web-based mapping software | www.geocortex.com

   

  An Esri Platinum Business Partner

   

   

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.