Site Loader

There is no guarantee that all of these features will be addressed. However, here is a small list of what we currently intend to include in future updates. In fact, many of these features already exists in the program, but we haven’t created an interface for the user to manage them (yet). If there is a specific feature you’d like to see or a bug you’d like to report, please email: These updates are included in your purchase. 

Favorites Section: This would allow users to have a quick way to find libraries and lists they use often.

Recycle Bin Reference: This feature is mostly for administrators, this would make it much easier to find, delete, and restore recycled documents. 

List / Library creation: The application currently only manages files and list items. List and Libraries cannot be copied in their entirety. But, it is the intention that entire sites will be able to be copied between site collections and/or tenants.  Wholesale site copying will likely not be available until the second version of the application.

User mapping: An interface will need to be developed to manage user mapping. Currently, the Navigator always attempts to assign the same user account when copying files between libraries.

Column Mapping: The Navigator attempts to set the values of columns of the same name when copying files between libraries. It ignores any columns that do not exist in both libraries. A UI will need to be developed to allow users a way to configure how columns get mapped.

Edit all columns: Currently, only text fields (columns) can be edited within the UI. Where any column value can be copied, the UI hasn’t yet been implemented to allow the user to change other column-types.

Check-in / Check-out support: This is more a concern for on-premises versions of SharePoint, as Microsoft is moving away from checking out files within SPO. As with many things, this needs an interface to allow users to configure how checked out files must be dealt with. Currently, files that are checked out will not be overwritten.

Logging: All errors are currently displayed in the UI, and the user is allowed to make a choice when appropriate. However, there should be an unattended mode, where errors are simply logged, and the application continues without prompting the user. In this case, an error log will be very important.

UI to manage local data: Currently, all the SharePoint metadata is captured in a few local databases. Mostly, this makes the application exponentially quicker while navigating folders that have already been browsed. However, a side-effect is that it’s possible to navigate the folder metadata even when the site is not available/offline. This said, these local databases may have sensitive metadata the user might want to manage or purge from the database. This is especially true if the computer is a shared computer. This can be done manually, but there should be an interface to make managing the cache easier.

Bulk Modify: Modifying a bunch of item fields at once is very handy for administrators who are trying to manage metadata. An interface needs to be developed to do this. This will not be implemented until after all fields are editable in the UI.

Flatten Folders: Folders are not a good way to manage metadata. There are many articles on why folders do not make for good metadata. We will not get into ‘why?’ here. That said, turning folders into metadata is a laborious task to do manually. There needs to be a UI to make it easy to map folders to columns, so that libraries can be flattened.

Search: Expose SharePoint’s search in the application interface. SharePoint’s search will have better results than anything the Navigator will be able to present (e.g. The Navigator is working with cached data and does not have file contents). Exposing SharePoint search would be useful as a discovery tool.Copy/Paste: Simply not implemented yet. It would be exactly the same functionality as drag & drop.

PowerShell Functionality: Adding some scripting would be relatively easy to include. However, there are licensing issue we must consider before adding in PowerShell functions.

Post Author: marc