problem editing dataset mdx query sql 2005

Hi all,
I have created a report with the report wizard. I used a cube as a
datasource.
After creating I also run the report without any problems.
However when I go to the data tab to edit my dataset.
The dataset becomes empty and my reports is getting errors like
"Report item expressions can only refer to fields within the current
data set scope or, if inside an aggregate, the specified data set
scope"
What is the problem, why can't I change a dataset based on analysis
services, i don't have any problems with datasets based on normal
databases.In Short:
WORKAROUND: If you have created your report using the Report Wizard to start
the MDX Query Builder, open the .rdl file as XML. Find the section starting
with <rd:MdxQuery> and ending with </rd:MdxQuery> and delete all spaces and
newlines between elements (between closing > and opening <) so the whole
complex element is inline. You will be able to continue working with the
report normally.
1) The problem arises when you use the Report Wizard (as GaryV indicated
before me)
2) If you compare the XML generated by the Query Builder when using the
Report Wizard and Add existing item... you will see
a) the complex element <rd:MdxQuery> from the Wizard path is nicely
formatted with spaces and newlines while
b) the Query Builder used directly puts the whole long
<rd:MdxQuery></rd:MdxQuery> "subdocument" inline
c) the proof is in the pudding - if you delete the formatting characters (I
ssupect the inlines are key) you can tab to Data and edit the dataset w/o
problems
See thread " VS crashes when ..."
"Anke" <anke_ruigrok@.zonnet.nl> schrieb im Newsbeitrag
news:1134563578.098538.277750@.g49g2000cwa.googlegroups.com...
> Hi all,
> I have created a report with the report wizard. I used a cube as a
> datasource.
> After creating I also run the report without any problems.
> However when I go to the data tab to edit my dataset.
> The dataset becomes empty and my reports is getting errors like
> "Report item expressions can only refer to fields within the current
> data set scope or, if inside an aggregate, the specified data set
> scope"
> What is the problem, why can't I change a dataset based on analysis
> services, i don't have any problems with datasets based on normal
> databases.
>|||Thanx for you're help, it works fine for me!
Ralph Watermann schreef:
> In Short:
> WORKAROUND: If you have created your report using the Report Wizard to start
> the MDX Query Builder, open the .rdl file as XML. Find the section starting
> with <rd:MdxQuery> and ending with </rd:MdxQuery> and delete all spaces and
> newlines between elements (between closing > and opening <) so the whole
> complex element is inline. You will be able to continue working with the
> report normally.
> 1) The problem arises when you use the Report Wizard (as GaryV indicated
> before me)
> 2) If you compare the XML generated by the Query Builder when using the
> Report Wizard and Add existing item... you will see
> a) the complex element <rd:MdxQuery> from the Wizard path is nicely
> formatted with spaces and newlines while
> b) the Query Builder used directly puts the whole long
> <rd:MdxQuery></rd:MdxQuery> "subdocument" inline
> c) the proof is in the pudding - if you delete the formatting characters (I
> ssupect the inlines are key) you can tab to Data and edit the dataset w/o
> problems
>
> See thread " VS crashes when ..."
> "Anke" <anke_ruigrok@.zonnet.nl> schrieb im Newsbeitrag
> news:1134563578.098538.277750@.g49g2000cwa.googlegroups.com...
> > Hi all,
> >
> > I have created a report with the report wizard. I used a cube as a
> > datasource.
> > After creating I also run the report without any problems.
> > However when I go to the data tab to edit my dataset.
> > The dataset becomes empty and my reports is getting errors like
> >
> > "Report item expressions can only refer to fields within the current
> > data set scope or, if inside an aggregate, the specified data set
> > scope"
> >
> > What is the problem, why can't I change a dataset based on analysis
> > services, i don't have any problems with datasets based on normal
> > databases.
> >|||I mean thanx for your help............