Handling document localization to subfolder

[travelo94]

Hi , i encountered a problem when i created document localization to subfolder related to parent document localization the control shows me the subfolder allows me to open it in sharepoint and add files etc. but doesnt show content.

when i open the folder in sharpoint all of the uploaded files with control are avaliable

[vantruonginfo]

me too :)

[ilia-sokolov]

The issue is being investigated and fixed.

[beeper77]

I also have the problem with empty folders. @ilia-sokolov is it really fixed in the Solution zip file? I used the SPFileExplorer as a Subgrid in a Main form. Btw, I love the control :)

Update: It's working better if the Control is the only one in a tab. In my first test I used it in a section on the main tab. Maybe you can look at this topic.
I also have another little glitch. I use a SharePoint document link at company level. The company can have multiple projects and the project table also have a sharepoint link. to make it more interesting, in SharePoint the project folders are below the company folders.

Here you can see the SharePoint folders at Company level. The SPMigration Folder is a Project in the Project Table and have its own connection between SP - Dataverse.

This is the content of the SPMigration folder.

From the Company view in the power app I have the following glitch:

The Rootfolder shows the wrong folders and a duplicate of the files. The content normally is below the spmigration folder and not at root level. Also the 2 root folders are missing. The navigation on the left site is also jumping around.
Any ideas?

[beeper77]

I need to revise my comment. In my analysis, I initially assumed the wrong cause. It seems that the problem arises in the file "FullFileExplorerProps" in the function "initFullFileExplorerProps". A list of the content is created there: currentFolderContent = dataSet.sortedRecordIds.map((recordId) => {...
The dataSet comes from:
const dataSet = context.parameters.documentsDataSet;
So it comes directly from the Dataverse. For whatever reason, not all elements are contained in this dataset. The elements of the root level are missing, i.e. everything under SP Migration is included. "Internal" etc. is missing. However, Dataverse's own view of the documents shows the structure correctly.

[ilia-sokolov]

Dear @beeper77,
The control reuses filters of the view that it is applied. Could you please check if there are no conditions that limit the amount of data that is returned? Would you also mind to create a separate issue for this problem?