<?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>Hi, I use the smart node &amp;quot;Query database&amp;quot;. Someone has try t</title><link>https://community.appian.com/discussions/f/process/6179/hi-i-use-the-smart-node-query-database-someone-has-try-t</link><description>Hi, I use the smart node &amp;quot;Query database&amp;quot;. Someone has try to use a &amp;quot;data inupt&amp;quot; to specify a field&amp;#39;s name on my SQL query? I have some identical requests on differents fields, and for now i use several &amp;quot;query database&amp;quot; nodes. Thanks in advance. OriginalPostID</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Hi,&lt;br /&gt;I use the smart node "Query database".&lt;br /&gt;Someone has try t</title><link>https://community.appian.com/thread/27286?ContentTypeID=1</link><pubDate>Wed, 03 Feb 2016 21:57:52 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:8392476f-3f6a-48ca-aae0-893a9ccd1525</guid><dc:creator>abhinavg</dc:creator><description>@victorb  what design / solution approach you followed to implement the above usecase. If you can share your thoughts ...&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Hi,&lt;br /&gt;I use the smart node "Query database".&lt;br /&gt;Someone has try t</title><link>https://community.appian.com/thread/24089?ContentTypeID=1</link><pubDate>Wed, 28 Oct 2015 17:34:34 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:4ecc4874-5375-444b-931b-6b1a77779b18</guid><dc:creator>Victor Bouchery</dc:creator><description>Hi Fabien, yes i could do that but with this solution a part of the business rules isn&amp;#39;t stored in Appian. Thanks anyway&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Hi,&lt;br /&gt;I use the smart node "Query database".&lt;br /&gt;Someone has try t</title><link>https://community.appian.com/thread/24058?ContentTypeID=1</link><pubDate>Wed, 28 Oct 2015 00:32:16 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:b0a1a8d8-8fcd-4d0d-843f-fc364b716013</guid><dc:creator>fabienb</dc:creator><description>Hi Victor, you could also use a stored proceudure to achieve this.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Hi,&lt;br /&gt;I use the smart node "Query database".&lt;br /&gt;Someone has try t</title><link>https://community.appian.com/thread/24054?ContentTypeID=1</link><pubDate>Tue, 27 Oct 2015 21:11:38 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:b7ae4531-104a-47de-b5b3-a2f285e61616</guid><dc:creator>anshuk170</dc:creator><description>If you want to fetch datas from multiple tables you can create view and fetch the same using a!QueryEntity function.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Hi,&lt;br /&gt;I use the smart node "Query database".&lt;br /&gt;Someone has try t</title><link>https://community.appian.com/thread/24028?ContentTypeID=1</link><pubDate>Tue, 27 Oct 2015 12:48:54 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:9388ed12-b338-4883-a93c-7644f52e956b</guid><dc:creator>Victor Bouchery</dc:creator><description>I can&amp;#39;t use QueryEntity because i need to request several tables with 1..n relationship. It will be implemented as nested mulitiples in Appian, but it&amp;#39;s not recomanded due to performance issues and a!QueryEntity does not support request on nested multiple field.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Hi,&lt;br /&gt;I use the smart node "Query database".&lt;br /&gt;Someone has try t</title><link>https://community.appian.com/thread/24022?ContentTypeID=1</link><pubDate>Tue, 27 Oct 2015 08:40:04 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:68c1d9be-d3bd-41f5-87ae-853db75732ff</guid><dc:creator>anshuk170</dc:creator><description>Try using a!queryEntity function to achieve what you are looking for.You can create rule inputs for the coloumns that you want to fetch.Query Db smartservice also degrades the performance of the application.As a best practice try using a!queryEntity functon.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Hi,&lt;br /&gt;I use the smart node "Query database".&lt;br /&gt;Someone has try t</title><link>https://community.appian.com/thread/23995?ContentTypeID=1</link><pubDate>Mon, 26 Oct 2015 21:18:01 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:64f68116-9c9e-4efc-b807-5d11580cb26e</guid><dc:creator>Mike Schmitt</dc:creator><description>any particular reason you can&amp;#39;t use a!queryEntity?&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Hi,&lt;br /&gt;I use the smart node "Query database".&lt;br /&gt;Someone has try t</title><link>https://community.appian.com/thread/23994?ContentTypeID=1</link><pubDate>Mon, 26 Oct 2015 20:49:05 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:71953297-6e5c-4173-bd3b-03aa13c53fa0</guid><dc:creator>Victor Bouchery</dc:creator><description>Ok, thank you for your feed back.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Hi,&lt;br /&gt;I use the smart node "Query database".&lt;br /&gt;Someone has try t</title><link>https://community.appian.com/thread/23993?ContentTypeID=1</link><pubDate>Mon, 26 Oct 2015 20:36:52 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:5f3926d2-c6fb-4a3d-a4b8-da2eb4479138</guid><dc:creator>Chris</dc:creator><description>I don&amp;#39;t believe you will be able to dynamically define the selection fields with the Query Database node.  You can either pull back all columns you would need in each query, or run multiple Query DB nodes as you are now.  Another alternative would be to use the Execute Stored Procedure node - create a procedure in SQL that allows you to send column name as an input, for use in a dynamic query there.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>