Dataflow Modeling - Term Mapping
      Back to home
      1. biGENIUS-X Knowledge Base
      2. Application Modules
      3. Dataflow Modeling - Term Mapping

      Create a Term Mapping

      Create a Term Mapping

      To create a new Term and its Term Mapping simultaneously in a Model Object, access the Term overview page for a Model Object:

      Then click on the Plus icon:

      The Add Term side panel window is opened with the Term and Term Mapping properties:

      Fill in the following information:

      1. Name: Term's name
      2. Description (optional): Term's description
      3. DataType: The Data Type list depends on the Semantic configuration of the Generator. In this example, you can choose the following Data Types:
      4. Length (optional): Term's maximum length. Relevant for a Data Type varchar, for example. For Data Type varchar(50), the text can have 50 characters.
      5. Precision (optional): Term's precision. It is the number of digits that make up a number. Relevant for a Data Type decimal, for example. For Data Type decimal(38,17), the number can have 38 digits, and 38 - 17 = 21 digits on the left.
      6. Scale (optional): Term's scale. It is the number of digits to the right of the decimal point in a number. Relevant for a Data Type decimal, for example. For Data Type decimal(38,17), the number can have 17 digits to the right.
      7. Nullable (optional): Check the box if the Term can be nullable.
      8. Business Key (optional): Check the box if the Term is the Business Key of the Model Object (or a part of the Business Key in case of composed Business Key).
      9. Identity (optional): Check the box if the Term is an Identity. 
      10. Hide for mapping source (optional): Check the box if you want to hide the Term in Term Mappings when the Model Object is used as the Source.
        1. Mostly set to true by Generator Configuration.
          A use case is: the Foreign Key created in a Satellite, when a Relationship to the Hub is made, is checked Hide for mapping source. This Term will stay part of the Model Object in the application but will not be part of the result view and table in the generated artifacts. It is only helpful for calculating the correct HK.
      11. Hide for mapping target (optional): Check the box if you want to hide the Term in Term Mappings when the Model Object is used as the Target
      12. Expression: this is the Term Mapping, which can contain several Source Terms:
      13. Default Value (optional): value to apply as Mapping is the Term Mapping is NULL
      14. Aggregation Type (optional): The Aggregation Type list depends on the Semantic configuration of the Generator. In this example, you can choose the following Aggregation Types:

      Then click on the Save button:

      • The new Term and its term Mapping appears in the Terms list of the Target Model Object:
      • A notification confirms the correct insert:

      Demonstration video