Which data type cannot be used as an Attribute field in CLM?

Which data type cannot be used as an Attribute field in CLM?

• A. String
• B. Number
• C. Table
• D. Boolean

Answer: (C)

In CLM, attributes are meant to hold single, scalar values that you can easily search, filter, and apply in rules or automations. A data type that stores multiple rows and columns—the Table type—is a complex, multi-record structure. Since an attribute is designed to represent one value for a contract or entity, a Table doesn’t fit as an attribute field. That’s why the Table option isn’t allowed as an Attribute field. String, Number, and Boolean are all examples of simple, single-value types: you can store text, a numeric value, or true/false in an attribute and use them in logic, calculations, and validations. Those work as attribute fields because they align with the one-value-per-record purpose of attributes, whereas a Table would require handling multiple rows and would be managed as a separate related entity or a different kind of field, not as a straightforward attribute.

In CLM, attributes are meant to hold single, scalar values that you can easily search, filter, and apply in rules or automations. A data type that stores multiple rows and columns—the Table type—is a complex, multi-record structure. Since an attribute is designed to represent one value for a contract or entity, a Table doesn’t fit as an attribute field. That’s why the Table option isn’t allowed as an Attribute field.

String, Number, and Boolean are all examples of simple, single-value types: you can store text, a numeric value, or true/false in an attribute and use them in logic, calculations, and validations. Those work as attribute fields because they align with the one-value-per-record purpose of attributes, whereas a Table would require handling multiple rows and would be managed as a separate related entity or a different kind of field, not as a straightforward attribute.