Get Inspire insights from former attendees in our AMA discussion thread on Inspire Buzz. ACEs and other community members are on call all week to answer!

Alteryx Designer Desktop Discussions

Find answers, ask questions, and share expertise about Alteryx Designer Desktop and Intelligence Suite.
SOLVED

Identifying Users With Toxic Roles - Use Case

surajmthomas
8 - Asteroid

I have 2 tables 

 

First Table: If you notice the Rows are repeated for some of the IDs. If an ID is associated to multiple ROLES, each ROLE will have a separate entry with the ID

 

IDRole
100BUSVF
100BUSMK
100BUSVWR
101BUSMK
102BUSVWR
103MIGVF
103MIGMK

 

Second Table: This is the Toxic Role Rules Table 

 

Valid_RoleToxic_Role
BUSVFBUSMK
MIGVFMIGMK

 

How to read this rules table -- 

An ID having BUSVF should not also have BUSMK

An ID having MIGVF should not also have MIGMK

 

Therefore, I would need to compare the second table with the first table and throw exceptions where the Toxic Rules Table match

 

For example consider ID 100 in the first table. 

 

ID 100 has roles BUSVF, BUSMK, BUSVWR

 

The toxic rules table states that an ID having BUSVF should not also have BUSMK. Therefore, ID 100 is an exception.

 

How do I go about achieving this ?

 

 

 

7 REPLIES 7
messi007
15 - Aurora
15 - Aurora

@surajmthomas,

 

Please see below

 

messi007_0-1625124674850.png

attached the workflow,

 

Hope this helps!

Regards,

AngelosPachis
16 - Nebula

Hi @surajmthomas ,

 

Not sure this is what you are looking for but do give it a try. What it does is it checks if a Toxic ID is found in your original table and flags it out. So based on the logic I assume you described, the only ID which is not toxic and should not be exempted is 102

 

AngelosPachis_0-1625125112308.png

 

 

Hope that helps,

 

Angelos

surajmthomas
8 - Asteroid

@AngelosPachis  Thank you Angelo for your time. Much Appreciated.I have tried this. This is partially correct, but not quite what I am looking to achieve. The values in the Toxic Column are not always Toxic. What I mean to say is

 

The user can have a role BUSMK. Therefore, the user 101 associated with BUSMK is valid. 102 associated with BUSVWR is also valid

 

What I am trying to achieve here is according to the Valid Toxic Relationship table is

 

A user having BUSVF cannot also have BUSMK as a role. Therefore, if you look at ID 100, it has BUSVF, BUSMK and BUSVWR. Here, 100 having BUSVF, BUSVWR is ok. But because of the Valid Toxic Relationship table, ID 100 having BUSMK is invalid.

 

Therefore my exception should be

 

100 - BUSMK

 

 

surajmthomas
8 - Asteroid

@messi007Thank you for your time and help. I am trying this out. Will revert.

AngelosPachis
16 - Nebula

Hi @surajmthomas ,

 

Thank you for the extra information. Following the same logic, shouldn't ID 103 also be exempted?

 

If you slightly configure the workflow it achieve the desired result

 

AngelosPachis_0-1625129923509.png

 

AngelosPachis
16 - Nebula

@surajmthomas or you can tweak it even further to the role granularity, so

 

100 - BUSMK

and

103 - MIGMK

 

are exempted

AngelosPachis_0-1625130554452.png

 

surajmthomas
8 - Asteroid

@AngelosPachis @messi007  Thank you both very much for the inspiration and your time for your solutions. You both are geniuses. I have worked on the solution that I was looking for based on your inputs. This is what I was quite looking for and it works like a charm

 

surajmthomas_0-1625157639806.png

 

Labels