<?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>
									How to Submit a Print Job - Team Ticket Downloader				            </title>
            <link>https://www.ticketattendant.com/community/team-ticket-downloader/how-to-submit-a-print-job/</link>
            <description>Ticket Attendant Discussion Board</description>
            <language>en-US</language>
            <lastBuildDate>Wed, 11 Mar 2026 07:41:27 +0000</lastBuildDate>
            <generator>wpForo</generator>
            <ttl>60</ttl>
							                    <item>
                        <title>How to Submit a Print Job</title>
                        <link>https://www.ticketattendant.com/community/team-ticket-downloader/how-to-submit-a-print-job/#post-66</link>
                        <pubDate>Wed, 18 Sep 2024 20:11:37 +0000</pubDate>
                        <description><![CDATA[From the Team Ticket Downloader you can automatically print groups of team tickets.


Select the Team that you want to print tickets for.


Select the Account that contains the tickets...]]></description>
                        <content:encoded><![CDATA[<article id="article-body" class="article-body">
<p dir="ltr"><span>From the Team Ticket Downloader you can automatically print groups of team tickets.</span></p>
<ol>
<li dir="ltr">
<p dir="ltr"><span>Select the </span><strong>Team</strong><span> that you want to print tickets for.</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>Select the </span><strong>Account</strong><span> that contains the tickets you want to print.</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>Select a </span><strong>Print Date Range</strong><span> to find event tickets to print within the given time frame.</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>Click </span><strong>Add Jobs</strong><span>.</span></p>
</li>
</ol>
<p> </p>
<div><img src="https://www.ticketattendant.com/wp-content/uploads/wpforo/default_attachments/1727980447-Screenshot-2024-10-03-at-13351PM.png" /></div>
<p> </p>
<p dir="ltr"><span>If the job is Completed, it will display how many tickets were found, printed, and attached to the POS in that order. At this point the JobID becomes a link. </span></p>
<p dir="ltr"> </p>
<div dir="ltr" align="left">
<table><colgroup><col /></colgroup>
<tbody>
<tr>
<td>
<p dir="ltr"><span>Pro Tip</span><span> </span></p>
<br />
<p dir="ltr"><span>We encourage TTD jobs to be run in batches as opposed to full seasons at a time. This is because the crawling process is extensive and can often run into blocks from third-party sites, especially when long processes are being run.</span></p>
<br />
<p dir="ltr"><span>We typically recommend keeping TTD jobs under 30-day date ranges maximum. If at all possible, attempt to run TTD jobs for individual game dates.</span></p>
</td>
</tr>
</tbody>
</table>
</div>
<p> </p>
</article>
<div id="wpfa-1901" class="wpforo-attached-file"><a class="wpforo-default-attachment" title="Screenshot-2024-10-03-at-1.33.51 PM.png" href="//www.ticketattendant.com/wp-content/uploads/wpforo/default_attachments/1727980447-Screenshot-2024-10-03-at-13351PM.png" target="_blank" rel="noopener"><i class="fas fa-paperclip"></i> Screenshot-2024-10-03-at-1.33.51 PM.png</a></div>]]></content:encoded>
						                            <category domain="https://www.ticketattendant.com/community/team-ticket-downloader/">Team Ticket Downloader</category>                        <dc:creator>Regan</dc:creator>
                        <guid isPermaLink="true">https://www.ticketattendant.com/community/team-ticket-downloader/how-to-submit-a-print-job/#post-66</guid>
                    </item>
							        </channel>
        </rss>
		