Forum Discussion
Customer Document Libary: How to organize a libary to store information effectively?
Hi ca_rem,
You should consider using Document Sets.
A Document Set is a group of related documents that you can manage as a single entity. You can create a Document Set in a single step, and then define its characteristics and metadata.
Document Set's were recently updated. LincolnDeMaris posted about the enhancements in this thread:
Thanks, Norman Young . You saved my day again. This is exactly what I want.
But I wonder can we use flow with Document Set. Going deeper into my example above:
Example above:
When a customer is added to Customer List, automatically creates a Document Set name "Customer + ID" in Customer Document List.
More advanced, Example 2: If we have 4 list "Customer List," "Customer Document List", "Order List" and "Order Document List":
- Step 1: Check "Order List" if the first order of customer not exists, automatically creates a Document Set name "Customer + ID" in Customer Document List. If exists, do nothing.
- Step 2: When creating a new Order Item in "Order List", automatically creates a Document Set in "Order Document List"
ca_rem is there a specific reason why you would need separate lists for your customers, orders and documents? You can place all of the customer metadata into your document sets and then add columns to the documents to classify these as orders, with dates, statuses and other information. You can then use views to filter and group the documents to create virtual customers and orders lists. This way your're recording all the data against the documents themselves and not maintaining a separate copy of this information and designing complex Flows to try and synchronise them.
MattyVx .
Thanks for your idea. I see it may a solution if the data of customer not too much, maybe less than 10 columns.
I simply want to group them in the correct form, one side is the list, the other is the document. Anh when I add a document, I only lookup for 1 column in Customer List, instead of fill all the column of the customer.
Or something I missing?