<?xml version="1.0" encoding="UTF-8"?>        <rss version="2.0"
             xmlns:atom="http://www.w3.org/2005/Atom"
             xmlns:dc="http://purl.org/dc/elements/1.1/"
             xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
             xmlns:admin="http://webns.net/mvcb/"
             xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
             xmlns:content="http://purl.org/rss/1.0/modules/content/">
        <channel>
            <title>
									Scheduled Queries - AugSQL				            </title>
            <link>https://www.augforums.com/forums/augsql/scheduled-queries/</link>
            <description>Acumatica User Group Forums</description>
            <language>en-US</language>
            <lastBuildDate>Sun, 11 Oct 2026 02:00:21 +0000</lastBuildDate>
            <generator>wpForo</generator>
            <ttl>60</ttl>
							                    <item>
                        <title>RE: Scheduled Queries</title>
                        <link>https://www.augforums.com/forums/augsql/scheduled-queries/#post-10792</link>
                        <pubDate>Mon, 17 Jul 2023 04:05:19 +0000</pubDate>
                        <description><![CDATA[As I was creating the Passing Parameters to SQL Queries idea (click here), I thought about a different way to handle this Scheduled Queries idea.
 
What if, instead of adding a tab called ...]]></description>
                        <content:encoded><![CDATA[<p>As I was creating the <a href="https://www.augforums.com/forums/augsql/passing-parameters-to-sql-queries/" target="_blank" rel="noopener"><strong>Passing Parameters to SQL Queries idea (click here)</strong></a>, I thought about a different way to handle this Scheduled Queries idea.</p>
<p> </p>
<p>What if, instead of adding a tab called <span style="text-decoration: underline">SQL QUERIES</span> to the <span style="text-decoration: underline">Automation Schedules (SM205020)</span><span> screen, we instead added a tab called <span style="text-decoration: underline">URLS</span>.</span></p>
<p> </p>
<p>Then, you could add whatever URLs you want to the <span style="text-decoration: underline">URLS</span> tab, including URLs that follow the format of the <a href="https://www.augforums.com/forums/augsql/passing-parameters-to-sql-queries/" target="_blank" rel="noopener"><strong>Passing Parameters to SQL Queries idea (click here)</strong></a>:</p>
<p><a class="wpforo-auto-embeded-link" href="https://mycompany.acumatica.com/Main?CompanyID=SalesDemo&amp;ScreenId=QQ900003&amp;Action=RunQuery&amp;MyParam1=MyValue1&amp;MyParam2=MyValue2" target="_blank" rel="nofollow noopener">https://mycompany.acumatica.com/Main?CompanyID=SalesDemo&amp;ScreenId=QQ900003&amp;Action=RunQuery&amp;MyParam1=MyValue1&amp;MyParam2=MyValue2</a></p>
<p> </p>
<p>This would allow you to schedule not only SQL Queries, but any URL, which has additional use cases like needing to trigger something to happen in an outside system.</p>]]></content:encoded>
						                            <category domain="https://www.augforums.com/forums/augsql/">AugSQL</category>                        <dc:creator>Tim Rodman</dc:creator>
                        <guid isPermaLink="true">https://www.augforums.com/forums/augsql/scheduled-queries/#post-10792</guid>
                    </item>
				                    <item>
                        <title>Scheduled Queries</title>
                        <link>https://www.augforums.com/forums/augsql/scheduled-queries/#post-10790</link>
                        <pubDate>Mon, 17 Jul 2023 03:20:56 +0000</pubDate>
                        <description><![CDATA[This idea would depend on the completion of this Saved SQL Queries idea:
 
Once we have the ability to save SQL queries, it would be great if we could run those queries on a schedule.
 
...]]></description>
                        <content:encoded><![CDATA[<p>This idea would depend on the completion of this Saved SQL Queries idea:</p>
<p><a href="https://www.augforums.com/forums/augsql/saved-sql-queries">https://www.augforums.com/forums/augsql/saved-sql-queries</a></p>
<p> </p>
<p>Once we have the ability to save SQL queries, it would be great if we could run those queries on a schedule.</p>
<p> </p>
<p>This idea is an initial high-level proposal for how to do that.</p>
<p> </p>
<p>A lot of this will depend on how difficult it would be to tap into the current Automation Schedule functionality and we might discover that it would be simpler to build our own schedule logic. So I'm not sure how that will turn out, but I'm outlining what things would look like in my perfect world, without the inconvenient constraints of technical feasibility.</p>
<p> </p>
<p>In my perfect world, we would add a tab to the existing <span style="text-decoration: underline">Automation Schedules (SM205020)</span> screen called <span style="text-decoration: underline">SQL QUERIES</span>, next to the existing <span style="text-decoration: underline">EVENTS</span> tab. The <span style="text-decoration: underline">SQL QUERIES</span> tab would list the SQL Queries that have been assigned to a specific Automation Schedule.</p>
<p> </p>
<p>Then, on the <span style="text-decoration: underline">AugSQL Saved Queries (QQ900003)</span><span> screen, there would be a new tab called <span style="text-decoration: underline">SCHEDULES</span> that would behave the same as the <span style="text-decoration: underline">SCHEDULES</span> tab on the existing <span style="text-decoration: underline">Business Events (SM302050)</span> screen in that it would list the schedules that a specific SQL Query has been assigned to.</span></p>
<p> </p>
<p>As long as the schedule is Active, then the SQL Query would get executed automatically according to the defined schedule.</p>]]></content:encoded>
						                            <category domain="https://www.augforums.com/forums/augsql/">AugSQL</category>                        <dc:creator>Tim Rodman</dc:creator>
                        <guid isPermaLink="true">https://www.augforums.com/forums/augsql/scheduled-queries/#post-10790</guid>
                    </item>
							        </channel>
        </rss>
		