> For the complete documentation index, see [llms.txt](https://www.mica.wtf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.mica.wtf/eu-level/q-and-a/eba-qa-2024-7285-template-specific-instructions-primary-keys.md).

# Template specific instructions – primary keys

|                 |                                                                                                                                                          |
| --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Authority**   | EBA                                                                                                                                                      |
| **Q\&A ID**     | EBA\_QA\_2024\_7285                                                                                                                                      |
| **Topic**       | Register of information (DORA)                                                                                                                           |
| **Legal basis** | [Article 28(9)](https://www.mica.wtf/dora/digital-operational-resilience-act/chapter-v-managing-ict-third-party-risk/article-28-general-principles) DORA |
| **Status**      | Final Q\&A                                                                                                                                               |
| **Published**   | 28/03/2025                                                                                                                                               |
| **Submitted**   | 13/12/2024                                                                                                                                               |
| **Source**      | [EBA Q\&A](https://www.eba.europa.eu/single-rule-book-qa/qna/view/publicId/2024_7285)                                                                    |

## Question

How to report data fields in case of missing values?

## Background

Some fields are marked as primary keys, and therefore they cannot be missing. However, in some cases the specific field might not be relevant for the entity (e.g., template B\_03.02.0010)

## Final answer

If financial entities are not able to fill some data fields that are mandatory, they can leave these data fields blank (report empty values), unless the instructions to the data fields or responses to Q\&A. provide otherwise (please refer to responses to Q\&A 140, 141, 142, 143, 144, 145, 146, 147, 148). These will be highlighted as data quality issues in the data quality feedback.

However, financial entities cannot report empty values for the data fields identified as keys in the data model ( Data Model for DORA Register of Information ). If the financial entity cannot provide a value for a specific field that is identified as a primary key in the data model, financial entity should report ‘Not Applicable’ in that field.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.mica.wtf/eu-level/q-and-a/eba-qa-2024-7285-template-specific-instructions-primary-keys.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.