I am using DocsList for a large project and it works great. Recently, errors have appeared, and basically they have roots with getting a folder or file. When I was doing research, I found that DriveApp was updated. The problem is that DriveApp has no search options like DocsList.
For example, if I had a folder structure like this:
Root -Main Folder 1 --Folder 1 --Folder 2 -Main Folder 2 --Folder 1 --Folder 2
To get the folder "Folder 1" in "Main folder 2", I can add a search parameter like this: DocsList.getFolder ("Main folder 2 / Folder 1")
With DriveApp, I just don’t understand how to work with it. From what I understand, I need to do something like this for DriveApp:
var mainFolders = DriveApp.getFoldersByName('Main Folder 2'); while (mainFolders.hasNext()) { var mainFolder = termFolders.next(); var subFolders = termFolder.getFoldersByName('Folder 1');
So, if I had a deeper folder, I would have to expand it even more.?
I feel that instead of simplifying the situation, they have complicated the work of FileIterators and FolderIterators. And just making it hard to “get” a file or folder in code terms.
So basically this question is to find out how a person who uses DocsList to navigate and edit files and folders on a drive can go to DriveApp and achieve the same.
Small / discrete examples of different scenarios would be really helpful. I can take it from there. I will edit this more if you guys think that I don’t understand what I need help about.
source share