<?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>processing 50000+ entries</title><link>https://community.appian.com/discussions/f/best-practices/14922/processing-50000-entries</link><description>Hi all, 
 
 We have the requirement to read from different databases 50k + entries, apply some validation rules and for the ones that fail the validaiton generate an approval workflow. 
 
 The recommendation that we have been given to the customer is</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: processing 50000+ entries</title><link>https://community.appian.com/thread/66788?ContentTypeID=1</link><pubDate>Wed, 22 May 2019 08:19:34 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:009a7123-6384-48d0-99ec-72d31da5d432</guid><dc:creator>jesusa583</dc:creator><description>&lt;p&gt;Hi Stewart. Option 1 is also our preferred way. We still Need to find out how complex is the logic to filter the data. If possible we will use a stored procedure. I dont know yet the size of the filtered data but even if it is big as it is already filtered we will only Need the list of Ids and Display them in some forms. Thanks for your answer.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: processing 50000+ entries</title><link>https://community.appian.com/thread/66787?ContentTypeID=1</link><pubDate>Wed, 22 May 2019 08:06:18 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:074ba98d-daab-495b-b6b7-da7ef2b960e7</guid><dc:creator>Stewart Burchell</dc:creator><description>&lt;ol&gt;
&lt;li&gt;How complex are the validation rules? Could these be effectively applied in the initial data-set selection? That is, the data is effectively pre-filtered before it ever gets to Appian?&lt;/li&gt;
&lt;li&gt;If you can do 1. (and you can&amp;nbsp;conduct some quite sophisticated logic in the database layer e.g. using a Stored Procedure) then what&amp;#39;s the likely size of the result-set? 1%? 10%? 50%? 95%? It&amp;#39;s worthwhile profiling the data to understand the magnitude of the problem and then you can design accordingly.&lt;/li&gt;
&lt;/ol&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: processing 50000+ entries</title><link>https://community.appian.com/thread/66781?ContentTypeID=1</link><pubDate>Wed, 22 May 2019 01:31:26 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:72bb3181-e5a2-49a4-9c7d-7e93f8a1f983</guid><dc:creator>TJ</dc:creator><description>&lt;p&gt;Agreed. Appian advises complex data processes to be done outside the Appian platform.&amp;nbsp;&amp;nbsp;Please use a Java service or employ ETL and then trigger Appian workflow.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>