Custom Fields

A custom field is a field you add to a MonetizeNow object to hold information that's specific to your business, such as a customer segment or a case-study opt-in. MonetizeNow's built-in logic doesn't use custom fields, but you can: in rules, CRM field mapping, bulk uploads and the API.

Manage them in Settings → Custom Fields.

Common use cases

Drive quote rules from a custom field

Example: You want to add legal language to a quote when a customer agrees to take part in a case study, and you want the Head of Marketing to approve the quote when they don't.

1. Create a Checkbox custom field on Quote called Case study opt in.
2. Create a Conditional Term that inserts the legal language when Case study opt in is true.
3. Create an Approval Rule that requires Head of Marketing approval when Case study opt in is false.

Drive quote rules from CRM data

Example: You want different quote approvers for each customer segment (for example, Enterprise or Mid-Market), and the segment is a field on the Salesforce opportunity.

1. Create a custom field on Quote called Segment, as a Dropdown or Single Line Text.
2. In Salesforce Field Mapping, map the opportunity's segment field to the Segment custom field on the MonetizeNow quote. MonetizeNow custom fields appear in the mapping list with a customField. prefix.
3. Create one or more Approval Rules on Segment, with a different approver for each segment.

Rules can use custom fields from Quotes, Accounts and Bill Groups as conditions.

Create a custom field

1. Go to Settings → Custom Fields and click New.
2. Fill in the form (see Field settings below).
3. Click Save.

Custom fields can't be deleted. Once a field is saved it stays. Double-check the Object, API Name and Type before saving, because those three can't be changed afterwards either.

Objects that support custom fields

Usage Event custom fields support Single Line Text only, with a maximum of 50 per tenant.

Field types

Field settings

Dropdown values

Each option has a Label (what users see), a Value (what's stored) and an Enabled checkbox. The Value fills in from the Label. Drag the handles to change the order.

• A field can have up to 50 options, and each Value must be unique.
• After saving, you can add options and edit their labels, but you can't remove an option or change its Value.
• To retire an option, clear Enabled. A disabled option is no longer offered for selection, and records that already use it keep their value.

Field visibility

For each custom field, choose whether all roles share the same access (All Roles) or each role gets its own (Specific Roles). For each role, the field can be:

• Editable: users with this role can view and edit the field.
• Read Only: users with this role can view but not edit the field.
• Hidden: users with this role can't see the field.

With Specific Roles, use Set all roles to to change every role at once. At least one role must be able to see the field. The Custom Fields list shows Varies by role when roles differ.

📘

Users with more than one role get the most permissive access. For example, a user with one role set to Editable and another set to Read Only can edit the field.

Visibility controls how the field appears in the MonetizeNow app. It doesn't restrict access through the API.

Limits

Where else custom fields appear

• Record pages: on the object's page, according to each user's visibility.
• Rules: rules can reference custom fields on Quotes, Accounts and Bill Groups.
• CRM field mapping: Salesforce and HubSpot field mapping list MonetizeNow custom fields with a customField. prefix.
• Bulk upload: the Products, Offerings and Quotes templates under Settings → Onboarding include a column for each custom field on that object, headed by its API Name.
• API: custom field values are read and written by API Name.