What are the limitations and guidelines for child relational tables?

Use this article as a reference while you set up child relational tables.

Limitations

The following are not supported for child relational table data.

  • New or classic dynamic content rules
  • Asset library
  • Landing pages
  • Classic queries
  • Scoring
  • Transact orgs
  • You cannot use Child Relational Table or Relational Table query criteria if the query is a contact source for Mobile App Messages or SMS.
  • Program entry
  • Child Relational Tables (CRT) can be used in decisions within Programs. However, you cannot use CRT criteria for personalization in the email subject line or body content, including use of Dynamic Content rules in the email IF the email is also using the Send Time Optimization (STO) send type. You can use CRT in the email personalization if you are sending normally or at a specific time.
  • Child Relational Table (CRT) criteria cannot be used as part of the entrance query as a contact source for a Program, or any Mobile App Messages, SMS messages or messages using Send Time Optimization (STO).
  • Child Relational Tables (CRT) criteria can be used in decisions and in email content in Programs, except when using STO for email sends.
Note: A Child Relational Table cannot be used as part of programs contact source query for entry, but you can use a Relational Table.

Guidelines

Use the following guide lines to help you during your child relational table set-up process.
  • Use multiple Child Relational Table queries per email, as you can reuse the queries to employ the personalization fields more effectively.
  • Try to keep the parent to child Contact Matching limited to a maximum of 20.

    When you build a relational table or database query with a parent and child relationship, the data that is mapped from parent to child should be low. This ensures that the query doesn't take a large amount of time to complete.

    It is recommended that you regularly purge a table that frequently writes entries. This ensures that the parent or child table is more manageable.

  • Preview and Click to View can be intermittently slow.
  • Queries with child relational table capabilities are blocked from being set as the program contact source.