Cross site lookup

%3CLINGO-SUB%20id%3D%22lingo-sub-777323%22%20slang%3D%22en-US%22%3ECross%20site%20lookup%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-777323%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20using%20SharePoint%20online%20we%20would%20like%20to%20access%20top-level%20site%20list%20data%20to%20subs%20site.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Efor%20example%2C%20we%20created%20the%20customer%20list%20in%20the%20top-level%20site.%20we%20need%20to%20use%20this%20data%20to%20all%20subsite%20list.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ehow%20we%20can%20do%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-777323%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-777378%22%20slang%3D%22en-US%22%3ERe%3A%20Cross%20site%20lookup%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-777378%22%20slang%3D%22en-US%22%3EUnfortunatelyh%20this%20is%20not%20possible%20with%20SPO%20Today%2C%20so%20to%20meet%20this%20requirement%20you%20need%20custom%20development%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-777388%22%20slang%3D%22en-US%22%3ERe%3A%20Cross%20site%20lookup%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-777388%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F383629%22%20target%3D%22_blank%22%3E%40Jeyganesh%3C%2FA%3Ethird-party%20solutions%20exist%20for%20these%20kind%20of%20scenario's.%20I%20know%20they%20exist%20but%20haven't%20used%20them%20myself.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20you%20could%20consider%20to%20make%20use%20of%20Managed%20Metadata%20Term%20Sets%20instead%20of%20SharePoint%20lists.%20You%20could%20for%20example%20create%20a%20Customers%20Term%20Set%20to%20store%20the%20most%20important%20data%20to%20be%20able%20to%20identify%20a%20customer%20and%20reference%20this%20using%20Managed%20Metadata%20columns%20from%20all%20your%20subites.%20If%20you%20need%20to%20store%20more%20data%20around%20these%20same%20customers%20you%20might%20still%20also%20have%20your%20central%20%22Customers%22%20list%20optionally%20also%20pointing%20to%20this%20same%20Term%20Set%20and%20create%20a%20custom%20developed%20synchronization%20mechanism%20%3CSPAN%3Eto%20prevent%20maintenance%20of%20your%20customer%20lists%20in%20more%20than%20one%20place.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EHope%20this%20helps!%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-777674%22%20slang%3D%22en-US%22%3ERe%3A%20Cross%20site%20lookup%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-777674%22%20slang%3D%22en-US%22%3EDepending%20on%20the%20list%20providing%20data%20you%20might%20be%20able%20to%20get%20by%20with%20utilizing%20Managed%20metadata%2C%20which%20you%20can%20setup%20lists%20of%20data%20which%20can%20be%20used%20as%20columns%20in%20all%20your%20sites%20and%20managed%20in%20one%20location.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-781718%22%20slang%3D%22en-US%22%3ERe%3A%20Cross%20site%20lookup%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-781718%22%20slang%3D%22en-US%22%3E%3CP%3EOur%20existing%20SharePoint%20site%20is%20SharePoint%20server%202013.%20there%20we%20used%20Site%20columns%20in%20the%20top-level%20site%20and%20used%20the%20lookup%20field%20to%20all%20subsite.%20this%20feature%20is%20not%20supported%20SharePoint%20Online%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-781850%22%20slang%3D%22en-US%22%3ERe%3A%20Cross%20site%20lookup%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-781850%22%20slang%3D%22en-US%22%3EThis%20scenario%2C%20in%20the%20way%20it%20worked%20in%20your%20SharePoint%202013%20environment%20with%20subsites%2C%20still%20works%20exactly%20the%20same%20in%20SharePoint%20Online%20and%20is%20also%20supported.%20Perhaps%20you%20should%20consider%20moving%20to%20more%20modern%20site%20structure%20using%20multiple%20site%20collections%20and%20hub%20sites%20but%20that's%20another%20topic.%3CBR%20%2F%3E%3CBR%20%2F%3E%22Cross%20site%22%20typically%20refers%20to%20the%20use%20of%20multiple%20site%20collections.%20Having%20lookups%20across%20site%20collections%20is%20not%20supported%20out%20of%20the%20box.%3C%2FLINGO-BODY%3E
Contributor

We are using SharePoint online we would like to access top-level site list data to subs site.

 

for example, we created the customer list in the top-level site. we need to use this data to all subsite list.

 

how we can do this?

5 Replies
Unfortunatelyh this is not possible with SPO Today, so to meet this requirement you need custom development

@Jeyganeshthird-party solutions exist for these kind of scenario's. I know they exist but haven't used them myself.

 

However, you could consider to make use of Managed Metadata Term Sets instead of SharePoint lists. You could for example create a Customers Term Set to store the most important data to be able to identify a customer and reference this using Managed Metadata columns from all your subites. If you need to store more data around these same customers you might still also have your central "Customers" list optionally also pointing to this same Term Set and create a custom developed synchronization mechanism to prevent maintenance of your customer lists in more than one place.

 

Hope this helps!

Depending on the list providing data you might be able to get by with utilizing Managed metadata, which you can setup lists of data which can be used as columns in all your sites and managed in one location.

Our existing SharePoint site is SharePoint server 2013. there we used Site columns in the top-level site and used the lookup field to all subsite. this feature is not supported SharePoint Online?

This scenario, in the way it worked in your SharePoint 2013 environment with subsites, still works exactly the same in SharePoint Online and is also supported. Perhaps you should consider moving to more modern site structure using multiple site collections and hub sites but that's another topic.

"Cross site" typically refers to the use of multiple site collections. Having lookups across site collections is not supported out of the box.