uSyncCore.Config

The core config file, controls how uSync serializes and deserializes objects. as the core is used by other components changing these settings changes the behavour of all parts of uSync.

Mappings

When you move items between instances of umbraco, internal IDs will change, so you're template might have an id of 1023 on you're instance of umbraco, but for a fellow developer it might be 1123, it all depends in what order things have been created.

unfortunately a lot of umbraco configuration uses these IDs to identify things, so when you move instances you can loose these configuration settings.

uSync uses mappings to translate IDs between umbraco instances. when exporting an item, uSync takes an ID and translates it to something more generic, and when importing it takes that generic value and converts it to the local id on the target umbraco instance. Mostly this 'just works', but for somethings (notably datatypes) it needs configuration.

Value Mapper Setting.

<uSyncValueMapperSettings>
      <DataTypeId>Umbraco.MultiNodeTreePicker</DataTypeId>
      <MappingType>content</MappingType>
      <ValueStorageType>json</ValueStorageType>
      <ValueAlias>startNode</ValueAlias>
      <PropertyName>id</PropertyName>
      <PropertySplitter>0</PropertySplitter>
      <PropertyPosistion>0</PropertyPosistion>
    </uSyncValueMapperSettings>

Most of these values exsit to help uSync zone in on the exact place where the ID is stored, you don't need to provide all the elements (although without a matching DataTypeId no mapping will be attempted) but the more info you provide the less chance that uSync will miss identify something as an ID when it's not.

MappingType: type of object ID will relate to (content (inc media), tab, mediatype, doctype)

ValueAlias: What is the name of the alias where the ID is stored.

ValueStorageType: type of storage (json, text, Number) -