Overview

Due to recent changes in Quicktext, it is no longer possible to load templates and scripts directly from local or OneDrive folders.

To keep our workflow operational, we use a workaround:

We maintain:

• One template file
• One script file
• Both are stored in a shared OneDrive folder
• These files are then combined into a single JSON configuration file
• The combined file is uploaded and shared via SharePoint (HTTPS link)

This allows Quicktext to continue working using a remote file instead of local storage.

File Structure

In OneDrive, we maintain:

• 2026-sharing-templates.json → contains all templates
• 2026-sharing-scripts.json → contains all scripts

These are the source files and should be updated when changes are needed.

How the Workaround Works

We use a PowerShell script to:

• Read both JSON files
• Extract templates and scripts
• Combine them into one file
• Output a new file ready for upload

START Script

`$templateFile = "2026-sharing-templates.json"
$scriptFile = "2026-sharing-scripts.json"
$outputFile = "2026-quicktext-upload.json"

$template = Get-Content $templateFile -Raw | ConvertFrom-Json
$script = Get-Content $scriptFile -Raw | ConvertFrom-Json

$output = @{
templates = $template.templates
scripts = $script.scripts
}

$output | ConvertTo-Json -Depth 20 | Set-Content $outputFile -Encoding UTF8

Write-Host "Config file created: $outputFile"`

END Script

SharePoint File (Final Output)

After running the script, the generated file is uploaded and shared via SharePoint you can put this in Quicktext.
Don't forget to add ?download=1

Workflow Summary

• Edit templates or scripts in OneDrive
• Run the PowerShell script
• Generate updated 2026-quicktext-upload.json
• Upload/overwrite the file in SharePoint
• Quicktext loads the updated version via the shared link

• Important Notes

Do not edit the SharePoint file directly

• Always update the source files in OneDrive
• Always re-run the script after making changes