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 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.