Mar 25 2019 04:46 AM
Mar 25 2019 04:46 AM
In order to anticipate the adoption of SharePoint in a company (until the company matures and the conditions are more met to consider SharePoint use), I had started to prepare "the ground" by identifying and collecting some of the company's repositories (spread over multiple servers and unclassified) and centralizing them and managing in Excel in a table what would become the future metadatas. This technique made it possible to emulate tomorrow's research in a SharePoint environment.
However, now I would like to start going further by loading all these elements into a Sharepoint library. But, I don't know how to do this import process in SharePoint to reconcile the properties of each file (one line per file in my Excel table) and the files themselves that are not linked.
What would be the appropriate approach?
Thank you for your ideas?
Regards
Mar 25 2019 06:49 AM
Mar 25 2019 06:57 AM
@Deleted
What kind of properties are contained in the Excel file?
Are these properties like modification date, size, ...
or do the properties contain custom metadata like organisational unit, customer name, ...
Paul | SLIM Applications
Mar 25 2019 07:06 AM
@Paul de Jong The properties contain metadata such as: document type, scope, supplier etc....
Mar 25 2019 07:10 AM
Am I to understand that"'there is no possibility of massively importing files and their associated properties in "only one time"? Because, then, the objective is to then manage this only in SharePoint and natively. Because I don't want to re-enter all these properties on hundreds of files.
Mar 25 2019 07:22 AM
@Deleted Another option would be to import all the files into the library and then use the quick edit feature to do a mass update of properties.
Mar 25 2019 07:29 AM
Mar 25 2019 07:45 AM
Is it in the idea that this means that we should consider copying and pasting for all columns and rows? That's what I think I understand in your answer and that I'm a little afraid of.
I deduce that I have to give up the idea of finally being able to import metadatas through a mechanism that ultimately does not simply exist.
Mar 25 2019 07:49 AM
Solution@Deleted Only populate the value in the first column and then "grab" it in the bottom right corner like Excel and drag it down the rest of the columns.
Agreed this is a little laborious however the alternative would be a 3rd party tool or a PowerShell script that uses the Excel file as the initial metadata source.
Mar 25 2019 07:49 AM
Solution@Deleted Only populate the value in the first column and then "grab" it in the bottom right corner like Excel and drag it down the rest of the columns.
Agreed this is a little laborious however the alternative would be a 3rd party tool or a PowerShell script that uses the Excel file as the initial metadata source.