Skip to main content

​
Why can I connect a SharePoint library through a connector called “File from OneDrive”?

Microsoft Graph exposes personal OneDrive, OneDrive for Business, and SharePoint document libraries all as drives behind a single API, so one connector reaches all three surfaces. During setup, the drive picker lists every drive the authenticating Microsoft account can access, and each entry is one of three types: a personal drive, a business drive, or a SharePoint document library. Selecting a SharePoint library is expected and supported — the chosen drive simply determines which surface the file is read from. The account used to authenticate must have access to whichever drive is selected.

​
Why did my File from OneDrive data source get disconnected?

On each sync the connector searches the configured drive (and optional folder) for a file matching the file type and any filename filter. If that search returns no matching file after paging through all results, the connector raises NO_FILE_MATCHING_SETTING and disconnects the data source, which then has to be reconnected and reconfigured. The most common causes are a file that was renamed, moved to a different folder or drive, or deleted, or a filename filter that no longer matches the file. To recover, confirm the file still exists in the expected location and that its name still matches the configured filter, then reconnect the data source. See How to connect File from OneDrive to Adriel for the reconnection steps.

​
Why isn’t my file found when it sits in a subfolder?

On a personal OneDrive drive with no folder selected, the search is limited to files at the drive root, and files inside subfolders are excluded even when they match the file type and filter. The fix is to select the folder that contains the file during setup, which scopes the search to that folder. On business and SharePoint document-library drives this root-only restriction does not apply, but selecting the folder is still the most reliable way to pin the intended file.

​
Can I import an Excel (XLSX) file?

No. This connector reads CSV files only, so an Excel workbook cannot be selected during setup. For an Excel-based source, the file can be saved or exported as CSV in OneDrive and then imported, or a connector that accepts Excel directly can be used instead — for example, File from Email or Amazon S3. The first row of the CSV must contain column headers, because the available fields are derived from those headers.

​
Can one data source import more than one file?

No. Each data source binds to a single file. To bring in a second file, create a second File from OneDrive data source pointed at that file. Fields, metrics, and breakdowns are then defined per data source from the columns of each imported file.

​
Why don’t my latest file edits show up immediately?

The connector reads from a cached copy of the file that is refreshed on a schedule rather than at dashboard load, so edits saved in OneDrive appear only after the next successful sync. New columns added to the file also become available on the next sync, once the cached field metadata is refreshed. For the sync schedule, see the File from OneDrive data reference.

​
How much history does this connector import?

Each sync reflects the current contents of the configured file, so the amount of history available depends on the rows the file itself contains rather than on how long the data source has been connected. To report on a longer period, keep the historical rows in the file. When a column is mapped as the date field during setup, that column drives date-range filtering on the dashboard; without a mapped date column, all rows are treated as a single snapshot regardless of the selected date range.