﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Alliance Forums / General Support / Merchant Support  / List Pay / Latest Posts</title><generator>InstantForum.NET v4.1.2</generator><description>Alliance Forums</description><link>http://support.allianceach.com/forums/</link><webMaster>forums@allianceach.com</webMaster><lastBuildDate>Mon, 08 Sep 2008 00:02:45 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: List Pay</title><link>http://support.allianceach.com/forums/Topic219-4-1.aspx</link><description>My apologies, we have been on other items but should be able to get to this soon.</description><pubDate>Sat, 19 Jan 2008 08:40:28 GMT</pubDate><dc:creator>Paul</dc:creator></item><item><title>RE: List Pay</title><link>http://support.allianceach.com/forums/Topic219-4-1.aspx</link><description>I see the answer to my own question is: No.&lt;br&gt;&lt;br&gt;8 Transaction Submission(s) were successful. 8 Transaction Submission(s) Failed.&lt;br&gt;Submission Failed. Object reference not set to an instance of an object.&lt;br&gt;Submission Failed. Object reference not set to an instance of an object.&lt;br&gt;Submission Failed. Object reference not set to an instance of an object.&lt;br&gt;Submission Failed. Object reference not set to an instance of an object.&lt;br&gt;Submission Failed. Object reference not set to an instance of an object.&lt;br&gt;Submission Failed. Object reference not set to an instance of an object.&lt;br&gt;Submission Failed. Object reference not set to an instance of an object.&lt;br&gt;Submission Failed. Object reference not set to an instance of an object.&lt;br&gt;&lt;br&gt;It must be one hell of a curved grading system for 50% to not be "failing"!&lt;br&gt;&lt;br&gt;</description><pubDate>Fri, 18 Jan 2008 13:16:10 GMT</pubDate><dc:creator>pukka</dc:creator></item><item><title>RE: List Pay</title><link>http://support.allianceach.com/forums/Topic219-4-1.aspx</link><description>It's been 2 months, has anything been fixed with ListPay to make it usable?</description><pubDate>Fri, 18 Jan 2008 12:53:35 GMT</pubDate><dc:creator>pukka</dc:creator></item><item><title>RE: List Pay</title><link>http://support.allianceach.com/forums/Topic219-4-1.aspx</link><description>Once we can get into this it will function as intended.</description><pubDate>Mon, 12 Nov 2007 11:11:06 GMT</pubDate><dc:creator>Paul</dc:creator></item><item><title>RE: List Pay</title><link>http://support.allianceach.com/forums/Topic219-4-1.aspx</link><description>I spent the time going through and updating most of my storage records to listpay and then submitted a big batch of them.  Of the ~25 I submitted, more than half failed with no explanation however I am perfectly able to submit individual transactions to each storage record.&lt;br&gt;&lt;br&gt;It doesn't seem, based on my experience and that of others, that listpay is fully baked.  Please give it some TLC.  Thanks, &lt;br&gt;&lt;br&gt;&lt;br&gt;Brian&lt;br&gt;</description><pubDate>Mon, 05 Nov 2007 07:56:41 GMT</pubDate><dc:creator>pukka</dc:creator></item><item><title>RE: List Pay</title><link>http://support.allianceach.com/forums/Topic219-4-1.aspx</link><description>This was forwarded to IT on 10/6.  I am hoping it makes it to Dev queue by 11/15.</description><pubDate>Thu, 01 Nov 2007 10:09:42 GMT</pubDate><dc:creator>Paul</dc:creator></item><item><title>List Pay</title><link>http://support.allianceach.com/forums/Topic219-4-1.aspx</link><description>I have only tried it with a small sample but List pay has the potential to be really speed up our data entry.  There are two things that are making it not very helpful to us:&lt;br&gt;&lt;br&gt;1. The ordering of the transactions.  Is it random?  Ordered on some internal ID?  How about doing it the same way the storage page works - alphabetically on Friendly name?&lt;br&gt;&lt;br&gt;2. In my test transaction with two payments, one of them failed.  It didn't say why nor any suggestion on how to correct it leaving me to enter it by hand.  How about a more verbose error message? &lt;br&gt;&lt;br&gt;#1 is the deal breaker; #2 (assuming it happens rarely) is a nice-to-have although from a usability perspective it's considered a "critical" flaw.&lt;br&gt;&lt;br&gt;Thanks, &lt;br&gt;&lt;br&gt;&lt;br&gt;Brian&lt;br&gt;</description><pubDate>Thu, 04 Oct 2007 11:48:02 GMT</pubDate><dc:creator>pukka</dc:creator></item></channel></rss>