# extractDataBlock

This block is used for VC documents which are based on (or ‘conform to’) a schema which contains embedded schemas, extractDataBlock provides means to extract a data set which corresponds to any of these embedded schemas (at any depth level), and if required after processing to return the updated values back into the VC dataset to their original ‘place’.

### 1. Properties <a href="#id-1.-properties" id="id-1.-properties"></a>

| Property Name | Details                                                                                                                                                                 | Example                                                                                                                                                                                                    | Status |
| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------ |
| Action        | an action which is executed by the block                                                                                                                                | <p>o Get – find and extract the part of the document which corresponds to the specified schema</p><p>o Set – update the part of the document, which corresponds to the specified schema, with new data</p> |        |
| Schema        | the schema which is target of the action. It is used to identify the embedded part of the data object - i.e. the field in the document which corresponds to this schema | Contact Details (1.1)                                                                                                                                                                                      |        |

## 1.1 Extraction <a href="#id-1.1-extraction" id="id-1.1-extraction"></a>

<figure><img src="https://3006114282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXVOaWpJKxLZf1Tee9eCO%2Fuploads%2FjpysL8lfbwXR0uIGxXad%2Fimage.png?alt=media&#x26;token=ffa7c91c-e8d3-4d08-b095-f5786741aadd" alt=""><figcaption></figcaption></figure>

## 1.2 Update <a href="#id-1.2-update" id="id-1.2-update"></a>

<figure><img src="https://3006114282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXVOaWpJKxLZf1Tee9eCO%2Fuploads%2F3T1jAz0TFhxMNkSPEipR%2Fimage.png?alt=media&#x26;token=799653e4-70e4-48bf-9e4f-b7ea43abbe28" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.guardianservice.io/technical-information/users/standard-registry-users-schemas-and-policies/policies/available-policy-workflow-blocks/extractdatablock.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.