Copy To

Note: If using a Commit Task then the inverse of the Read and Commit mapping is used and the Copy To mapping is ignored.

In Copy To, the Source is the Session's Schema and the Target is the Schema of the Data Store that is being copied to.

Creating Copy To Mappings

After configuring a Data Store, you can automatically add mappings by clicking the Refresh button if they aren't already populated. This can be further customised by selecting/deselecting existing classes and attributes, and by adding custom classes and attributes where necessary.

Note: Right click a class and select Expand All or Collapse All from the context menu to expand or collapse all classes and their attributes.

Only checked items will be used as part of the Schema, meaning only those classes and attributes will be included for exporting from 1Integrate to the Data Store.

Copy To Mapping Toolbar Icons

Icon	Description
	Refresh Reads the schema from the Data Store. Populates the mapping with the inverse of the Read and Commit mapping. Start with this operation to add all classes to the mapping.
	Delete all mappings Returns the mapping to its default state.
	Select Filters Typing in the Search Class or Search Attribute fields will filter the selection of Classes or Attributes. Additionally, selecting the Hide options will mean the filter will not include any or all of: Disabled Classes, Disabled Attributes, Custom Classes or Custom Attributes.
	Include Class/Attribute Checking the box next to Source includes all Classes and Attributes in the Schema. Checking a Class includes all of its Attributes. Checking an Attribute will include it.
	Don't Include Class/Attribute Unchecking a box removes it from the Schema. It works in the inverse of the way to include Classes and Attributes.

Viewing Attribute Metadata

Each class contains attributes that also store metadata based on its type. To view the metadata of an attribute, hover over the info icon that is next to the attribute name.

Unique Keys

You can set Unique Keys for attributes in a class. With a Unique Key set, the attribute cannot be disabled.

To set or remove a Unique key, right click the attribute and select the option to set/remove the key.

The icon for showing an attribute is set as a Unique Key

By default, this will set to the unique key that has been defined in the source data (e.g. the primary key of a table from a database).

Foreign Keys

Data Stores that refer to other Data Stores will mark which classes and attributes within their Schemas are foreign keys. This is marked with a icon which can be hovered over to show the class and attribute with the Data Store that it is from.

When an class or attribute is referenced by another Data Store it is marked by a Referenced Key icon. Hovering over this will list each instance of this class or attribute being used as a foreign key.

An example demonstrating the application of rules using Ontology to road features split into A-road, B-road and Motorways — id:NUMERIC is being referenced in other Data Stores as a foreign key