<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.talis.com/tdn" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Talis Developer Network - how to exclude borrowers with a particular standard message from a report - Comments</title>
 <link>http://www.talis.com/tdn/node/1790</link>
 <description>Comments for &quot;how to exclude borrowers with a particular standard message from a report&quot;</description>
 <language>en</language>
<item>
 <title>Excluding borrowers with a message</title>
 <link>http://www.talis.com/tdn/node/1790#comment-701</link>
 <description>&lt;p&gt;Hello Brian&lt;br /&gt;
thanks for the replies&lt;br /&gt;
the subquery solution works fine and takes about 3 mins to run&lt;br /&gt;
I can&#039;t get the synchronised solution to work but I suspect that this is still because a borrower can have multiple messages, &lt;/p&gt;
&lt;p&gt;just wanted to let you know how impressed I am by the support via the TDN, thanks&lt;/p&gt;
&lt;p&gt;Lin&lt;/p&gt;
</description>
 <pubDate>Mon,  1 Sep 2008 10:59:44 +0100</pubDate>
 <dc:creator>lcartwright</dc:creator>
 <guid isPermaLink="false">comment 701 at http://www.talis.com/tdn</guid>
</item>
<item>
 <title>Excluding borrowers with a message</title>
 <link>http://www.talis.com/tdn/node/1790#comment-700</link>
 <description>&lt;p&gt;The reason for this is that the data returned has a separate row for each message that a borrower currently has.  While you can exclude the row that has the message it is difficult for SQL to act across rows.&lt;/p&gt;
&lt;p&gt;You need to approach this in a different way.&lt;/p&gt;
&lt;p&gt;One approach would be to do two queries. One with all borrowers and then one with borrowers that have the message.  By synchronising the queries and using report filters you can bet a list.  There is an article &lt;a href=&quot;http://www.talis.com/tdn/system/files?file=art_bo166rep02.pdf&quot;&gt;Synchronising queries in Talis Decisions&lt;/a&gt; that discusses the theory of joining queries.&lt;/p&gt;
&lt;p&gt;The other approach is to use a subquery within the main query.  The sub query returns borrowers with the message but then the main query says to exclude the borrowers returned from the subquery in the main query results.  The article on this has just been published at &lt;a href=&quot;http://www.talis.com/tdn/system/files?file=art_bo239rep01.pdf&quot;&gt;Using subqueries in Talis Decisions&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;There are advantages and disadvantages in using either and the best approach has to be judged within the context of the actual document required.&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;
&lt;p&gt;Brian Crampton&lt;br /&gt;
Developer, Talis&lt;/p&gt;
</description>
 <pubDate>Thu, 28 Aug 2008 17:57:25 +0100</pubDate>
 <dc:creator>Brian Crampton</dc:creator>
 <guid isPermaLink="false">comment 700 at http://www.talis.com/tdn</guid>
</item>
<item>
 <title>Excluding borrowers with a message</title>
 <link>http://www.talis.com/tdn/node/1790#comment-699</link>
 <description>&lt;p&gt;in the query panel for conditions I am using&lt;/p&gt;
&lt;p&gt;from the circ universe, borrowers&lt;br /&gt;
object: borrower type&lt;br /&gt;
operand: in list - selected borrower types to include &lt;/p&gt;
&lt;p&gt;from borrowers, conditions I am using&lt;br /&gt;
object: standard messages&lt;br /&gt;
operand: not equal to &#039;selected standard message&#039;&lt;/p&gt;
&lt;p&gt;from Loans, due date reporting&lt;br /&gt;
object: due date&lt;br /&gt;
operand:  less than or equal to &#039;selected date&#039;&lt;/p&gt;
&lt;p&gt;filter:limit to current issues&lt;/p&gt;
&lt;p&gt;in the reporting panel I am currently using only&lt;br /&gt;
object:borrower details,  barcode&lt;/p&gt;
&lt;p&gt;Just so we are clear I am trying to EXCLUDE from the list borrowers who have a particular standard message from the list&lt;/p&gt;
</description>
 <pubDate>Tue, 26 Aug 2008 17:37:47 +0100</pubDate>
 <dc:creator>lcartwright</dc:creator>
 <guid isPermaLink="false">comment 699 at http://www.talis.com/tdn</guid>
</item>
<item>
 <title>Excluding borrowers with a message</title>
 <link>http://www.talis.com/tdn/node/1790#comment-698</link>
 <description>&lt;p&gt;If you are using a query filter &lt;/p&gt;
&lt;p&gt;Standard messages in list Block Borrower&lt;/p&gt;
&lt;p&gt;then it should only pick up the borrowers with that message.  With the report filter it is more complicated because you are just restricting the row with the message and not the other message rows for a borrower.&lt;/p&gt;
&lt;p&gt;However the other objects used may be causing a problem.  Could you list the objects used in the query panel for both reporting and conditions. Can you include the classes the objects come from and what operands and values are used in the conditions.&lt;/p&gt;
&lt;p&gt;Brian Crampton&lt;br /&gt;
Developer, Talis&lt;/p&gt;
</description>
 <pubDate>Tue, 26 Aug 2008 15:48:30 +0100</pubDate>
 <dc:creator>Brian Crampton</dc:creator>
 <guid isPermaLink="false">comment 698 at http://www.talis.com/tdn</guid>
</item>
<item>
 <title>how to exclude borrowers with a particular standard message from a report</title>
 <link>http://www.talis.com/tdn/node/1790</link>
 <description>&lt;p&gt;I am a very new user so please excuse me if this is simple&lt;br /&gt;
I want to produce a list of borrowers with long overdue loans and to exclude from the list borrowers who have a particular standard message.  if I use a query filter that excludes this  message I still get borrowers with this message included in the output I guess because they also have other standard messages. including or excluding the standard message from the output makes no differenc. if I include all standard messages in the output and then use a report filter I get the same results.&lt;/p&gt;
</description>
 <comments>http://www.talis.com/tdn/node/1790#comments</comments>
 <category domain="http://www.talis.com/tdn/taxonomy/term/86">Talis Decisions</category>
 <pubDate>Tue, 26 Aug 2008 13:17:24 +0100</pubDate>
 <dc:creator>lcartwright</dc:creator>
 <guid isPermaLink="false">1790 at http://www.talis.com/tdn</guid>
</item>
</channel>
</rss>
