<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Process model and script task</title><link>https://community.appian.com/discussions/f/data/14008/process-model-and-script-task</link><description>Hi, I have a process model with 2 save to data store entity. In the process, I save to my first CDT, and that works fine. As the process moves on to save in the second CDT, it also works, however, it does not auto-generate an ID. In the database I see</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Process model and script task</title><link>https://community.appian.com/thread/63680?ContentTypeID=1</link><pubDate>Thu, 27 Dec 2018 19:28:28 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:d1269785-0471-4494-b83d-1949d761b399</guid><dc:creator>legotx</dc:creator><description>By default, Appian assigns a_id as the primary key if there are no primary key in the CDT.  You need to assign the ID as a primary key. And in your database scheme you can add an &amp;#39;auto increment&amp;#39; property for the ID.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Process model and script task</title><link>https://community.appian.com/thread/63531?ContentTypeID=1</link><pubDate>Wed, 19 Dec 2018 05:57:52 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:6021ec95-c5f9-46bb-ae86-b72e305a2e6c</guid><dc:creator>ravalik</dc:creator><description>Hi erics,&lt;br /&gt;
&lt;br /&gt;
As all practitioners said it is completely appian default behaviour. You need to make one of the columns in CDT as a primary key in order to avoid a-id.&lt;br /&gt;
&lt;br /&gt;
Thanks,&lt;br /&gt;
ravalik&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Process model and script task</title><link>https://community.appian.com/thread/63529?ContentTypeID=1</link><pubDate>Wed, 19 Dec 2018 04:07:09 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:3999f95a-0448-4844-aef7-d1a29d1b13f2</guid><dc:creator>nidhim855</dc:creator><description>Hi Eric,&lt;br /&gt;
&lt;br /&gt;
To get the auto generated id in the process, you need to save the result. For that go to Data, output tab  and save the store values to your same CDT.  Thanks&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Process model and script task</title><link>https://community.appian.com/thread/63528?ContentTypeID=1</link><pubDate>Wed, 19 Dec 2018 03:56:19 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:aa8ba7d0-47d4-400d-9939-ff31c3ee5b4d</guid><dc:creator>Hema</dc:creator><description>Hi Eric,&lt;br /&gt;
&lt;br /&gt;
The default behavior of Appian is that if there is no primary key defined in a CDT, while publishing the data store and creating a table, an extra column with the name a_id would be created in the DB. In order to avoid this, please make a column as primary key.&lt;br /&gt;
Also to auto-generate, use @GeneratedValue annotation in the xsd of CDT.&lt;br /&gt;
&lt;br /&gt;
Thanks,&lt;br /&gt;
Hema&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Process model and script task</title><link>https://community.appian.com/thread/63524?ContentTypeID=1</link><pubDate>Wed, 19 Dec 2018 03:15:39 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:039e6c36-1c63-4002-849b-91a35446c721</guid><dc:creator>bhanuprakash1303</dc:creator><description>Hi Eric171,&lt;br /&gt;
&lt;br /&gt;
This is default behavior of appian. if your cdt does not have auto-generated ID automatically a-id is generated in database side. it starts with 1,2,3....so on. it means it is not seqenece value.&lt;br /&gt;
&lt;br /&gt;
Hope it is understand.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Regards,&lt;br /&gt;
Bhanu&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Process model and script task</title><link>https://community.appian.com/thread/63518?ContentTypeID=1</link><pubDate>Tue, 18 Dec 2018 18:17:35 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:d0790ccb-9428-4097-a080-f16d14e54b6c</guid><dc:creator>ankushj</dc:creator><description>&lt;p&gt;Hi Eric,&lt;br /&gt; &lt;br /&gt; As Jacob mentioned, stored value back to CDT could be one of the reason. But A_id in database generally indicates that there is no @GeneratedValue defined in CDT. Please download and check you have generatedValue in the XSD&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Process model and script task</title><link>https://community.appian.com/thread/63514?ContentTypeID=1</link><pubDate>Tue, 18 Dec 2018 16:18:06 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:2eab80be-2880-4656-803e-2b49823ffd24</guid><dc:creator>Jacob Grafenstein</dc:creator><description>Hi Eric,&lt;br /&gt;
In your second Write to Datastore node, navigate to the Outputs tab. Are you saving the value of &amp;quot;Stored Values&amp;quot; back into your CDT?&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>