Community Tip - Did you get called away in the middle of writing a post? Don't worry you can find your unfinished post later in the Drafts section of your profile page. X
I need an infotable that has the path & filenames of all the files in a file repository, irrespective of the path.
Solved! Go to Solution.
@SB_9732186 It works for arbitrary directory hierarchy.
The code gets the hierarchy from the GetDirectoryStructure and then just iterates over it. Here is the InfoTable returned by GetDirectoryStructure.
Here is a bit better commented code
var params = {
infoTableName: "listFiles",
dataShapeName: "FileSystemFileWithLinks"
};
// Initializing empty InfoTable with the appropriate shape
var listFiles = Resources["InfoTableFunctions"].CreateInfoTableFromDataShape(params);
// Getting the directory structure of the repo
var repoDirStructure = Things[repoName].GetDirectoryStructure();
// Iterating through all the directories in the repo
// and merging the list of files in each
for (var el in repoDirStructure.rows) {
var listFiles2 = Things[repoName].GetFileListingWithLinks({
path: repoDirStructure[el]["path"]
});
var params = {t1: listFiles, t2: listFiles2};
listFiles = Resources["InfoTableFunctions"].Union(params);
}
result = listFiles;
The final result returned by the service:
Did you try using BrowseFileSystem service of File Repository?
Hi @mnarang
I have used BrowseFileSystem but that doesn't fit my use case.
Let me give you an example:
The service should return an infotable:
Path Filename
/one file1
/one file2
/one file3
/two file1
/two file2
/two file3
/three file1
/three file2
/three file3
Thanks.
I think direct API is not there for your use case, but you can use existing API to create your service which can give you desired result. For example, BrowseDirectory or BrowseFileSystem will give you everything which is there in the repo on path /, then you need to iterate the previous output and whenever you find fileType as D, you need to execute the service again to get file listing in the directories. At the end you need to have a logic for combining the data/representation as per your use case. There can be other combination as well like ListDirectories+ListFiles, as you will be iterating data and calling this API in the loop, you need to test this solution from performance standpoint.
One more point if you have huge hierarchy of directories then this approach might not work, as you have to deep dive in the directories and execute the service in inner loops.
Is it what you're looking for?
var listFiles = Things[repoName].GetFileListingWithLinks({
path: undefined /* STRING */,
nameMask: undefined /* STRING */
});
var repoDirStructure = Things[repoName].GetDirectoryStructure();
for (var el in repoDirStructure.rows) {
logger.warn("repoDirStructure"+repoDirStructure[el]["path"]);
// Merging files from all subfolders
if (el != 0){
var listFiles2 = Things[repoName].GetFileListingWithLinks({
path: repoDirStructure[el]["path"]
});
var params = {t1: listFiles, t2: listFiles2};
listFiles = Resources["InfoTableFunctions"].Union(params);
}
}
result = listFiles;
if the approach mentioned by @DmitryTsarev works for you, then it is good as it seems to be more simpler and straight forward.
The one above was a quick and dirty code.
Here is the sleeker version (no "init" step in the beginning and thus no "if" inside the loop):
var params = {
infoTableName: "listFiles",
dataShapeName: "FileSystemFileWithLinks"
};
var listFiles = Resources["InfoTableFunctions"].CreateInfoTableFromDataShape(params);
var repoDirStructure = Things[repoName].GetDirectoryStructure();
for (var el in repoDirStructure.rows) {
logger.warn("repoDirStructure"+repoDirStructure[el]["path"]);
// Merging files from all subfolders
var listFiles2 = Things[repoName].GetFileListingWithLinks({
path: repoDirStructure[el]["path"]
});
var params = {t1: listFiles, t2: listFiles2};
listFiles = Resources["InfoTableFunctions"].Union(params);
}
result = listFiles;
Hi @DmitryTsarev ,
The codes that you have provided will only work for a 2-level directory structure, am I correct?
I need it for n-level directory structure.
Thanks.
@SB_9732186 It works for arbitrary directory hierarchy.
The code gets the hierarchy from the GetDirectoryStructure and then just iterates over it. Here is the InfoTable returned by GetDirectoryStructure.
Here is a bit better commented code
var params = {
infoTableName: "listFiles",
dataShapeName: "FileSystemFileWithLinks"
};
// Initializing empty InfoTable with the appropriate shape
var listFiles = Resources["InfoTableFunctions"].CreateInfoTableFromDataShape(params);
// Getting the directory structure of the repo
var repoDirStructure = Things[repoName].GetDirectoryStructure();
// Iterating through all the directories in the repo
// and merging the list of files in each
for (var el in repoDirStructure.rows) {
var listFiles2 = Things[repoName].GetFileListingWithLinks({
path: repoDirStructure[el]["path"]
});
var params = {t1: listFiles, t2: listFiles2};
listFiles = Resources["InfoTableFunctions"].Union(params);
}
result = listFiles;
The final result returned by the service:
Hi @SB_9732186.
If you feel your question has been answered, please mark the appropriate response as the Accepted Solution for the benefit of others with the same question.
Regards.
--Sharon