Association

...

Syntax:

IsParent Name ToEntity Attributes [ DeleteBehaviour ] ( {
[ PropertyArray ] [ DbReferenceKeys ] [ UseDefinitions ]
}| ;)

IsParent

Association type

An association can either be a 'parent' relationship for detail entities or a 'reference' to another entity.

Syntax:

<"parent":"reference">

Name

Name of association

Syntax:

<Identifier>

Restrictions:

• The name must start with an uppercase letter and can only contain letters and numbers
• All attributes and associations must have unique names

ToEntity

Name of referenced entity

Syntax:

<Identifier>

Restrictions:

• The reference entity must be found in the current project

Attributes

Association attributes

Syntax:

(AssociationAttribute ( ,AssociationAttribute )* )

DeleteBehaviour

Optional delete behavior marker.

Standard behavior is 'restricted delete'. Any other option must be set explicitly.

Syntax:

#DeleteBehaviour

• CASCADE - Cascade delete relationship. This option can be used if a general cascade relation will be defined between several entities. This option is only valid for parent key columns and this is also checked in method Reference_SYS.Refresh_Active_List__. It is only possible to have one single cascade definition in one entity.
• CUSTOM - Specify checking methods. This option can be used if specific checking methods (chkPL) are meant to be used. A more specific method for cascade operations (doPL) can also be specified. It is important to state that these methods are developed within the 'current' entity and not in the referencing one. This problem is detailed described in previous sections about validation before removing objects. Note that the key attributes are sent to the procedure as one single string consisting of a list of key attributes separated by the text separator (^).
• CUSTOMLIST - Specify checking methods (variation). This option is similar to /CUSTOM with one difference. The key attributes are sent to the procedure in different parameters instead of one single field-separated list. Using this option, it is easier for the developer to define the custom PL/SQL-methods to be called when a LU-instance is removed.
• NOCHECK - Disable reference checks. This option will deactivate all implicit checks before removing the referenced object and no actual code within system service Reference_SYS will be executed through methods Delete___ or Check_Delete___.

associations {
   parent                               IsoCountry     IsoCountry( CountryCode)/CASCADE{   }
   reference                            ItemIdRef      MovieItem( MovieId)/NOCHECK{   }
   reference                            TypeElementRef MovieTypeElement( CountryCode, MovieId)/CUSTOM=(Check_Reference_Pfe__,){   }
   reference                            LibraryIdRef   MovieLibrary( MovieId)/CUSTOMLIST=(Check_Remove,Do_Remove){   }
}

DbReferenceKeys

Db Reference Keys

Syntax:

DbReferenceKey

UseDefinitions

Use Definitions

Syntax:

( UseDefinition )*

This page is generated from IFS Developer Studio at 2025-11-27 07:44.