# Multi-table models should support sequential data

**URL:** <https://forum.datacebo.com/t/multi-table-models-should-support-sequential-data/204>\
**Category:** Synthetic Data Creation\
**Tags:** multi-table, sequential, feature-request\
**Created:** [June 6, 2024, 6:22pm UTC](https://forum.datacebo.com/t/multi-table-models-should-support-sequential-data/204 "2024-06-06T18:22:45Z")\
**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:** [June 6, 2024, 6:22pm UTC](https://forum.datacebo.com/t/multi-table-models-should-support-sequential-data/204/1 "2024-06-06T18:22:45Z")

</div>

# Problem Description

Currently all multi-table synthesizers assume that each table contains single-table (non-sequential) data. However, in some cases you may have one or more table that correspond to sequences. As an example, see [**this issue**](https://forum.datacebo.com/t/duplicated-values-within-a-group/198) raised by @yuntien.lee.

We will keep this feature request open and use to collect more information about this use case, and communicate any updates in prioritization, etc.

# Workarounds

In the meantime, do note that there may be workarounds you can use to emulate the sequences in a multi-table context. This may require some additional post-processing to delete duplicate rows, reorder, etc. For anyone running into this issue, our team can help provide workarounds that will unblock your use case.