Dynamically linking to WRS with parameters from Stored Process .. how to ??

[TwanManders]

From my SAS Portal i have to make a stored process that can capture an employee's department ( i use (_metaperson) and lookup in metadata for the department). Now i want to open automatically a Web Report with a parameter that holds the department and uses this information to show a Web Report with a filter for department.

How to do this?

[Madelyn_SAS]

You can use the stored process to dynamically generate data for an information map and then use the map for the report. Will that work?

[AngelaHall]

Why not skip the stored process altogether and use the 'derive identity values for row-level permissions' in the information map filter screen?

There is a SAS note that might be useful:
http://support.sas.com/kb/31/563.html


~ Angela
http://sas-bi.blogspot.com

[jplarios]

Angela,
will row level work the same way for a cube source?

[AngelaHall]

The information map 'Derive identity values (for row-level permissions)' only works for relational tables, for OLAP cubes the reference provided by SAS for 9.1.3 =
http://support.sas.com/onlinedoc/913/getDoc/en/bisecag.hlp/a003139257.htm

for 9.2 =
http://support.sas.com/documentation/cdl/en/bisecag/61133/HTML/default/viewer.htm#/documentation/cdl...

~ Angela
http://sas-bi.blogspot.com

[jplarios]

Angela,
for the membel-level ( OLAP source) will WRS be able to know who is entering ( like the _metaperson)? We have a table that explodes the hierarchy -between manager and supervisor which we currently use in an STP along with _metaperson. We eventually will use it with IM for row level ( but relational source). But will it work with an OLAP source? the 9.2 doc you pointed me too was not clear whether this member-level permissions are hard-coded or dynamic.

[AngelaHall]

The MDX expression is hard coded within the 'Add Authorization' window, but the 'user' the expression is assigned to could be a group of people instead of an individual (in step 2b of the 9.2 Example referenced above).

Managing the users within the group could then be completed via SAS Management Console User Manager, and no additional modifications are required to the cube/report when data or users within the group change. WRS will use this metadata authorization to determine what the user can or cannot see.

~ Angela
http://sas-bi.blogspot.com

[TwanManders]

Thanx for your input ..

i'm still working on a pemanent solution but found out how to make a
direct link from within stored process on portal where i get fx. a portalside from metadata

file _webout;
put '';
run;