CMPivot shouldn't be required to have default scope
It would be really great if default scope wasn't a required for CMPivot.
We use security scopes to separate workstations boundaries from server boundaries for the administrators. We are concerned that giving the default scope will open our server boundary up to the workstations administrators.
Cliff Hughes commented
I was able to reproduce the problem as a Full Admin with a Server Admin security scope, I have my lab setup simiar to separate out server and workstation objects, apps, packages, etc. and collections, so even as a full admin my server admin could not run CMPivot without an error, screen shot attached and voting this up for the community, as another customer I work with is fighting this same problem with their environment.