A Translation is a Fabric Studio object used for creating data transformation rules. The Translation editor exists in the Fabric .NET Studio only. In the Web Studio, the translations are presented as XML files and can still be used by the Fabric server, without a dedicated editor for editing them in the Web Studio.
The Web Studio introduces a new object - MTable - to be used for defining the data transformation rules via several dedicated Actors.
A Translation is a Fabric Studio object that transforms data from one set of valid values to another in order to enable the execution of various transformation rules. Translation objects can be used as decision tables in Fabric and can be defined either on a Shared Object level or on a Logical Unit level or both.
There are several options for populating data in a Translation in the Fabric Studio:
Click for more information about Data Population in Translations.
A Translation can be used when a table population or project function needs to apply transformation rules. For example:
Translations are defined via the translation window which has two tabs:
The following icons are displayed at the top of the Translation Schema tab:
Icon |
Action |
Print translation definition. |
|
Export translation definition as an Excel file. |
|
Filter definition by one or more columns. |
|
Toggle summaries. |
|
Toggle groupings. |
The following options define system behavior when a matching translation is not found. Select an option from the dropdown list on the bottom of the Translation Schema tab. The Use Default option is always defined when a new translation is created and can be modified when needed.
The structure of a translation is defined in the Translation Schema tab and is comprised of Input and Output fields:
A Translation Schema has the following structure:
Parameter Property |
Description |
Title |
Name of the parameter. |
Direction |
Indicates whether a parameter is Input or Output. |
Type |
Parameter type. The following types are supported:
|
Length |
Field length, max number of characters. Populated automatically for several types, for example Project function. Ignored for Blob and Auto increment types. |
Match |
Optional: A Regular expression that indicates a restricted format for each value and is applied for manual Translation population only. Ignored for Blob and Auto increment types. |
Default Value |
Default value used when no entry is found (relevant for an Output setting). |
Allow NULL |
True / False indicates whether the setting can be NULL. Default is True. |
Comment |
Optional: Additional information. |
Note that all Translation Schema constraints are only applied in the Fabric Studio. The Fabric Server uses the data only and not the Schema’s information. The following icons are displayed next to each Translation setting:
Icon |
Action |
Deletes the Translation row. |
|
Moves the Translation row up. |
|
Moves the Translation row down. |
A Translation is a Fabric Studio object used for creating data transformation rules. The Translation editor exists in the Fabric .NET Studio only. In the Web Studio, the translations are presented as XML files and can still be used by the Fabric server, without a dedicated editor for editing them in the Web Studio.
The Web Studio introduces a new object - MTable - to be used for defining the data transformation rules via several dedicated Actors.
A Translation is a Fabric Studio object that transforms data from one set of valid values to another in order to enable the execution of various transformation rules. Translation objects can be used as decision tables in Fabric and can be defined either on a Shared Object level or on a Logical Unit level or both.
There are several options for populating data in a Translation in the Fabric Studio:
Click for more information about Data Population in Translations.
A Translation can be used when a table population or project function needs to apply transformation rules. For example:
Translations are defined via the translation window which has two tabs:
The following icons are displayed at the top of the Translation Schema tab:
Icon |
Action |
Print translation definition. |
|
Export translation definition as an Excel file. |
|
Filter definition by one or more columns. |
|
Toggle summaries. |
|
Toggle groupings. |
The following options define system behavior when a matching translation is not found. Select an option from the dropdown list on the bottom of the Translation Schema tab. The Use Default option is always defined when a new translation is created and can be modified when needed.
The structure of a translation is defined in the Translation Schema tab and is comprised of Input and Output fields:
A Translation Schema has the following structure:
Parameter Property |
Description |
Title |
Name of the parameter. |
Direction |
Indicates whether a parameter is Input or Output. |
Type |
Parameter type. The following types are supported:
|
Length |
Field length, max number of characters. Populated automatically for several types, for example Project function. Ignored for Blob and Auto increment types. |
Match |
Optional: A Regular expression that indicates a restricted format for each value and is applied for manual Translation population only. Ignored for Blob and Auto increment types. |
Default Value |
Default value used when no entry is found (relevant for an Output setting). |
Allow NULL |
True / False indicates whether the setting can be NULL. Default is True. |
Comment |
Optional: Additional information. |
Note that all Translation Schema constraints are only applied in the Fabric Studio. The Fabric Server uses the data only and not the Schema’s information. The following icons are displayed next to each Translation setting:
Icon |
Action |
Deletes the Translation row. |
|
Moves the Translation row up. |
|
Moves the Translation row down. |