Skip to main content
Version: Current

Using the Field Manager (Staff/Advanced)

Warning: Advanced Feature

The Field Manager is an advanced configuration tool primarily intended for use by Zudello implementation staff or trained partners. Incorrect configuration can significantly impact system behaviour and user experience. Proceed with caution and consult Zudello support if unsure.

The Field Manager provides a centralised way to manage how standard system fields are presented across different modules and submodules within Zudello. You can customize field labels and control their default visibility, complementing the more granular control offered by Document Type Forms.

Best practices

  • Use clear and consistent labels that users will understand.
  • Test any changes thoroughly across relevant modules and submodules.
  • Avoid hiding essential fields required for core functionality or integrations.
  • Document any significant customizations made via the Field Manager.
  • Prefer Form configuration for hiding fields on specific document types unless a global hide is required.

Accessing Field Manager

Accessing the Field Manager requires specific administrative permissions, typically reserved for Zudello staff or trained partners.

  1. Navigate to Settings via the company menu.
  2. Click Field Manager in the left sidebar (if available with your permissions).

Understanding the Interface

The Field Manager displays a list of core Zudello data models (e.g., Transaction, TransactionLine, Supplier, Item).

  1. Select Model: Click on a model name (e.g., Transaction) from the list on the left.
  2. Field List: The main area displays all standard fields associated with the selected model.
  3. Columns:
    • Field Name: The internal system name of the field (read-only).
    • Label: The default display label for the field across the system.
    • Visibility: The default visibility (Visible/Hidden) for the field.
    • Actions: Edit icon to customize the field's settings.

Customizing Field Labels

You can change the default label of a field or set specific labels for different contexts (modules/submodules).

  1. Select the Model containing the field you want to customize.
  2. Find the field in the list and click the Edit icon (pencil).
  3. Default Label: Modify the text in the Label field to change the default display name everywhere.
  4. Scoped Labels (Optional): To set a different label for a specific area:
    • Click Add Scope.
    • Select the Module (e.g., Purchasing).
    • Select the Submodule (e.g., Invoice).
    • Enter the desired Label for this specific scope.
    • Repeat "Add Scope" for other module/submodule combinations if needed.
  5. How Scoping Works: If a specific scope (Module + Submodule) is defined, its label will be used in that context. Otherwise, the default Label is used.
  6. Click Save.

Customizing Field Visibility

You can set a field to be hidden by default across the system or hidden only within specific modules/submodules.

  1. Select the Model containing the field.
  2. Find the field and click the Edit icon.
  3. Default Visibility: Use the Visibility dropdown to set the default state (Visible or Hidden).
  4. Scoped Visibility (Optional): To control visibility for a specific area:
    • Click Add Scope.
    • Select the Module.
    • Select the Submodule.
    • Use the Visibility dropdown for this scope (Visible or Hidden).
  5. Interaction with Forms:
    • If Field Manager sets visibility to Hidden (either default or scoped), the field will be hidden in that context, regardless of the Form configuration for a specific Document Type.
    • If Field Manager sets visibility to Visible, the Form configuration for a specific Document Type can still hide the field for that specific type.
  6. Click Save.

Important Considerations

  • Global Impact: Changes made in Field Manager affect all users within the team.
  • Testing: Thoroughly test changes in relevant areas (document viewers, list views, filters, exports) to ensure they behave as expected.
  • Workflow Impact: Hiding fields essential for data entry, integrations, or automations can break workflows. Be certain a field is not required before hiding it globally.
  • Consult Support: Due to the potential impact, it's highly recommended to consult with Zudello support before making significant changes in the Field Manager.

Need help?

Contact Zudello support for assistance or guidance when using the Field Manager.