# Fix combinations between tables

**URL:** <https://forum.datacebo.com/t/fix-combinations-between-tables/399>\
**Category:** Synthetic Data Creation\
**Tags:** feature-request\
**Created:** [January 26, 2026, 8:58pm UTC](https://forum.datacebo.com/t/fix-combinations-between-tables/399 "2026-01-26T20:58:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![neha](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.datacebo.com/neha/32/15_2.png) [@neha](https://forum.datacebo.com/u/neha)\
**Post date:** [January 26, 2026, 8:58pm UTC](https://forum.datacebo.com/t/fix-combinations-between-tables/399/1 "2026-01-26T20:58:34Z")

</div>

_I’m filing this feature request based on [this older thread](https://forum.datacebo.com/t/resolved-cross-table-constraints/220) about adding multi-table constraints. Although we’ve added multi-table constraints, we haven’t yet added logic for the particular pattern that is being described._

**Which software are you using?** : SDV Enterprise (CAG bundle)

### Description

> if I had a diagnosis table and a procedures table, could I have a constraint in the diagnosis table that applies to the procedure table (such as given a diagnosis in the diagnosis table, only generate specific procedures in the procedure table)?

This seems similar to the [FixedCombinations constraint](https://docs.sdv.dev/sdv/concepts/constraint-augmented-generation-cag/predefined-constraints/fixedcombinations), except it applies across tables.

### We prioritize based on demand!

If you’d like to support this feature, please reply below with any details about your specific case and/or react to this post. Thanks!