Spaces
Apps
Templates
Create
SkySync V3 Documentation
All content
Space settings
Shortcuts
How-to articles
How-to articles
This trigger is hidden
Content
Results will update as you type.
Release Notes
Configuration
FAQ - Frequently Asked Questions
•
Activating SkySync returns an error: SkySync could not acquire a license. Please check...
•
Allow Mapping Passthrough
•
Cannot open database "SkySync" requested by the login
•
Content Filtering in relation to a Publish Job
•
Filtered Files still receive errors
•
Folders who's colors have been changed aren't visible in Navigator
•
How SkySync Stores Credentials
•
What is User Drive mapping?
•
How to determine which version of SkySync is installed
•
Mapped Metadata will not save
•
Metadata Time Stamps rollover to the next day
•
My user mapping settings are missing after changing the connector in the job
•
Newly created folders on the destination not result in new child jobs being created from my Folder Mapping Sync Job.
•
No errors will show to prevent overlapping connectors or jobs
•
Rate Limitations Warning
•
Set the date and time on your computer to be current
•
SkySync Transfer Usage
•
SkySync Won't Load Past the Splash Screen
•
Submitting a SkySync Support Ticket With Portal Architects
•
Use platform specific adjustments to increase initial upload performance
•
What is External Account Mapping Passthrough
•
When do Data Usage Warning Emails Start?
•
Windows Defender Warning When Installing SkySync
•
The file and folder counts are different between file explorer and Analyzer/Inspector
•
Mapping unresolved source and destination accounts
•
What Are Determining Changes?
Installation & Upgrade
Job Control Panel
Storage Providers
•
How-to articles
Getting Started
Advanced Features
SkySync V3 Documentation
/
FAQ - Frequently Asked Questions
/
Mapped Metadata will not save
Summarize
Mapped Metadata will not save
Peter Ransom (Deactivated)
Owned by
Peter Ransom (Deactivated)
Aug 03, 2017
Loading data...
Issue:
When manually mapping metadata the connections are not saved
Reason:
This is a known issue with the software that will be resolved in the next version of the product
Workaround:
Create the metadata connection twice. For example if I click on two metadata objects to map them I will click on them a second time.
{"serverDuration": 64, "requestCorrelationId": "e44dc31e3a1a40aeb00101fcbf8c39ef"}