BUG? or intended that in order to move or rename reports....

...anywhere in the folder structure a person must be set up as a Content Manager at the Reporting Services ROOT (and at every level of the folder hierarchy down to the level that they are moving/renaming)?

Sure, you can remove them from the role in other folders where they should not be moving or renaming objects, but it seems you still have to have them at the root (and down the chain), which gives them far more capabilities than you might intend.

Jeff

After further examination into this problem, it appears in order for someone to move or rename a report or file, they need two things:

1) Content Manager role for the folder they are moving to/from or renaming files

2) Content Manager role for the root RS folder, but not up or down the chain between the root or the folder above.

This has really got to be a bug, as I can't imagine Microsoft doing this on purpose.

Jeff

Bug Report: Expressions not deleted

I've noticed that if you create a data flow task (such as a DataReader source) and then bind an expression to it, if you rename or delete the task the expressions bound to the task will disappear but still be in the DTSX itself. So, if your expressions stop parsing (if you remove a variable, etc.) you will get errors for these expressions which you thought should have been removed. The workaround is to re-add the tasks with the old names and go delete the expressions from the expression list.
I suggest you raise a bug at http://lab.msdn.microsoft.com/ProductFeedback|||I could reproduce this problem and filed a bug.