Nice video! I'm not much of a database person, but I'm very curious about how you connect multiple sharepoint lists together in a 1 to 1 relationship using the ID column as the primary key. Surely, if the lists have a different amount of records those ID numbers won't match up to another list ... can you explain how you get the two lists to connect via this ID?
@@PowerAppsTutorial Thanks for the clarification - I didn't realize you were simply patching one list's ID into the other list as seperate column, I thought it was directly comparing each list item's ID to ID which didnt make any sense lol. So is there any downside to NOT using the ID column, and for two seperate lists to use one single unique identifier like "CustomerName" which will always be the same on both lists? Thanks.
I love this idea!
😊👍👍
Nice video! I'm not much of a database person, but I'm very curious about how you connect multiple sharepoint lists together in a 1 to 1 relationship using the ID column as the primary key. Surely, if the lists have a different amount of records those ID numbers won't match up to another list ... can you explain how you get the two lists to connect via this ID?
Sure! here you go! I'm actually considered a relationship expert: ruclips.net/video/c3Rb7wACap0/видео.htmlsi=R3GFILgXgktzJyqt
@@PowerAppsTutorial Thanks for the clarification - I didn't realize you were simply patching one list's ID into the other list as seperate column, I thought it was directly comparing each list item's ID to ID which didnt make any sense lol. So is there any downside to NOT using the ID column, and for two seperate lists to use one single unique identifier like "CustomerName" which will always be the same on both lists?
Thanks.
No downsides, you only have to ensure that your CustomerName is a unique column😊