Hi,
Glad you could make it work.
That said, I must admit that the need to specify browse permission is not the perfect approach. The problem comes from that the web service that will permit to enumerate child sites, needs this specific permission. If we were using the object model, we could easily overcome this by using ElevatedPrivileges when necessary.
We are currently investigating a possible approach to overcome this limitation that would involve specifying "Credentials stored securely in the report server" combined with the "Impersonate the authenticated user after a connection has been made to the data source" option. The idea would be to use stored credentials for enumerating sites and child sites and revert to current user credentials for retrieving lists items.
