Translations Overview

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.

Click for more information about MTables.

What Is a Translation?

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.

  • Translations defined on a Shared Object level can be used in all objects in a project.
  • When a Translation is used for web services, it must be defined on a Shared Object level.

There are several options for populating data in a Translation in the Fabric Studio:

  • Manual population via the Translation window.
  • Retrieving the Translation’s data from a file. The data is loaded from the file once.
  • Retrieving the Translation’s data from a database to create a Dynamic Translation. The data is loaded from the database during each sync process.

Click for more information about Data Population in Translations.

How Can I Use a Translation in Fabric?

A Translation can be used when a table population or project function needs to apply transformation rules. For example:

  • When there are several source systems, each having a list of valid values for the customer type attribute. The translation defines one unified set of valid values for the target (Fabric) and transformation rules from the input value (source) to the output value (target).
  • When there are several DB interfaces, the translation can map between the system name and its DB interface name to be used in the code.
  • When there is a list of attributes or business rules in the LU, the translation can define an SQL query for each attribute or business rule.

Translation Window

Translations are defined via the translation window which has two tabs:

  • Translation Schema tab, defines the Translation Schema properties. Each column in a Translation Schema must be either input or output and can have different data types.
  • Translation Data tab, which is populated by the translation’s values in the input and output fields. The data can be populated in a translation in several ways.

Translation Schema Tab Icons

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.

Translation Options

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.

Option

Description

Use Default

Use the value defined in the Default Value column in the Translation Schema tab.

Reject Record

Rejects a single record.

Reject Instance

Rejects the entire instance.

Report and Use Default

Reports the missing value and uses the default value.

Translation Schema

The structure of a translation is defined in the Translation Schema tab and is comprised of Input and Output fields:

  • There can be one or more than one Input field.
  • A translation’s primary key is a combination of all translation input fields. The primary key defines which translation entries are used to apply the data transformation rules and therefore must be unique.
  • An output value does not need to be unique and can be repeated.

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:

  • Integer.
  • Real.
  • Text.
  • Blob (applicable only for a DB that supports Blob).
  • Auto increment. Creates an automatic sequence starting from 1 and incremented by 1. The value cannot be updated by the user.
  • Project function. Fabric provides a list of all functions available in the project. The value must be selected from the dropdown list.
  • LUDB function, applicable for Translations on LU levels only. Fabric provides a list of LUDB functions available in the LU. The value must be selected from the dropdown list.
  • LUDB table, applicable for Translations on LU levels only. Fabric provides a list of LU tables available in the LU. The value must be selected from the dropdown list.
  • DB Interface. Fabric provides a list of the Interfaces in the project. The value must be selected from the dropdown list.
  • SQL. Fabric enables testing the SQL query by opening a Query Builder from the Table Schema window.
  • LU Name, applicable for Translations on a Shared Objects level only. Fabric provides a list of all LU available in the project. The value must be selected from the dropdown list.

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.

 

Translations Overview

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.

Click for more information about MTables.

What Is a Translation?

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.

  • Translations defined on a Shared Object level can be used in all objects in a project.
  • When a Translation is used for web services, it must be defined on a Shared Object level.

There are several options for populating data in a Translation in the Fabric Studio:

  • Manual population via the Translation window.
  • Retrieving the Translation’s data from a file. The data is loaded from the file once.
  • Retrieving the Translation’s data from a database to create a Dynamic Translation. The data is loaded from the database during each sync process.

Click for more information about Data Population in Translations.

How Can I Use a Translation in Fabric?

A Translation can be used when a table population or project function needs to apply transformation rules. For example:

  • When there are several source systems, each having a list of valid values for the customer type attribute. The translation defines one unified set of valid values for the target (Fabric) and transformation rules from the input value (source) to the output value (target).
  • When there are several DB interfaces, the translation can map between the system name and its DB interface name to be used in the code.
  • When there is a list of attributes or business rules in the LU, the translation can define an SQL query for each attribute or business rule.

Translation Window

Translations are defined via the translation window which has two tabs:

  • Translation Schema tab, defines the Translation Schema properties. Each column in a Translation Schema must be either input or output and can have different data types.
  • Translation Data tab, which is populated by the translation’s values in the input and output fields. The data can be populated in a translation in several ways.

Translation Schema Tab Icons

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.

Translation Options

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.

Option

Description

Use Default

Use the value defined in the Default Value column in the Translation Schema tab.

Reject Record

Rejects a single record.

Reject Instance

Rejects the entire instance.

Report and Use Default

Reports the missing value and uses the default value.

Translation Schema

The structure of a translation is defined in the Translation Schema tab and is comprised of Input and Output fields:

  • There can be one or more than one Input field.
  • A translation’s primary key is a combination of all translation input fields. The primary key defines which translation entries are used to apply the data transformation rules and therefore must be unique.
  • An output value does not need to be unique and can be repeated.

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:

  • Integer.
  • Real.
  • Text.
  • Blob (applicable only for a DB that supports Blob).
  • Auto increment. Creates an automatic sequence starting from 1 and incremented by 1. The value cannot be updated by the user.
  • Project function. Fabric provides a list of all functions available in the project. The value must be selected from the dropdown list.
  • LUDB function, applicable for Translations on LU levels only. Fabric provides a list of LUDB functions available in the LU. The value must be selected from the dropdown list.
  • LUDB table, applicable for Translations on LU levels only. Fabric provides a list of LU tables available in the LU. The value must be selected from the dropdown list.
  • DB Interface. Fabric provides a list of the Interfaces in the project. The value must be selected from the dropdown list.
  • SQL. Fabric enables testing the SQL query by opening a Query Builder from the Table Schema window.
  • LU Name, applicable for Translations on a Shared Objects level only. Fabric provides a list of all LU available in the project. The value must be selected from the dropdown list.

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.