Forum Discussion
Fabric graph
Hii psrihitha
You do not need to create three separate User node types. Create one User node type with UserID as the unique key; each distinct row/UserID in the source table automatically becomes a separate User node.
A single node type currently maps to one source table. If user details are spread across multiple tables, first merge/union and deduplicate them into one Lakehouse table or view. Different relationship tables can still create multiple edges connected to the same User node by matching the same UserID.
In my case, the user-related data is distributed across multiple tables and relationships originate from the same User node.How can i determine which relationship should be created for each record?Data contains Owned by/Managed by/IT Application owner user details.
Hii psrihitha
Keep one User node using UserID as the key and one Application node using ApplicationID. Create separate edge types for each role: User-OWNS>Application, User-MANAGES>Application, and User-IT_APPLICATION_OWNER_OF>Application. Map each edge to its corresponding column, such as OwnedByUserID, ManagedByUserID, or ITApplicationOwnerUserID; the edge mapping determines the relationship for every record. The same source table can be used for all three edge types when it contains these columns.
When the data has a single RoleType column, either prepare three filtered Lakehouse tables before creating the edges, or create one generic HAS_ROLE edge and add RoleType as an edge property. Fabric creates one edge per source row, and the User/Application IDs and data types must match their respective node keys.