> For the complete documentation index, see [llms.txt](https://docs.dynalogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/statistics-column-set-relation-6182310.md).

# Statistics Column Set Relation

Here you connect the *Column set* to the relevant page/Report.

| Ref. objecttype | Ref. object-id | Ref. objectname                    |
| --------------- | -------------- | ---------------------------------- |
| Page            | 6182765        | Registration Approvalr             |
| Page            | 6182311        | JobManager Employeecard            |
| Report          | 6182809        | Specification for time and Payment |
| Report          | 6182810        | Statistics Column Report           |

If you need different *Columns Set* for each User, then the *User ID* can be limited to different users.

| Topic                         |
| ----------------------------- |
| [Sequence](#field-1)          |
| [User ID](#field-5)           |
| [Ref. Object Type](#field-11) |
| [Ref. Object ID](#field-12)   |
| [Ref. Object Name](#field-13) |
| [Column Set ID](#field-21)    |
| [Description](#field-25)      |

## See also

[Registration approval](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/general/registration-approval-6182765.md)

## Reference

[Column Function](https://documentation.jmgapp.dk/en-us/T_6182307.htm)\
[Statistics Column](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/statistics-column-6182308.md)\
[Statistics Column Set](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/statistics-column-set-6182309.md)

\
\\

<details>

<summary>Sequence</summary>

Unique number which identify this line.

</details>

<details>

<summary>User ID</summary>

If each calculater/approver need a different *Statistics Column Set*, this field can be filled out with a NAV/BC user.

</details>

<details>

<summary>Ref. Object Type</summary>

Can be *Page* og *Report*

</details>

<details>

<summary>Ref. Object ID</summary>

Fill in with the relevant *Ref. Objekt ID*.

Options:

| REF. Objecttype | REF. Object-ID | REF. Objectname                   |
| --------------- | :------------: | --------------------------------- |
| Report          |     6182809    | Specification of Time and Payment |
| Report          |     6182810    | Statistics Column Report          |
| Page            |     6182311    | JobManager Employee Card          |
| Page            |     6182765    | Registration Approval             |

</details>

<details>

<summary>Ref. Object Name</summary>

Is automatically filled out, when the *Ref. Object ID* is filled out.

</details>

<details>

<summary>Column Set ID</summary>

Filled in automatically.

</details>

<details>

<summary>Description</summary>

Filled in automatically.

</details>

{% hint style="warning" %}
Some links in the original help refer to unavailable topics. See [Legacy Source Gaps](https://docs.dynalogic.com/birds-jobmanager-product-overview/training-and-support/source-gaps.md) for details.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/statistics-column-set-relation-6182310.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
