zoukankan      html  css  js  c++  java
  • Understanding the RelationshipType Enumeration [AX 2012]

    Understanding the RelationshipType Enumeration [AX 2012]

    3 out of 3 rated this helpful - Rate this topic

    Updated: January 28, 2012

    Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

    When you add a node under AOT > Data Dictionary > Tables > YourTable > Relations, you can set the value of the RelationshipType property of the new relation. The list of possible values for the RelationshipType property is the list of elements in the RelationshipType enum. The meaning of each element in the RelationshipType enum is described in this topic.

    Description of Elements

    The following table describes the elements of the RelationshipType property.

    Element name

    Description

    Automatic inference

    NotSpecified

    Often the default value for the RelationshipType 

    property.

    When the RelationshipType property has the value NotSpecified, the system infers an appropriate value. The system infers the value in the following sequence:

    1. Specialization
    2. Link
    3. Composition
    4. Aggregation
    5. Association

    For example, if the criteria for both Composition and Aggregation are met, the system infers Composition. This is true because Composition occurs earlier in the list.

    Specialization

    Applies only to table inheritance, to relationships between base and derived tables.

    The system sets the RelationshipType property to Specialization whenever table inheritance is involved.

    Link

    Is a non-relational relationship. Link 

    requires that the Validate property be set to No.

    This type of relationship supports navigation between forms that list many records from a table and forms that provide detail fields for one record from the table.

    Link is meant only to support the migration of extended data type (EDT) link relations for upgrade to Microsoft Dynamics AX 2012 from earlier versions of the product. Migration tools create this type relationship, but you must not.

    Composition

    Is a stronger type of Aggregation. A table must not have more than oneComposition relation. For example, a building is composed of rooms, and a given room cannot exist in more than one building.

    If the criteria for Composition are met, but you manually assign the value ofAggregation or Association, the system leaves the value as Aggregation orAssociation.

    Aggregation

    Is appropriate when the child table is considered to be subordinate to the entity of the parent table.

    The system infers Aggregation when either of the following is true:

    • The parent table has a delete action node that is defined to use this relation node.
    • Any of the foreign key fields for this relation in the child table have theirMandatory property set to Yes.

    If the criteria for Aggregation are met, but you manually assign the value ofAssociation, the system leaves the value as Association.

    Association

    The concept of a standard foreign key.

    You must set the RelationshipType property to Association if the system does not set the value of property to anything, and both Aggregation and Composition are inappropriate.

    See also

    Table Relation Properties

  • 相关阅读:
    计算机视觉的常用测试数据集和源码
    Demo:基于 Flink SQL 构建流式应用
    102万行代码,1270 个问题,Flink 新版发布了什么?
    bilibili 实时平台的架构与实践
    阿里云2020上云采购季来啦!降本增效1亿补贴!
    阿里云助力宁波市教育局“甬上云校”停课不停学
    Quick BI新版本功能解读系列之-V3.5
    百万TPS高吞吐、秒级低延迟,阿里​搜索离线平台如何实现?
    五分钟学会使用 go modules(含在家办公使用技巧)
    OAM 深入解读:OAM 为云原生应用带来哪些价值?
  • 原文地址:https://www.cnblogs.com/msdynax/p/3768329.html
Copyright © 2011-2022 走看看