# Question - Linking risks to compliance packages items

**URL:** https://discussions.eramba.org/t/question-linking-risks-to-compliance-packages-items/2157
**Category:** Forum - Software
**Tags:** question
**Created:** [May 24, 2022, 8:06pm UTC](https://discussions.eramba.org/t/question-linking-risks-to-compliance-packages-items/2157 "2022-05-24T20:06:35Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![kisero](https://discussions.eramba.org/user_avatar/discussions.eramba.org/kisero/32/2925_2.png) [@kisero](https://discussions.eramba.org/u/kisero)
#### Post date: [June 6, 2022, 9:58am UTC](https://discussions.eramba.org/t/question-linking-risks-to-compliance-packages-items/2157/8 "2022-06-06T09:58:14Z")

</div>

actually there is no way, on an item report, to see that relation.

1/ the table widget does not include foreign tables like compliance.

 ![image](https://discussions.eramba.org/uploads/default/original/2X/6/6df8b8bc0378fae096000936496cccedfac8b481.png)

we need to review the core sections, make sure the related core sections are listed there so you can pull a simple table with those relations

2/ the tree chart could include a branch “Compliance Items” and list the related items “Compliance Package Name - Compliance Package Item ID”

 ![image](https://discussions.eramba.org/uploads/default/original/2X/f/f0cab4b03c58d0a050111f13296a219d6e454915.png)

I think #2 would be simpler to implement, but we’ll see.

giuthub: [https://github.com/eramba/eramba\_v2/issues/3521](https://github.com/eramba/eramba_v2/issues/3521)

---

_[View the full topic](https://discussions.eramba.org/t/question-linking-risks-to-compliance-packages-items/2157)._
