Understanding the Yellowfin database structure

Tara Wilson shared this question 2 years ago
Answered

I'm looking for some clarity and confirmation on some of the Yellowfin database components.


IpPerson - why does it contain many duplicates? Is this because some were removed and re-added during some testing?


Is this understanding of YF DB structure correct?

Organisation = Company

IpClass + Person = User

IpRltshp = many-to-many between company and user

AccessGroupFlat = many-to-many between role and person

OrgRole = Roles dictionary (if yes - why users, manager are deleted)

StaffMemberRole = many to many between Role and User


I'm also looking for clarity on the following, what are these tables for?

AccessGroup, AccessGroupMembers


Thanks in advance!

Comments (4)

photo
1

Hello Tara,


Thanks for reaching out with your question.

In regards to duplicates of users in the Config DB, when a user is removed the record remains in the IpClass. Instead of removing the record, Yellowfin changes the 'EndDate' field to a date older than 'today' to remove the user. If the account is added again after removal, a new record will be created in this table, resulting in seemingly duplicate entries.


The Organisation table will list all existing Client Organizations within the Yellowfin installation.


The main entries for users are within the IpClass + Person tables, however references to them via their Primary Key echo throughout other tables as well.


IpRltshp - maps users to Client Organizations as part of its functionality.


AccessGroupFlat - maps users to Groups within Yellowfin.


OrgRole - contains the role definitions. I'm unsure as to what you're referring in parasynthesis.


StaffMemberRole - maps users to their assigned roles.


AccessGroup - contains all groups created within Yellowfin.


AccessGroupMembers - contains users and their group assignments.


Does this address your questions?


Thanks,

Ryan

photo
1

Hello Tara,


I'm going to go ahead and mark this as Answered. If I haven't answered your questions, or you need more information, don't hesitate to re-open this Question.


Thanks,

Ryan

photo
1

Thanks, Ryan. You were able to answer my question.

photo
1

Tara,


Thanks for the update. Don't hesitate to contact us with any further questions or issues.


Thanks,

Ryan