Add a custom field

When you need to track something DealJourney has no field for (a project number, a region, a contract type of your own), add a custom field.

1. 1Open Admin from the sidebar.
2. 2Go to ⟦Feltopsætning⟧ under Organisation.
3. 3Choose the record type the field belongs to: customers, contacts, leads, opportunities, or subscriptions.
4. 4Add the field, give it a label people will understand, and choose the right type.
5. 5Save.Pick the type carefully: it is the decision that matters most. A date

stored as text cannot be filtered as "before last month". A number stored as text sorts 10 before 9. A fixed set of options stored as free text ends up with four spellings of the same word and no reliable filter. Use a date for dates, a number or currency for amounts, a yes/no for flags, and a dropdown whenever the answer comes from a known list.

The order in the list is the order people read the fields in. Sort the list by Rækkefølge and drag a row by the handle on its left to move it. The new order saves as soon as you drop the row, and it applies everywhere that record type is shown. Dragging is only offered while the list is in that order and no search is active, because dropping a row into a name-sorted or filtered list would put it somewhere you did not point at.

Once created, the field shows on that record type for everyone, and it becomes available as a filter condition and as a column on the list page. That is the real payoff: a custom field is what lets you later ask for every opportunity on one project, or every customer in one region.

Keeping two dropdowns in step. Feltafhængigheder lets one choice field decide what another one may offer: Forbind to dropdown-felter, så de følges ad. Enten begrænser du, hvad det ene tilbyder ud fra det andet, eller også udfyldes det ene automatisk ud fra det andet. Pick the allowed options for each value of the controlling field, and the rest disappear from the picker on the record. Once a value has been decided, the panel shows only the options it allows — Ret ({{count}} mere) brings the rest back when you want to change the set. A rule over twenty options and five brands is otherwise a hundred checkboxes with the answer buried inside it.

Taking a field away: hide it, or delete it. These are not the same thing and only one of them is reversible.

• Hide is the Synlig switch on the field's row. It flips to Skjult, the field disappears from forms and record pages, and everything already stored stays exactly where it is. Switch it back on and the values are all still there. This is what you want almost every time, and it is the only option on the fields DealJourney ships (those can be hidden but never deleted). Obligatoriske felter kan ikke skjules, so clear the required setting first if you need to hide one.
• Delete removes the field you created, for good. The field, its label overrides and any dropdown-dependency rule that mentions it all go. What it does NOT do is clear the values already saved on your records: they stay in the database with nothing left to display them, and creating a new field with the same name later will not bring them back into view.

Before you confirm a delete, the dialog tells you how many records still hold a value for that field. If it cannot work that out it says so rather than guessing, and you should treat that as "there is probably data here".

Adding a new kind of thing (cars, contracts, properties) is not a custom field. That is a custom entity, which gets its own page and its own records, under Egne objekter.