# Source System Table & Field Documentation

**URL:** https://discourse.getdbt.com/t/source-system-table-field-documentation/10363
**Category:** Help
**Tags:** documentation
**Created:** [October 16, 2023, 9:21pm UTC](https://discourse.getdbt.com/t/source-system-table-field-documentation/10363 "2023-10-16T21:21:58Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![JamesLarsen42](https://avatars.discourse-cdn.com/v4/letter/j/74df32/32.png) [@JamesLarsen42](https://discourse.getdbt.com/u/JamesLarsen42)
#### Post date: [October 16, 2023, 9:21pm UTC](https://discourse.getdbt.com/t/source-system-table-field-documentation/10363/1 "2023-10-16T21:21:58Z")

</div>

I’m new to dbt, and am about to build a number of target models for my new company. One of the key pieces will be utilizing the documentation functionality. However, I want a place to document our source tables / fields. In particular, I only want to document each source field once, even if it is used by multiple target models. Is this a built in feature with dbt? If someone can point me in the right direction to do more research, I’d greatly appreciate it!

---

<div class="post-metadata">

### Author: ![a\_slack\_user](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.getdbt.com/a_slack_user/32/1629_2.png) [@a\_slack\_user](https://discourse.getdbt.com/u/a_slack_user)
#### Post date: [October 16, 2023, 10:04pm UTC](https://discourse.getdbt.com/t/source-system-table-field-documentation/10363/2 "2023-10-16T22:04:29Z")

</div>

Look into using doc blocks for reusable docs.

Note: `@Jack Nguyen` originally [posted this reply in Slack](https://getdbt.slack.com/archives/CBSQTAPLG/p1697493862554599?thread_ts=1697491340.939189&cid=CBSQTAPLG). It might not have transferred perfectly.

---

<div class="post-metadata">

### Author: ![a\_slack\_user](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.getdbt.com/a_slack_user/32/1629_2.png) [@a\_slack\_user](https://discourse.getdbt.com/u/a_slack_user)
#### Post date: [October 16, 2023, 10:29pm UTC](https://discourse.getdbt.com/t/source-system-table-field-documentation/10363/3 "2023-10-16T22:29:13Z")

</div>

Ditto on leveraging doc blocks. h/t \<@U05TBUYDPDW\>

You can also play with this upstream\_description parameter from codegen:

````auto
model_name='YOUR_MODEL_NAME',
upstream_descriptions='TRUE'
) }}```

<sub>Note: `@rho` originally [posted this reply in Slack](https://getdbt.slack.com/archives/CBSQTAPLG/p1697495345869249?thread_ts=1697491340.939189&cid=CBSQTAPLG). It might not have transferred perfectly.</sub>
````

---

<div class="post-metadata">

### Author: ![rho](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.getdbt.com/rho/32/3108_2.png) [@rho](https://discourse.getdbt.com/u/rho)
#### Post date: [October 16, 2023, 10:32pm UTC](https://discourse.getdbt.com/t/source-system-table-field-documentation/10363/4 "2023-10-16T22:32:48Z")

</div>

That didn’t seem to paste well. You can also play with this upstream\_description parameter from codegen:

```auto
{{ codegen.generate_model_yaml(
model_name='YOUR_MODEL_NAME',
upstream_descriptions='TRUE'
) }}

```
