https://community.appian.com/discussions/f/general/11549/can-t-add-second-acp-to-query-database-nodeI have a SQL query that&#39;s relatively complicated. It runs directly in Oracle, and the node validates when the values I&#39;m trying to replace with ACPs are hard coded. I can add one ACP before it tells me &quot;SQL command not properly ended&quot;. This is what Ien-USTelligent Community 12https://community.appian.com/thread/50869?ContentTypeID=1Wed, 13 Dec 2017 19:06:40 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:3bd89e4d-aa22-43db-b26b-bcaaa6c3e22daloks0189Hi <a href="/members/jessicae400">jessicae400</a> I am completely agree with @Mike ,View will be best option for you in this case.<br /> <br /> Also you can make the use stored procedure in such cases where you can write native SQL queries and can execute it from appian rules or process. But stored procedure is specially meant to perform some complex and time taking jobs.<br /> <br /> So I prefer going for View as the first option.<br /> <br /> Hope this will help you<div style="clear:both;"></div>https://community.appian.com/thread/50866?ContentTypeID=1Wed, 13 Dec 2017 17:36:41 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:1e6b686f-4321-4594-9a9a-be247c3cd63eMike SchmittJust FYI, I believe Appian best practices for this type of use case (in general) state to create a View, and then use the OOB queryEntity functionality to query on that view. This offers a lot of flexibility since you can build special things into the queryEntity function.<div style="clear:both;"></div>