Custom Menu Options
A Custom Menu Option is a named container you create to group your own Custom Records, Custom Reports and Custom Pages under a single entry in AdmCloud's navigation, instead of leaving each of them scattered on its own.
What it is and what it's for
A Custom Menu Option only has a Name, an Owner and a Protected flag — it doesn't hold any content by itself. Its purpose is to act as the folder or heading that other customization objects point to: when you create a Custom Record, a Custom Report or a Custom Page, you can pick one of your Custom Menu Options so that item shows up filed under that name in the app's menu instead of loose at the top level.
It's useful once you have several custom objects of the same kind (for example, three Custom Records used by the warehouse team) and want them to appear together, under one label, instead of as separate unrelated entries.
Screens in this area
| Screen | What it does |
|---|---|
| List | Lists every Custom Menu Option in your company by name. From here you create a new one or open an existing one's detail. |
| Create / Edit | The form with the option's Name, Owner and Protected flag. |
| Details | The already saved option in read-only mode, with its change log. |
How to use it, step by step
- Open the Custom Menu Options list and click New.
- Enter the Name that will show up in the navigation, for example "Warehouse Tools" or "Human Resources Extras".
- Set the Owner, and whether it should be Protected (so only the owner can edit or delete its structure).
- Save.
- Assign it from the object you want to group. Open a Custom Record, a Custom Report or a Custom Page and pick this Custom Menu Option on its Menu field, so that object files itself under this entry in the navigation.
Where a Custom Menu Option is used
Once created, a Custom Menu Option can be linked from:
- A Custom Record (a user-defined data entity).
- A Custom Report.
- A Custom Page.
Because of that, a Custom Menu Option can't be deleted while any Custom Record, Custom Report or Custom Page still points to it — see Validations on save below.
Key fields
| Field | What it's for |
|---|---|
| Name | The label shown in the navigation. It's required and must be unique across all your Custom Menu Options. |
| Owner | The user responsible for this menu option; must be an active user. They're the one who can edit or delete it when it's flagged as Protected. |
| Protected | When checked, only the owner can modify or delete this menu option's structure. |
Validations on save
- Name required and unique: it can't repeat the name of another Custom Menu Option in your company.
- The Owner must be an active user in the system.
- A Protected menu option can only be edited or deleted by its owner; other users get a message saying they don't have permission.
- You can't delete a Custom Menu Option that's in use. The system blocks the deletion and lists the names of the Custom Records, Custom Reports and/or Custom Pages that are still filed under it.
Availability and permissions
- Access is controlled by the "Customization" permission on the user group, with separate levels for view, add and edit.
Tips and common mistakes
Create the Custom Menu Option before the objects you want to group. That way it's already available on the Menu field when you create your Custom Records, Custom Reports or Custom Pages, instead of having to go back and edit each one afterward.
If you can't delete a menu option, check what's still filed under it first. The error message lists the Custom Records, Custom Reports or Custom Pages using it; unlink or reassign them before trying to delete it again.
A Custom Menu Option has no content of its own. If you're looking to build a catalog of options for a Custom Field's dropdown, use a Custom List instead — a Custom Menu Option only organizes how other customization objects appear in the navigation.