Report Deployment

Hi,
Two Things:
1a) I was wondering if there is the odd issue with redeploying a report in
that some changes do not seem to be propagated. For instance, In one case I
set default parameter values for a report - this would cause the report to
automatically execute when browsing to it - I did not want this behaviour so
I removed the default values and redeployed the report. The defaults were
still there when refreshing the browser window - (even with closing and
reopening the browser the paramter values have not been removed).
1b) As an aside, can you turn this behaviour off so the report does not run
automatically if all parameters are preset?
2) Consequently, to ensure the report definition gets fully updated, I
remove the report and redeploy. A side-effect of this is all the
subscriptions are removed - and rightly so. However, the datasources for
the subscription remain. Is there any reason why this is?
thanks
regards
Matt1a) Server properties will always win when the rdl is republished. Because
the original RDL had defaults the server extracted this and stores them.
When a new RDL is uploaded we do not update the server parameters.
1b) No, you can not turn of this behavior.
2) Are the data sources shared? If so then they don't belong to the report
so they will not be deleted. If they are not shared, how are you still
seeing them?
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Matt" <NoSpam:Matthew.Moran@.Computercorp.com.au> wrote in message
news:ewy2iFoeEHA.644@.tk2msftngp13.phx.gbl...
> Hi,
> Two Things:
> 1a) I was wondering if there is the odd issue with redeploying a report in
> that some changes do not seem to be propagated. For instance, In one case
I
> set default parameter values for a report - this would cause the report to
> automatically execute when browsing to it - I did not want this behaviour
so
> I removed the default values and redeployed the report. The defaults were
> still there when refreshing the browser window - (even with closing and
> reopening the browser the paramter values have not been removed).
> 1b) As an aside, can you turn this behaviour off so the report does not
run
> automatically if all parameters are preset?
> 2) Consequently, to ensure the report definition gets fully updated, I
> remove the report and redeploy. A side-effect of this is all the
> subscriptions are removed - and rightly so. However, the datasources for
> the subscription remain. Is there any reason why this is?
> thanks
> regards
> Matt
>
>

Report builder - open error - (401) Unauthorized.

Hi,
Does anyone have similar error for Report Builder? It seems odd for the
messages. I don't know what is going wrong after the installation.
Many thanks.
Kenny
kenny_tm_cheng@.hotmail.com
=============
PLATFORM VERSION INFO
Windows : 5.1.2600.131072 (Win32NT)
Common Language Runtime : 2.0.50727.42
System.Deployment.dll : 2.0.50727.42 (RTM.050727-4200)
mscorwks.dll : 2.0.50727.42 (RTM.050727-4200)
dfdll.dll : 2.0.50727.42 (RTM.050727-4200)
dfshim.dll : 2.0.50727.42 (RTM.050727-4200)
SOURCES
Deployment url :
http://sql2005client/ReportServer/ReportBuilder/ReportBuilder.application
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later
in the log.
* Activation of
http://sql2005client/ReportServer/ReportBuilder/ReportBuilder.application
resulted in exception. Following failure messages were detected:
+ Downloading
http://sql2005client/ReportServer/ReportBuilder/ReportBuilder.application did
not succeed.
+ The remote server returned an error: (401) Unauthorized.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [08/02/2006 15:19:48] : Activation of
http://sql2005client/ReportServer/ReportBuilder/ReportBuilder.application has
started.
ERROR DETAILS
Following errors were detected during this operation.
* [08/02/2006 15:19:57]
System.Deployment.Application.DeploymentDownloadException (Unknown subtype)
- Downloading
http://sql2005client/ReportServer/ReportBuilder/ReportBuilder.application did
not succeed.
- Source: System.Deployment
- Stack trace:
at
System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
at System.Deployment.Application.SystemNetDownloader.DownloadAllFiles()
at
System.Deployment.Application.FileDownloader.Download(SubscriptionState
subState)
at
System.Deployment.Application.DownloadManager.DownloadManifestAsRawFile(Uri&
sourceUri, String targetPath, IDownloadNotification notification,
DownloadOptions options, ServerInformation& serverInformation)
at
System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirectBypass(SubscriptionStore
subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState,
IDownloadNotification notification, DownloadOptions options,
ServerInformation& serverInformation)
at
System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore
subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState,
IDownloadNotification notification, DownloadOptions options)
at
System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut)
at
System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
-- Inner Exception --
System.Net.WebException
- The remote server returned an error: (401) Unauthorized.
- Source: System
- Stack trace:
at System.Net.HttpWebRequest.GetResponse()
at
System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.I am getting a very similar error:
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed
later in the log.
* Activation of
http://rgv-bos-bl2/ReportServer/ReportBuilder/ReportBuilder.application
resulted in exception. Following failure messages were detected:
+ Downloading
http://rgv-bos-bl2/ReportServer/ReportBuilder/ReportBuilder.application
did not succeed.
+ The remote server returned an error: (401) Unauthorized.
+ The target principal name is incorrect
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
In my case it looks like a security related issue. I gave my account
all possible rights on the report server but no luck.
Radu|||HI, Radu.
Yes, I searched the KB for support but no luck.
I use the standalone server but no active directory.. not sure it relates to
security rights.
One throught may be related to the ASP.NET app pool is running under
NetworkService? it may not have access right to run Report Builder for the
users?
kenny|||I'm not sure if this will work for you but I managed to get report builder to
work on my servers, both development and production. I changed so many
things that I cannot say for certain this is what has to be done, but I
thought it might give you a direction.
The error indicates that it is a permission problem even though everything
seems to be set properly, right? In my scenario I've got Anonymous access
disabled and basic authentication configured, Integrated Windows
authentication is deselected. All of these settings are the same on the
report server, report manager, and report builder virtual directories and
even the files underneath each directory.
Here's what I did, I opened c:\program files\Microsoft SQL
Server\MSSQL.2\Reporting Services\Report Server\web.config
I edited the web.config file to reflect forms authentication instead of
Windows and told it not to impersonate
<authentication mode="Forms" />
<identity impersonate="false" />
I saved the file and opened https://www.server.com/reports - it of course
errored because the server is not configured for forms authentication. I
then reset the Web.Config file back to the original configuration
<authentication mode="Windows" />
<identity impersonate="true" />
Save the Web.config file
Open IIS and navigate to Web Sites | Default Web Site | ReportServer |
ReportBuilder
Right click ReportBuilder.application
Click Properties
Click File Security
Click Edit under Authentication and Access Control
Select Integrated Windows Authentication
Leave the Basic Authentication option selected as well if already selected.
Click OK
Repeat the above steps for ReportBuilder.exe and ReportBuilder.exe.manifest
From a workstation, not the server console
Browse to https://www.server.com/reports log in click Report Server
Click Report Builder and login again.
Report Builder opens
If you want you can then go back and remove the Integrated Windows
Authentication on ReportBuilder.exe.manifest and Reportbuilder.exe. Do not
change Reportbuilder.application or reportbuilder will not work.
I'm not sure what security holes I may have opened, but at least its working
for now.
Let me know if this works for you.
"Kenny Cheng" wrote:
> HI, Radu.
> Yes, I searched the KB for support but no luck.
> I use the standalone server but no active directory.. not sure it relates to
> security rights.
> One throught may be related to the ASP.NET app pool is running under
> NetworkService? it may not have access right to run Report Builder for the
> users?
> kenny

Report Builder - Entities list behaving poorly.

While attempting to create a new report, I came across what I feel is some
odd behavior. I select an item in the Entities list, then drag an item from
the newly populated Fields list to the report area. Once I drop the field
item, the Entities list changes scope showing only the Entity from which I
made a selection and any items within it. I can't get back up to the main
list unless I undo the operation.
Being relatively new to this domain, I considered that I might be expecting
behavior that I shouldn't be, however, when I checked the tutorial provided,
the instructions led me to believe I was right in being perplexed, thus this
post.
Anyone have info?
Thank you,
Scottits a normal behavior.
The model only present entities which can be used regarding what you
currently have in the report.
of your entities have no links between them, there are not available to the
user.
This insure that the user will not select unrelated entities and generates
bad queries. (like full outer join queries)
You have to create some roles between your entities to allow the user to go
from 1 entity to another.
"ScottT" <ScottT@.discussions.microsoft.com> wrote in message
news:14E3E2DB-B9CD-4D3D-9176-3B1FA5D7E4E0@.microsoft.com...
> While attempting to create a new report, I came across what I feel is some
> odd behavior. I select an item in the Entities list, then drag an item
> from
> the newly populated Fields list to the report area. Once I drop the field
> item, the Entities list changes scope showing only the Entity from which I
> made a selection and any items within it. I can't get back up to the main
> list unless I undo the operation.
> Being relatively new to this domain, I considered that I might be
> expecting
> behavior that I shouldn't be, however, when I checked the tutorial
> provided,
> the instructions led me to believe I was right in being perplexed, thus
> this
> post.
> Anyone have info?
> Thank you,
> Scott
>|||I'm not sure if I'd call it "normal".
From my initial investigations there has to actually be a foreign key on the
tables in SQL Server.
If this is the case and you can't have "logical" relationships between
entities, than this will make things very difficult for a lot of people.
It will make report builder unusable for databases with complex
relationships between entities and legacy systems.
You should be able to have no actual foreign keys if you don't want to
(however bad practice this is).
"Jéjé" wrote:
> its a normal behavior.
> The model only present entities which can be used regarding what you
> currently have in the report.
> of your entities have no links between them, there are not available to the
> user.
> This insure that the user will not select unrelated entities and generates
> bad queries. (like full outer join queries)
> You have to create some roles between your entities to allow the user to go
> from 1 entity to another.
> "ScottT" <ScottT@.discussions.microsoft.com> wrote in message
> news:14E3E2DB-B9CD-4D3D-9176-3B1FA5D7E4E0@.microsoft.com...
> >
> > While attempting to create a new report, I came across what I feel is some
> > odd behavior. I select an item in the Entities list, then drag an item
> > from
> > the newly populated Fields list to the report area. Once I drop the field
> > item, the Entities list changes scope showing only the Entity from which I
> > made a selection and any items within it. I can't get back up to the main
> > list unless I undo the operation.
> >
> > Being relatively new to this domain, I considered that I might be
> > expecting
> > behavior that I shouldn't be, however, when I checked the tutorial
> > provided,
> > the instructions led me to believe I was right in being perplexed, thus
> > this
> > post.
> >
> > Anyone have info?
> >
> > Thank you,
> > Scott
> >
>
>|||Reportbuilder is not designed for complex schemas!
the system doesnt support complex relationships and other business rules.
Reportbuilder is (more) designed to give access to a well formatted
database, I mean a database with a "beautyfull" schema (good and simple
relationship).
Also, Reportbuilder is designed to be very intuitive for the end user. so
when the user start to play with the customer name, reportbuilder will
display only customer's related information because the MUST go through
these known entities to continue his report.
A user can't select a customer name and a product name as is, the user MUST
select the customer name, then the sales then the product, because the
question is "what are the product sales to my customers?"
the job you have to do is to create this easy to use reportbuilder model in
front of your database to insure that an end user can use your database
without any SQL knowledge.
if your database is too complex, you have to work hard to generate a report
builder model.
"James" <James@.discussions.microsoft.com> wrote in message
news:16CD66FF-16CA-44F6-9E50-496026C88464@.microsoft.com...
> I'm not sure if I'd call it "normal".
> From my initial investigations there has to actually be a foreign key on
> the
> tables in SQL Server.
> If this is the case and you can't have "logical" relationships between
> entities, than this will make things very difficult for a lot of people.
> It will make report builder unusable for databases with complex
> relationships between entities and legacy systems.
> You should be able to have no actual foreign keys if you don't want to
> (however bad practice this is).
> "Jéjé" wrote:
>> its a normal behavior.
>> The model only present entities which can be used regarding what you
>> currently have in the report.
>> of your entities have no links between them, there are not available to
>> the
>> user.
>> This insure that the user will not select unrelated entities and
>> generates
>> bad queries. (like full outer join queries)
>> You have to create some roles between your entities to allow the user to
>> go
>> from 1 entity to another.
>> "ScottT" <ScottT@.discussions.microsoft.com> wrote in message
>> news:14E3E2DB-B9CD-4D3D-9176-3B1FA5D7E4E0@.microsoft.com...
>> >
>> > While attempting to create a new report, I came across what I feel is
>> > some
>> > odd behavior. I select an item in the Entities list, then drag an item
>> > from
>> > the newly populated Fields list to the report area. Once I drop the
>> > field
>> > item, the Entities list changes scope showing only the Entity from
>> > which I
>> > made a selection and any items within it. I can't get back up to the
>> > main
>> > list unless I undo the operation.
>> >
>> > Being relatively new to this domain, I considered that I might be
>> > expecting
>> > behavior that I shouldn't be, however, when I checked the tutorial
>> > provided,
>> > the instructions led me to believe I was right in being perplexed, thus
>> > this
>> > post.
>> >
>> > Anyone have info?
>> >
>> > Thank you,
>> > Scott
>> >
>>|||I agree with what you're saying about the reportbuilder being a simple tool
for users without much or any knowledge of SQL or the particular database.
The bit I don't understand is why we are so limited in what we can do when
building the model.
This is a layer of abstraction and so it shouldn't matter if the actual
database is complicated underneath as long as the final model you present the
user with is straight forward.
Whats the point of having the layer of abstraction if everything has to be
in the database, you might as well report directly from the database.
As far as you know, is there definitely no way to say 2 tables are related
in your model that don't have an actual foreign key in SQL Server?
"Jéjé" wrote:
> Reportbuilder is not designed for complex schemas!
> the system doesnt support complex relationships and other business rules.
> Reportbuilder is (more) designed to give access to a well formatted
> database, I mean a database with a "beautyfull" schema (good and simple
> relationship).
> Also, Reportbuilder is designed to be very intuitive for the end user. so
> when the user start to play with the customer name, reportbuilder will
> display only customer's related information because the MUST go through
> these known entities to continue his report.
> A user can't select a customer name and a product name as is, the user MUST
> select the customer name, then the sales then the product, because the
> question is "what are the product sales to my customers?"
> the job you have to do is to create this easy to use reportbuilder model in
> front of your database to insure that an end user can use your database
> without any SQL knowledge.
> if your database is too complex, you have to work hard to generate a report
> builder model.
>
> "James" <James@.discussions.microsoft.com> wrote in message
> news:16CD66FF-16CA-44F6-9E50-496026C88464@.microsoft.com...
> > I'm not sure if I'd call it "normal".
> > From my initial investigations there has to actually be a foreign key on
> > the
> > tables in SQL Server.
> > If this is the case and you can't have "logical" relationships between
> > entities, than this will make things very difficult for a lot of people.
> > It will make report builder unusable for databases with complex
> > relationships between entities and legacy systems.
> > You should be able to have no actual foreign keys if you don't want to
> > (however bad practice this is).
> >
> > "Jéjé" wrote:
> >
> >> its a normal behavior.
> >> The model only present entities which can be used regarding what you
> >> currently have in the report.
> >> of your entities have no links between them, there are not available to
> >> the
> >> user.
> >> This insure that the user will not select unrelated entities and
> >> generates
> >> bad queries. (like full outer join queries)
> >>
> >> You have to create some roles between your entities to allow the user to
> >> go
> >> from 1 entity to another.
> >>
> >> "ScottT" <ScottT@.discussions.microsoft.com> wrote in message
> >> news:14E3E2DB-B9CD-4D3D-9176-3B1FA5D7E4E0@.microsoft.com...
> >> >
> >> > While attempting to create a new report, I came across what I feel is
> >> > some
> >> > odd behavior. I select an item in the Entities list, then drag an item
> >> > from
> >> > the newly populated Fields list to the report area. Once I drop the
> >> > field
> >> > item, the Entities list changes scope showing only the Entity from
> >> > which I
> >> > made a selection and any items within it. I can't get back up to the
> >> > main
> >> > list unless I undo the operation.
> >> >
> >> > Being relatively new to this domain, I considered that I might be
> >> > expecting
> >> > behavior that I shouldn't be, however, when I checked the tutorial
> >> > provided,
> >> > the instructions led me to believe I was right in being perplexed, thus
> >> > this
> >> > post.
> >> >
> >> > Anyone have info?
> >> >
> >> > Thank you,
> >> > Scott
> >> >
> >>
> >>
> >>
>
>|||there is an abstraction layer, the DSV.
in the DSV you can create links that doesn't exists in the database, you can
add a layer of queries and other calculated columns etc...
So if there is no foreign key in the database, you can create a logical
relationship in the DSV.
you can use unrelated tables in the model.
but if there is no links, then the user can't use these 2 tables at the same
time in report builder.
"James" <James@.discussions.microsoft.com> wrote in message
news:6879B37B-A3DC-4871-B254-80BC0B93648D@.microsoft.com...
>I agree with what you're saying about the reportbuilder being a simple tool
> for users without much or any knowledge of SQL or the particular database.
> The bit I don't understand is why we are so limited in what we can do when
> building the model.
> This is a layer of abstraction and so it shouldn't matter if the actual
> database is complicated underneath as long as the final model you present
> the
> user with is straight forward.
> Whats the point of having the layer of abstraction if everything has to be
> in the database, you might as well report directly from the database.
> As far as you know, is there definitely no way to say 2 tables are related
> in your model that don't have an actual foreign key in SQL Server?
> "Jéjé" wrote:
>> Reportbuilder is not designed for complex schemas!
>> the system doesnt support complex relationships and other business rules.
>> Reportbuilder is (more) designed to give access to a well formatted
>> database, I mean a database with a "beautyfull" schema (good and simple
>> relationship).
>> Also, Reportbuilder is designed to be very intuitive for the end user. so
>> when the user start to play with the customer name, reportbuilder will
>> display only customer's related information because the MUST go through
>> these known entities to continue his report.
>> A user can't select a customer name and a product name as is, the user
>> MUST
>> select the customer name, then the sales then the product, because the
>> question is "what are the product sales to my customers?"
>> the job you have to do is to create this easy to use reportbuilder model
>> in
>> front of your database to insure that an end user can use your database
>> without any SQL knowledge.
>> if your database is too complex, you have to work hard to generate a
>> report
>> builder model.
>>
>> "James" <James@.discussions.microsoft.com> wrote in message
>> news:16CD66FF-16CA-44F6-9E50-496026C88464@.microsoft.com...
>> > I'm not sure if I'd call it "normal".
>> > From my initial investigations there has to actually be a foreign key
>> > on
>> > the
>> > tables in SQL Server.
>> > If this is the case and you can't have "logical" relationships between
>> > entities, than this will make things very difficult for a lot of
>> > people.
>> > It will make report builder unusable for databases with complex
>> > relationships between entities and legacy systems.
>> > You should be able to have no actual foreign keys if you don't want to
>> > (however bad practice this is).
>> >
>> > "Jéjé" wrote:
>> >
>> >> its a normal behavior.
>> >> The model only present entities which can be used regarding what you
>> >> currently have in the report.
>> >> of your entities have no links between them, there are not available
>> >> to
>> >> the
>> >> user.
>> >> This insure that the user will not select unrelated entities and
>> >> generates
>> >> bad queries. (like full outer join queries)
>> >>
>> >> You have to create some roles between your entities to allow the user
>> >> to
>> >> go
>> >> from 1 entity to another.
>> >>
>> >> "ScottT" <ScottT@.discussions.microsoft.com> wrote in message
>> >> news:14E3E2DB-B9CD-4D3D-9176-3B1FA5D7E4E0@.microsoft.com...
>> >> >
>> >> > While attempting to create a new report, I came across what I feel
>> >> > is
>> >> > some
>> >> > odd behavior. I select an item in the Entities list, then drag an
>> >> > item
>> >> > from
>> >> > the newly populated Fields list to the report area. Once I drop the
>> >> > field
>> >> > item, the Entities list changes scope showing only the Entity from
>> >> > which I
>> >> > made a selection and any items within it. I can't get back up to
>> >> > the
>> >> > main
>> >> > list unless I undo the operation.
>> >> >
>> >> > Being relatively new to this domain, I considered that I might be
>> >> > expecting
>> >> > behavior that I shouldn't be, however, when I checked the tutorial
>> >> > provided,
>> >> > the instructions led me to believe I was right in being perplexed,
>> >> > thus
>> >> > this
>> >> > post.
>> >> >
>> >> > Anyone have info?
>> >> >
>> >> > Thank you,
>> >> > Scott
>> >> >
>> >>
>> >>
>> >>
>>|||Thanks,
I was trying to do it through the designer view of the report model.
I didn't realise I wanted to be in the designer view of the Data Source View
instead.
"Jéjé" wrote:
> there is an abstraction layer, the DSV.
> in the DSV you can create links that doesn't exists in the database, you can
> add a layer of queries and other calculated columns etc...
> So if there is no foreign key in the database, you can create a logical
> relationship in the DSV.
> you can use unrelated tables in the model.
> but if there is no links, then the user can't use these 2 tables at the same
> time in report builder.
>
> "James" <James@.discussions.microsoft.com> wrote in message
> news:6879B37B-A3DC-4871-B254-80BC0B93648D@.microsoft.com...
> >I agree with what you're saying about the reportbuilder being a simple tool
> > for users without much or any knowledge of SQL or the particular database.
> >
> > The bit I don't understand is why we are so limited in what we can do when
> > building the model.
> > This is a layer of abstraction and so it shouldn't matter if the actual
> > database is complicated underneath as long as the final model you present
> > the
> > user with is straight forward.
> > Whats the point of having the layer of abstraction if everything has to be
> > in the database, you might as well report directly from the database.
> >
> > As far as you know, is there definitely no way to say 2 tables are related
> > in your model that don't have an actual foreign key in SQL Server?
> >
> > "Jéjé" wrote:
> >
> >> Reportbuilder is not designed for complex schemas!
> >> the system doesnt support complex relationships and other business rules.
> >>
> >> Reportbuilder is (more) designed to give access to a well formatted
> >> database, I mean a database with a "beautyfull" schema (good and simple
> >> relationship).
> >>
> >> Also, Reportbuilder is designed to be very intuitive for the end user. so
> >> when the user start to play with the customer name, reportbuilder will
> >> display only customer's related information because the MUST go through
> >> these known entities to continue his report.
> >> A user can't select a customer name and a product name as is, the user
> >> MUST
> >> select the customer name, then the sales then the product, because the
> >> question is "what are the product sales to my customers?"
> >>
> >> the job you have to do is to create this easy to use reportbuilder model
> >> in
> >> front of your database to insure that an end user can use your database
> >> without any SQL knowledge.
> >> if your database is too complex, you have to work hard to generate a
> >> report
> >> builder model.
> >>
> >>
> >> "James" <James@.discussions.microsoft.com> wrote in message
> >> news:16CD66FF-16CA-44F6-9E50-496026C88464@.microsoft.com...
> >> > I'm not sure if I'd call it "normal".
> >> > From my initial investigations there has to actually be a foreign key
> >> > on
> >> > the
> >> > tables in SQL Server.
> >> > If this is the case and you can't have "logical" relationships between
> >> > entities, than this will make things very difficult for a lot of
> >> > people.
> >> > It will make report builder unusable for databases with complex
> >> > relationships between entities and legacy systems.
> >> > You should be able to have no actual foreign keys if you don't want to
> >> > (however bad practice this is).
> >> >
> >> > "Jéjé" wrote:
> >> >
> >> >> its a normal behavior.
> >> >> The model only present entities which can be used regarding what you
> >> >> currently have in the report.
> >> >> of your entities have no links between them, there are not available
> >> >> to
> >> >> the
> >> >> user.
> >> >> This insure that the user will not select unrelated entities and
> >> >> generates
> >> >> bad queries. (like full outer join queries)
> >> >>
> >> >> You have to create some roles between your entities to allow the user
> >> >> to
> >> >> go
> >> >> from 1 entity to another.
> >> >>
> >> >> "ScottT" <ScottT@.discussions.microsoft.com> wrote in message
> >> >> news:14E3E2DB-B9CD-4D3D-9176-3B1FA5D7E4E0@.microsoft.com...
> >> >> >
> >> >> > While attempting to create a new report, I came across what I feel
> >> >> > is
> >> >> > some
> >> >> > odd behavior. I select an item in the Entities list, then drag an
> >> >> > item
> >> >> > from
> >> >> > the newly populated Fields list to the report area. Once I drop the
> >> >> > field
> >> >> > item, the Entities list changes scope showing only the Entity from
> >> >> > which I
> >> >> > made a selection and any items within it. I can't get back up to
> >> >> > the
> >> >> > main
> >> >> > list unless I undo the operation.
> >> >> >
> >> >> > Being relatively new to this domain, I considered that I might be
> >> >> > expecting
> >> >> > behavior that I shouldn't be, however, when I checked the tutorial
> >> >> > provided,
> >> >> > the instructions led me to believe I was right in being perplexed,
> >> >> > thus
> >> >> > this
> >> >> > post.
> >> >> >
> >> >> > Anyone have info?
> >> >> >
> >> >> > Thank you,
> >> >> > Scott
> >> >> >
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>