---
title: "Data pre-filling - Inheritance between cards"
slug: "data-pre-filling-inheritance-between-cards"
updated: 2022-10-11T17:09:16Z
published: 2022-10-11T17:09:16Z
canonical: "help.cooperlink.io/data-pre-filling-inheritance-between-cards"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.cooperlink.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Data pre-filling - Inheritance between cards

This article applies to DELIVER EMPOWER licenses

## Purpose and scope

To avoid input errors and re-encodings, Cooperlink makes it possible to reuse the data already encoded. This article explains the inheritance mechanism between cards.

## Inheritance

![](https://cdn.document360.io/c21b52e3-341e-4ea9-8692-3488bd21cd8d/Images/Documentation/image-1630452999507.png)Each item in Cooperlink can have a metadata card to enrich its information structure.

In order to avoid unnecessary re-encodings, this information can be inherited by the workflow. This inheritance allows, among other things, to set default values.

Inheritance depends on the configuration settings of the workflow and requires the use of identical keys.

## Example

Imagine a project card that contains a *document_type* key metadata with a value of PLAN. When I start a new workflow, I will create a new workflow card that also contains *the same field document_type**.* The workflow therefore inherits the value PLAN. It is no longer necessary to re-encode it.