Power Platform Community Forum Thread Details

Actually I don't know if it's called "library" but when connecting from Sharepoint using canvas, it only detects "Documents" which are the "shared documents"; the objective of my development is to obtain files contained in an internal folder of "shared documents" and this is a bit deep in navigation, in addition to this the Sharepoint site in which I am working has a huge number of files (it is the site of the company where I work) and when making the connection to "shared documents" in canvas, it only brings me 2000 "records" (yes, I increased the limit allowed by delegation) and in those 2000 records the file I need does not appear.

An example of that internal folder would be "Shared documents/Data/Project/Processed" and I need to connect directly to "Processed" without accessing the other locations that this library has.

Then this thing of creating libraries occurred to me, since in a Sharepoint site of the company where I work there is in addition to "Documents", there is another "library" (excuse me if I say it wrong), so my question is that can you create a "library" that points to an internal folder of another library and thus be used as a direct connection in canvas?

PS: I tried filtering from the "Documents" connection but many fields have that apparent limitation of delegation and more because of the access that the company gives me to access those files, it prevents me from obtaining the information I need; By the way, the file or files I am looking for are particular and do not use galleries, on the other hand, a non-delegable property is "Title" but that property is not filled in and I have to make a Power Automate flow but I have to validate that with my bosses.

Categories:

Building Power Apps

@MasterRA

I don't really like posting links as answers here in the forums but this issue has been solved by a number of notable PowerAppsters so I'm going to link one here. @mdevaney has a blog post that I think is just what you need?

https://www.matthewdevaney.com/power-apps-navigating-folders-subfolders-in-a-sharepoint-document-library/

One other thing I will mention is to try and build Metadata into your Doc Lib where possible, instead of using many folders.

As an example, if you have Folder A and the usually way docs are stored in this folder is in Year and Month Sub-folders then instead of the sub-folders, use metadata columns for Year and Month. This will also allow for specific filtering via PowerApps and greatly assist with eliminating delegation issues you may come up against.

A best practice I used to answer if I need a folder or not is permissions. Say Folder A from above needs to be restricted to a certain Group of users, then the answer is 'Yes' Folder A is needed. However, if Folder A doesn't need any users access restrictions then consider a new Metadata column at that level where the field contents would look like: Folder A, Folder B, Folder C ...