Share
Report
571I've run into this numerous times before; but now I'm finally going to ask the question here: why are there so many datasets in GP SSRS reports that use XML SemanticQuery structures?<SemanticQuery
xmlns="schemas.microsoft.com/.../semanticmodeling"
xmlns:xsd="www.w3.org/.../XMLSchema"
xmlns:xsi="www.w3.org/.../XMLSchema-instance"\
xmlns:qd="schemas.microsoft.com/.../semanticquerydesign"
xmlns:rb="schemas.microsoft.com/.../reportbuilder">
<Hierarchies>
<Hierarchy>
<BaseEntity>
<!--Customer-->
<EntityID>Gd7c3c32e-abf5-4b2c-89e1-726b55145026</EntityID>
</BaseEntity>
<Groupings>
<Grouping Name="Customer">
<Expression Name="Customer">
<EntityRef>
<!--Customer-->
<EntityID>Gd7c3c32e-abf5-4b2c-89e1-726b55145026</EntityID>
</EntityRef>
</Expression>
<Details>
<Expression Name="Customer Number">
<AttributeRef>
<!--Customer Number-->
<AttributeID>Ge6a45c2d-d85e-45c6-8793-56cdbe496076</AttributeID>
</AttributeRef>
</Expression>
</Details>
</Grouping>
</Groupings>
</Hierarchy>
</Hierarchies>
</SemanticQuery>
This comes from the "Historical Aged Trial Balance" SSRS report in the DataSet for CustomerID.
Is this a case of GP using XML technology "because it's there"? Or "it was there years ago when we designed the report and there hasn't been any call to change it"?
I'm trying to make condensed versions of a couple GP SSRS reports and I get into trouble with a slash-and-burn approach while getting rid of Datasets and Parameters that aren't needed. I know that I also have to create a "condensed" version of the stored procs to go along with the reports and that's a joy in itself!
Anyway, have any of you dealt with SemanticQueries? Have you replaced them with something simpler, more SQL-like?
Sincerely,
Steve Erbach
WOW Logistics Company
Appleton, WI
*This post is locked for comments
All responses (
Answers (
