I should create a one to many relation between to tables: Flow Table and Track Thttps://community.appian.com/discussions/f/integrations/4210/i-should-create-a-one-to-many-relation-between-to-tables-flow-table-and-track-tI should create a one to many relation between to tables: Flow Table and Track Table. The first one, Flow, has a primary key which is made up of two columns cod_flow and cod_rec. There isn&#39;t any auto-increment id. I would like to set 2 foreign keys, cod_flowen-USTelligent Community 12RE: I should create a one to many relation between to tables: Flow Table and Track Thttps://community.appian.com/thread/15030?ContentTypeID=1Thu, 05 Feb 2015 20:21:55 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:451c6a23-2f3f-4751-9385-542671b1a876PhilBI should add that you then can&#39;t write to that view using the CDT. Ultimately, Jacob is correct, Appian doesn&#39;t support composite keys.<div style="clear:both;"></div>RE: I should create a one to many relation between to tables: Flow Table and Track Thttps://community.appian.com/thread/15029?ContentTypeID=1Thu, 05 Feb 2015 20:20:04 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:fb38d418-a02d-4e98-99f7-7d96718e54a4PhilBIt may not be possible if the owners of the database don&#39;t wish to do it, but you could have them build a view against the database that flattens the two tables against each other by doing the composite join for you and generates a unique ID against each row, and then map a cdt to that view. There are various options for generated keys but what is possible depends on the type of database used.<div style="clear:both;"></div>RE: I should create a one to many relation between to tables: Flow Table and Track Thttps://community.appian.com/thread/15020?ContentTypeID=1Thu, 05 Feb 2015 16:48:23 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:7f5d4336-1a42-4957-92c0-c8840d8d8967Jacob Cohen - Project Leader - Macedon TechnologiesUnfortunately, Appian does not support composite keys.<div style="clear:both;"></div>