Roles Constraints

[Former Member]

Hi,

I have created a new User called Taton in my repository.

I have created a new role for this user.

I have a Txonomy Lookup table named Categories and the main table Business Partner have one Lookup Field called Category.

In Table and Fields section, I took the SubCategory Person as constraint from 3 values of the Categories table: 1> Person, 2> Organization and 3> Group.

Now, I re-connected to the repository through Taton user.

But I am getting all 3 values 1> Person, 2> Organization and 3> Group in the Taxonomy Lookup field in the main table Business Partner that violates the concept of constraint.

Regards

Kaushik Banerjee

[former_member198313 · Accepted solution]

Hi,

Is these 3 are the total available values ?

You have to select the value for which you have to give the access in constraint field.

Select only 1 or 2 and you can see the difference.

Hope this helps,

+ An

[Former Member · Accepted solution]

Hi,

Ankur I have done exactly as told by you but I

am getting all three values. Here these are values of the Categories table.

Regards

Kaushik Banerjee

[former_member198313 · Accepted solution]

your email pls

or send me a mail

[Former Member · Accepted solution]

Hi Ankur,

sent you a Test mail.

Regards

Kaushik Banerjee

Edited by: Kaushik Banerjee on Oct 30, 2008 12:13 PM

[former_member198313 · Accepted solution]

sent you screenshots.

I used Inquera repository

selected values of only first category out of 3 categories.

In Data manager record mode and also in taxonomy mode, it shows only first category records for that user.

hope this helps,

+ An

[Former Member · Accepted solution]

Hi,

Now it is displaying the correct result.

I think the repository need to be dicsonnected and connected with the Taton user.

Regards

Kaushik Banerjee

[Former Member]

Hi,

if you use taxonomies to restrict users, you have to use the child nodes of the taxonomy. You are able to use the parent nodes as well, but according to SAP this is an error and results in wrong results.

You either have to select all child nodes from the taxonomy or, if you have too many, create a calculated field which contains only the first digit from the taxonomy code and use this with a named search. The last option is my workaround. You may also create a named search with the "starts with" operator (this may save a field, but I did not test it).

I hope that helps you further.

Best regards

Christian

[Former Member]

Hi,

I think even if we can create constraints for Roles but it is not possible to implement it.

All Taxonomy categories should be used in the main table lookup.

Regards

Kaushik Banerjee