Subject Browser - Enquiry

Enquiry mode is the read-only mode of Subject Browser.

Use it when you want to browse the namespace, inspect a Subject, and open related enquiries without changing the structure.

What Enquiry mode is for

Enquiry mode is designed for:

finding customers, suppliers, staff, and departments
checking where a Subject sits in the namespace
opening related enquiries
using Subject Browser as a safe navigation and lookup tool

Available enquiry actions

When a suitable Subject is selected, Enquiry mode provides:

Invoices
Payments
Statement

Structural Subjects do not expose these enquiry actions.

How it works

Select a Subject in the tree and then choose the enquiry you want.

On desktop:

the enquiry opens in the details area

On mobile:

the enquiry opens in the mobile details flow

This lets you move from the namespace directly into the related enquiry without leaving Subject Browser.

Subject Browser desktop view in Enquiry mode showing enquiry actions

Why namespace matters in Enquiry mode

Even in read-only use, namespace helps you understand context.

For example, the same Subject may appear in different structures because Trade Control uses relationships rather than a fixed contact tree.

That means namespace can help answer questions such as:

which branch of the business am I looking at
which department or team does this person belong to here
which path was used to reach this organisation

DAG-enabled enquiries

Subject Browser enquiries are namespace-aware.

That means the selected path is not just a label. It controls which related records are shown.

Subject Browser desktop view in Enquiry mode showing DAG enquiry

Direct Subject selection

If you select a leaf Subject such as a trading arm, the enquiry shows the activity for that selected Subject in the selected namespace.

Ancestor selection

If you select a parent namespace node such as a division, department, or holding structure, the enquiry can show the combined activity contained under that selected branch.

For example, if a holding structure contains more than one trading arm, selecting the holding structure can show the contained statement activity for the full branch.

This is especially useful when you want to understand activity at:

division level
department level
group level
holding-company level

Using Enquiry mode effectively

A common pattern is:

filter the namespace
select the required Subject or namespace node
confirm the namespace path and Subject details
open the related enquiry

This is especially useful when the same organisation or person can appear in more than one namespace.

Different path, different result

In a DAG model, the same Subject may appear in more than one namespace. This is expected.

Because enquiries are namespace-aware, the results may differ depending on the selected path.

For example:

one path may show only EU activity
another path may show only UK activity
a higher-level path may show the contained activity for both

This is normal and reflects the selected namespace context.

Common outcomes

No enquiry actions shown

This usually means one of the following:

no Subject is selected
the selected Subject is structural
the selected Subject does not support the enquiry action in the current context

Empty enquiry result

This may mean:

there is no activity in the selected namespace context
the selected path is more specific than the activity you expected
the selected Subject or namespace node does not contain records for that enquiry type

Different path, same Subject

You may reach the same Subject through more than one namespace. This is expected in the DAG model.

If the enquiry results are different, check the selected namespace path first.