# File handlers
When files are dropped inside the monitor directory the file is picked up by a specific handler based on the filename and extension. For excel both xls and xlsx are supported.
When the file is handled by the service, the file is renamed to: active.<filename>. When the handler is finished the file is moved to the completed or error directory.
# Pages (excel)
Use this format to create/update site pages. The filename should contain PageSet and format is xls(x)/csv.
The following columns are required:
- Url or MatterCode (/ClientCode)
- PageSet or PageSets or both.
- Additional columns are converted to properties (can be used as variables in the pageset)
The page that is defined in pageset is created/updated in the site via the url or via the client/mattercode and will be the homepage.
The pages that are defined in pagesets are created/updated in the site via the url or via the client/mattercode.
# QuickLaunchNavigation (excel)
Use this format to create/update the QuickLaunchNavigation in a site. The filename should contain QuickLaunchNavigation and format is xls(x)/csv.
The following columns are required:
- Url or MatterCode (/ClientCode)
- SiteSet
- Additional columns are converted to properties (can be used as variables in the siteset)
The QuickLaunchNavigation that is defined in the siteset is created/update in the site via the url or via the client/mattercode. Only items that are marked as Remove are removed.
# TopNavigation (excel)
Use this format to create/update the TopNavigation in a site. The filename should contain TopNavigation and format is xls(x)/csv.
The following columns are required:
- Url or MatterCode (/ClientCode)
- SiteSet
- Additional columns are converted to properties (can be used as variables in the siteset)
The TopNavigation that is defined in the siteset is created/update in the site via the url or via the client/mattercode. Only items that are marked as Remove are removed.
# CopySearchSchema (excel)
use this format to copy a search schema from one SiteCollection to a different SiteCollection. The filename should contain CopySearchSchema with format xls(x)/csv.
The following columns are available:
- Origin (required)
- Target (required)
- Force
- CreateCrawledProperties
- Debug
Origin is the SiteCollection URL from which the search schema is copied.
Example https://tenant.sharepoint.com/sites/siteCollection1.
Target is the Site Collection URL where the search schema will be copied.
Example: https://tenant.sharepoint.com/sites/siteCollection2
Force is a boolean used for when the site collection already has a search schema and this needs to be overwritten. Do mind this will not overwrite aliases. The aliases that need to be removed will be returned in the result message and need to be removed manually.
Example: True
CreateCrawledProperties is a boolean that controls whether crawled properties referenced in the origin schema should be auto-created on the target site. When set to True, crawled properties with ows in their name will have their SchemaId reset so SharePoint creates them during import. This is useful when the target site does not yet have the crawled properties that the managed properties in the schema are mapped to.
Example: True
Debug is a boolean that outputs the raw XML of the origin search schema to the console for troubleshooting purposes.
Example: True
# Retry behavior
The schema import automatically retries up to 5 times (with a 5-second delay between attempts) when SharePoint returns a "Service unavailable" error. This handles transient failures that can occur during search schema operations on SharePoint Online.