I had an enquiry from a co-worker this week. It was as follows: they had access to two lists that they used daily. These lists were in two different teams' channels. However, they wanted to bring some of the data from one list into another to 'make their life easier'. On top of this they wanted - as a bonus - to display the data visually. However, they were not permitted to amalgamate the lists due to others using them and the business wanted them separate. So how could we solve this to make things easier? This is almost a textbook case for using lookup columns. What we need is a list relationship, where information from one list (the source list) can be used in another list (the target list). List relationships let you join information from two lists and keep it consistent while people edit and delete list items. Sound good? It is. However, there is four really important things to know with lookup columns before we get going. First, they don't currently support all column types. Whilst Single Line of Text, Date and Numbers are supported, other types such as Choice and Currency are not. Secondly, they are only supported in the same SharePoint site. In Teams land that means only if the lists are in public channels in the same team or if both lists are in the same private channel. No cross team. No cross public and private channels. Third, if you are using large lists then lookup columns may not be a solution. At that point we may be looking at something like SQL and Power Apps. But the biggest one - number four - is this. A lookup column does not automatically add values from a source list. A lookup column allows you to add values held in a source list. In other word the source list seeds values for the target - but they have to be added manually. This is an important distinction. Here is how to create a list with lookup columns to another list. And as a bonus, connect that List to Power BI to report on it