Skip to main content

Configure objects, attributes and segments

Define record attributes, relationships and reusable segments.

Written by Carl Martin

Object configuration determines which fields records have and how they relate. Segments define reusable groups that can inform guidance, assignment or other rules.

Before you start

You need workspace administration access. Integration-defined or built-in attributes can have editing restrictions.

Records navigation groups companies, people, products, purchasing, production and sales records.

Choose the object that holds the business record before applying search or filters.

Configure the data model

  1. Open Settings → Objects and select the relevant object.

  2. Review its Attributes before adding a new field. Reuse an existing attribute when it already represents the same fact.

  3. Choose the correct type: text, number, date, selection, link, list or a supported calculation. Define required or unique constraints carefully.

  4. For a relationship, confirm the target object and whether it links one or multiple records, or contains a parent-owned list.

  5. Open Segments to define a reusable group with the intended conditions. Preview representative matches before using it in automation.

Check the result

The attribute stores the intended kind of value and the relationship points to the correct records. The segment matches the group your rule is meant to cover.

Use calculations deliberately

Formulas, lookups and rollups derive values from other fields or relationships. Check the dependency and result type before relying on the output. Some planning inputs require a stored field or compatible calculation.

Changing a field used in an integration, chart or rule can affect more than the record editor.

Keep segments understandable

Name a segment by its business meaning and inspect its conditions. A segment for one site or supplier class should not accidentally include the entire workspace.

If something does not look right

What you see

What to check

An attribute cannot be changed

Inspect whether an integration or built-in definition controls it.

A segment matches too much

Check missing conditions, operators and relationship scope before publishing dependent rules.

Does renaming a field repair its mapping?

A label and an integration mapping serve different purposes. Review the source mapping and downstream references separately.

Continue your work

Open the relevant area in Cartograph to continue with your workspace data.

Related articles

Did this answer your question?