Managed Metadata for Customer and Project List

%3CLINGO-SUB%20id%3D%22lingo-sub-1863756%22%20slang%3D%22en-US%22%3EManaged%20Metadata%20for%20Customer%20and%20Project%20List%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1863756%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20we%20want%20to%20store%20our%20project%20and%20customer%20documents%20on%20SharePoint%20online.%20We%20want%20to%20create%20lists%20for%20the%20customer%20and%20project%20lists%2C%20also%20use%20those%20values%20on%20document%20management.%20Structure%20will%20be%20like%20this%3A%3C%2FP%3E%3CP%3E-%20Customer%20A%3C%2FP%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20Project-1%3CBR%20%2F%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20Project-2%3C%2FP%3E%3CP%3E-%20Customer%20B%3C%2FP%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3BProject-3%3C%2FP%3E%3CP%3EWhich%20solution%20would%20be%20better%2C%20creating%20two%20termset%20for%20customers%20and%20projects%20or%20one%20hierarchical%20termset%3F%20I've%20attached%20two%20examples.%20Thanks%20for%20your%20help.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1863756%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-1864209%22%20slang%3D%22de-DE%22%3ESubject%3A%20Managed%20Metadata%20for%20Customer%20and%20Project%20List%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1864209%22%20slang%3D%22de-DE%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F37004%22%20target%3D%22_blank%22%3E%40azelmas%3C%2FA%3E%2C%20as%20a%20formefr%20Access%20Database%20architect%20I%20recommend%20Solution%202.%20%22Customers%22%20for%20me%20are%20one%20entity%20as%20well%20as%20another%20entity%20with%20the%20Projects.%20Projects%20are%20not%20just%20another%20Property%20or%20each%20Customer.%20One%20Customer%20can%20have%20multiple%20projects%20with%20us%2C%20this%20will%20be%20on%20my%20mind.%20But%20from%20the%20perspective%20of%20Dynamics%20365%20Solution%201%20is%20also%20an%20option%2C%20beyond%201%3An%20relationships.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20this%20helps%2C%20Greets%2C%20Eva.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1864489%22%20slang%3D%22en-US%22%3ERe%3A%20Managed%20Metadata%20for%20Customer%20and%20Project%20List%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1864489%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F37004%22%20target%3D%22_blank%22%3E%40azelmas%3C%2FA%3E%26nbsp%3BI%20would%20consider%20a%20combination%20of%20the%20two%20if%20you%20need%20to%20use%20a%20metadata%20column%20representing%20just%20customers.%20Create%20a%20Customers%20term%20set%20and%20in%20the%20Projects%20term%20set%2C%20re-use%20the%20Customer%20term%20from%20the%20Customer%20term%20set.%20That%20way%2C%20you%20have%20an%20opportunity%20to%20have%20term%20set%20with%20just%20Projects%20and%20another%20with%20just%20Customers%20-%20and%20you%20can%20filter%20the%20Projects%20list%20by%20Customer%20if%20you%20need%20to.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi, we want to store our project and customer documents on SharePoint online. We want to create lists for the customer and project lists, also use those values on document management. Structure will be like this:

- Customer A

        Project-1
        Project-2

- Customer B

       Project-3

Which solution would be better, creating two termset for customers and projects or one hierarchical termset? I've attached two examples. Thanks for your help. 

4 Replies

Hi @azelmas, as a formefr Access Database architect I recommend Solution 2. "Customers" for me are one entity as well as another entity with the Projects. Projects are not just another Property or each Customer. One Customer can have multiple Projects with us, this will be on my mind. But from the perspective of Dynamics 365 Solution 1 is also an option, beyond 1:n relationships. 

 

Hope this helps, Greets, Eva.

@azelmas I would consider a combination of the two if you need to use a metadata column representing just customers. Create a Customers term set and in the Projects term set, re-use the Customer term from the Customer term set. That way, you have an opportunity to have term set with just Projects and another with just Customers - and you can filter the Projects list by Customer if you need to.

@Eva Vogel Thank you for your reply. 

@Susan Hanley Thank you for your reply.