How do 'Copy Data' activities actually convert data types?

---

Definition of Interim Data Types:

• Interim data types are not explicitly defined in the documentation.  They are used internally by the system to facilitate data type conversion during the copy process.

---

Those interim data types should be documented - especially because some interim types are incompatible with certain source/destination types. 

Overriding Interim Type Mapping:

• You can override type mappings by configuring the type conversion settings in the Mappings tab of the Copy activity

---

That is not the interim types. That is the source/sink types. I understand you can configure the source/sink data types.

---

Documentation on the “Translator” Object:

• Detailed documentation on the “translator” object or properties for source/sink mapping objects is not readily available. The JSON code view allows you to see and edit the configurations, but specific properties related to the translator object are not well-documented.

---

There should be documentation on this. These are class representations, I don't see why we wouldn't be able to view the class methods and properties - at least the ones that are accessible to the Pipeline. Otherwise, there is no point in viewing the JSON. Might as well just remove it.

---

Modifying the Conversion Process:

• To modify the conversion process, you can use the type conversion settings in the Mappings tab. For example, you can specify custom formats for date and time conversions.

---

This is half-true, there are *some* configurations you may set - but those only work for certain source types. If I have an unusual type - right now I have no choice but to manually use a SQL Convert on the source, putting extra load on my SQL server. I shouldn't have to - Fabric should be more than capable of handling any SQL data type.