Deny new reports with connection, but grant existing reports to same connection

[nick_vanlent1]

Is there a way to prevent users from using a specific connection when creating new reports, but still be able to view existing reports that use that same connection?  We have two connections pointed to the same system, and are planning on removing one of the connections.  However, it may take us a while to switch the existing reports to the other connection.  In the meantime, we'd like to prevent users from creating more content with the connection that we plan on removing.

Thank you

[former_member182521 · Accepted solution]

Hi Nick,

There is no direct way to achieve your requirement as we cannot hide the connections based on two different workflows (Viewing, creating New reports).

Thanks

Mani

[nick_vanlent1 · Accepted solution]

That's what I figured.  Thanks for verifying.

[former_member182521 · Accepted solution]

However we have a workaround for your scenario.

Try organize your connections in two folders, one for the existing (with which you dont want new reports) and another one for New.

     - Let the access to New folder be same as that of the current one. Users can view and create connections from here.

     - For the folder with obsolete connections hide the view to the folder but provide access to connection underneath (By applying only at Sub Objects level) with View On Demand access level. as a result users will continue to have access to the connections but they cannot view them.

Let me know for any difficulty.

Thanks

Mani

[former_member185603]

what kind of connection? Are you using the universe to crreate reports? Are they webi reports or crystal reports?

[nick_vanlent1]

It is a connection to a BW system.  Most of the reports are Analysis for OLAP, but there are a good number of Web Intelligence reports, and a few dashboards as well.