Insert record values into content

Use placeholders to show a record’s values in dynamic content. For example, a greeting can use a candidate’s first name and fall back to a neutral greeting when no value is available. Caraer’s placeholder engine is called SmartenContent.

Before you begin

Identify the record context, property names, and any relation the content can read. Use a sandbox page and test both populated and missing values. CMS v2 module fields have their own resolved input contract; see CMS modules.

Insert one property

Hello {{property=firstname&defaultValue=there}}

With firstname set to Alex, the rendered text is Hello Alex. Test the fallback with a record that has no first name; it should remain readable.

Read a related record

{{property=firstname&object=user&relation=owner&defaultValue=Your contact}}

The object and relation select a related-record context; property selects the value to insert. Use schema names rather than display labels. The available value still depends on the caller’s context and permissions.

Combine related values

relationType=primary selects the primary related record. relationType=all collects values; the supported seperator parameter controls joining (its API spelling is intentional). Set a fallback and test empty and multiple matches.

Handle missing values deliberately

Use defaultValue for readable public content. Advanced failLevel handling can remove fields or content blocks when resolution fails, so test the final rendered page as well as the raw content. Use internal=true only when you need the underlying stored value instead of a display value.

Common mistakes

Guessing relation names, omitting a fallback, or testing only a populated record can leave public text blank or remove a block. Verify the actual page with missing and multiple related values. For ordinary API data retrieval, use record queries rather than content placeholders.