site inheritance causes reports to fail to render (datalink, feature maps have different ID)

Bryan Townsend

June 20, 2013 01:21

I recently deployed a site that inherits another. 

The parent site has a tremendous amount configured, my specific problem occurs with reports that use datalinks (and feature maps).

The parent site  (PlanningViewer) has this data link referenced in a report:

DataLinkSql_Addresses

 

The report fails to render in the child site (PlanningViewer_Internal) when accessed by the rest endpoint or through a Silverlight viewer. It appears the name of the datalink changes from what it is in the parent site to a different name in the child site, prefixed by the site name and a dash - “PlanningViewer-”.

 

DataLinkSql_Addresses

 ->> PlanningViewer- DataLinkSql_Addresses

 

Additionally, the Feature and Overview map requires this same prefix in the report. 

 

What this requires is another rpx file, identical to the original, except for the datalink and feature map changes  to reference the parent site (SiteName-).

So with multiple reports for each layer, this causes quite a bit of rework for small changes and duplication of identical reports.

 

Please let me know if there is some alternative or if this can be corrected in a future release. 

0

• 

  Permanently deleted user

  June 20, 2013 01:39

  I had this happen, too, and had to get rid of the inheritance references in the child sites. I configured everything I could in the master site, then imported the services to the child. But it means any map changes have to be reconfigured in each child, or you remove and re-import. Which can change the service ID...

  Also, a bug I ran into is that the dash itself causes an error in validation. I am told it will be fixed in the next release.

  0

Please sign in to leave a comment.