Use Table Designer to define the fields and layout of reusable table views. The application also calls this tool Table Builder. It helps administrators provide relevant columns for an object type or supported relationship context. A table definition controls presentation; it does not determine the full set of objects a widget loads.
Choose the table context
- Open Table Designer with an account permitted to manage table definitions.
- Review the table category and select the relevant object type. Use a universal definition only when it is appropriate and supported for the intended context.
- Load an existing definition to review it, or choose Create New Table to start a separate definition.
- Confirm the definition’s name, type, and category. For a relationship-based table, check the relationship context before adding its fields.
Select and arrange columns
Use the attribute area to choose the fields needed for the table. Arrange the columns in an order that supports the user’s task. Put identifying information where it is easy to scan, then add the values needed for comparison or follow-up work.
Review the available field properties, labels, and widths. Give longer text enough room and avoid adding fields that the intended users cannot interpret. Available attributes depend on the selected type and context.
Object values and relationship values have different meanings. A column describing a connection should use the appropriate relationship attribute. Check the selected relationship when a required connection value is missing from the available field list.
Preview and save
Use the view-mode control to inspect the current definition. Check the column order, headings, and available space, then return to editing if the arrangement needs adjustment.
Choose Save and wait for confirmation. Reopen the saved definition to verify the result, then select it in a compatible table-based view where applicable. Check the layout with representative objects, including longer names and values.
Distinguish layout from data and access
The table definition describes visible fields. A widget’s source or filter determines which objects it requests, and platform permissions govern access to those objects and allowed updates. Adding a column does not make its values editable or grant access.
An existing definition can be shared by several views. Consider those users before changing it. A separate definition is useful when a team needs a different presentation without changing the current shared layout.
Troubleshooting
If a column is unavailable, check the selected type, category, and relationship. If a column is empty in a consuming view, verify that the loaded objects have a value for that attribute.
If the saved table is not offered, check that its context matches the view and refresh the definition list. If Save fails, review the validation message and confirm your permission to manage the definition.
