Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 9080

Re: Restrictions on a query

$
0
0

Hi Suman,

When I don't use the manual input variable for second char, the query works just fine as your scenario mentioned above.

 

"You should not use another manual entry variable for second char. Because you are already fetching those values from your internal query(replacing). "

 

You are right about that. I am fetching those values from the internal query. What I want is user can select from those values. The point in adding the second char with a manual input is that, users may either choose the organizational unit they are restricted with (so they can view all employees within that organization) or select any employee within the organizational unit they are restricted with. Unfortunately selecting this variable as ready for input seems disabled. (I tried to create another variable, but, when I select as replacement path with the results of a query, all the options in details tab is becoming disabled).

I could handle this restriction using a customer exit type of variable, but, it is not so easy to deal with the organizational unit hierarchy. I need to find all employees not just belonging to the organizational unit, but, belonging to all the nodes under that organizational unit.

Any more idea?

Thank you.

Yasemin...


Viewing all articles
Browse latest Browse all 9080

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>