nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Custom field's value required (or by default)

Tania Pinard

Allo !

We are trying to find a way to make a custom field's value required or have a default value for it. This is a constituent custom field that is not required for all constituent. We are looking for a way to obligate the users to fill in the value if they want to use that specific custom field. Our goal is to have no empty values. Is that possible?

432576e1275fb9f5b9a68c034a0dfc32-huge-im

Merci,
Tania

Find more posts tagged with

Comments

Lee Grisham

@Tania Pinard Since business rules do not apply to NXT, I do not see this as possible. I would think you could run a monthly global change to the field to fill in blanks, but that is definitely not the most efficient way to do things.

Austen Brown

@Tania Pinard - Agree with @Lee Grisham's suggestion for this. Chiming in to add, that you could use Power Automate and it's certified connections to RE NXT to do the review work for you; there is a potential that you could build an automated flow to audit this section of your data and apply your designated ‘default’ field if the value = blank, automatically. Check out this blog I wrote for more information on this option: