How do you reference a field inside a Custom Data Type (CDT) from a rule or interface, such as accessing dealershipName on a vehicle CDT?

How do you reference a field inside a Custom Data Type (CDT) from a rule or interface, such as accessing dealershipName on a vehicle CDT?

• A. You access it via dot notation on the CDT variable, e.g., pv!vehicle.dealershipName.
• B. You must flatten the CDT into a local variable before using it in rules.
• C. CDT fields cannot be accessed directly in rules.
• D. You must convert the CDT to a text string to access its fields.

Answer: (A)

Accessing fields of a CDT is done directly with dot notation on the CDT variable. When you have a CDT instance like vehicle, you read its fields by appending the field name after a dot, for example pv!vehicle.dealershipName. This works whether the CDT comes from a rule input, a process variable, or a local variable, and it works for nested fields by chaining dots (pv!vehicle.dealershipName, or pv!vehicle.dealership.name if the subfield is itself a CDT). There’s no need to flatten the CDT or convert it to text to access its fields. Direct dot notation is the standard, straightforward way to reference CDT fields.

Accessing fields of a CDT is done directly with dot notation on the CDT variable. When you have a CDT instance like vehicle, you read its fields by appending the field name after a dot, for example pv!vehicle.dealershipName. This works whether the CDT comes from a rule input, a process variable, or a local variable, and it works for nested fields by chaining dots (pv!vehicle.dealershipName, or pv!vehicle.dealership.name if the subfield is itself a CDT).

There’s no need to flatten the CDT or convert it to text to access its fields. Direct dot notation is the standard, straightforward way to reference CDT fields.