Forum Discussion
Multiple sharepoint lists sharing same columns
Do you have a requirement there for security or is it that you just want to show different data sets to different users? If there's no security requirement around it, you could just use a single list with different views configured for each group of users. This way you have one version of the truth, i.e. one list item which is accessed by several different groups of users, but depending on the view will depend on the columns which are shown. This approach would give you the following:
List:
VIEW.A: Column1 Column2 Column3 Column4 Viewed by users set.A
VIEW.B: Column1 Column4 Column5 Viewed by users set.B
VIEW.C: Column1 Column2 Column4 Column6 Viewed by users set.C
Hi,
thanks for replying. Unfortunatelly, I need this for security. So group of users need to have access to list A, others need to acces List B etc.
- Matt WestonAug 23, 2018Iron Contributor
Do the users needs to interact with the data once it's in those lists or are they read-only?
- Nikola NenadovicAug 23, 2018Brass Contributor
They need to interact with the data that is only unique for that list. The shared data is imputed(and interacted with) in list A.
- Matt WestonAug 23, 2018Iron Contributor
Ok, thanks for that. So to summarise (this is just so that I completely understand the requirement :))
List A
Contains a set of data specific to this list.
Is secured to User Group A
List B
Contains the data that has been entered into List A AND has data specific to this list
Is secured to User Group B only
List C
Contains the data that has been entered into List A AND has data specific to this list
Is secured to User Group C only
Are you expecting users to be able to do something with the combined shared and unique data in lists B and C?
The way my mind is working at the moment you have a few options:
1. As Deleted mentioned, you could create a PowerApp to create a custom interface onto the lists
2. You use a Flow/Workflow to replicate the entries from List A into Lists B and C. I don't particularly like this as you'll have duplicates of the data, and you'll have to ensure that if anything changes in the consuming lists, then you'll need to replicate the changes across
3. You could create a page which has two web parts on it. One displaying the shared data from List A, and the other displaying the data relevant to them i.e. pageb.aspx has a web part displaying List B.