• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums Integration / Customization IPA/ProcessFlow

getattachrec.exe odd error

 7 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
Ward Mitchell
New Member Send Private Message
Posts: 0
New Member
2/11/2011 10:45 PM
Friends. I have developed a process flow that pulls the comments using getattachrec.exe via the WebRun node for an email that we send out when ACH's are processed via our AP160.

The flow works fine, no errors (trust me on this).

We pull data from APPAYMENT and then build a html email. A part of that email include comments that were inputted in for the ACH. The call looks as attached.



For most ACH's we do, works fine. But for a couple, we received the following error today:



<!--l version="1.0" encoding="Windows-1252"-->Has anyone run into this error or know what would cause this? Because when we go to the AP90.1 and look at that invoice's comment, we see it as clear as day.

David Williams
Veteran Member Send Private Message
Posts: 1127
Veteran Member
2/12/2011 12:03 PM
It looks like you have your vendor number hardcoded to 71 - is this invoice from the same vendor?
David Williams
Ward Mitchell
New Member Send Private Message
Posts: 0
New Member
2/13/2011 3:01 PM
I see that and changed that. Still get the error though. Good catch - I ve been pulling and plopping code trying to figure this one out.
David Williams
Veteran Member Send Private Message
Posts: 1127
Veteran Member
2/13/2011 3:19 PM
Are they always the same comment type? For example "Invoice Check Comments"?
David Williams
Ward Mitchell
New Member Send Private Message
Posts: 0
New Member
2/13/2011 3:24 PM
Yes they will always be these types of comments since we are showing the total invoices that belong to a particular ACH run
Ward Mitchell
New Member Send Private Message
Posts: 0
New Member
2/14/2011 2:06 PM
Figured this out friends:

The K2 variable had plus signs prior to my variable. K2 is the second item in the index and the plus signs should not be there. What is funny is that this whole time in our testing they have been taking until this past Friday. Odd! But nonetheless, fixed.
Stuart Perkins
Basic Member Send Private Message
Posts: 18
Basic Member
4/15/2011 11:58 AM
I'm having a similar problem. Attachments function well under LID but Portal returns the Parent Not Found error (38 or in output TEXT mode 5038). No funny characters on the key values though...company, employee (both numerics) and a claim number (text field). Really scratching my head on this one.
Stuart Perkins
Basic Member Send Private Message
Posts: 18
Basic Member
5/13/2011 6:15 PM
Resolved my issue.

Make sure that the database definition of the key fields of the main table match.  Our problem was that the field was defined "Alpha", but the form was "AL", which allowed lower case entries...lower case values were being translated by the drill function due to the GEN database definition, and voila... "Parent Record Not Found"...

Major symptom is "does it work under LID but not Portal?"...

Change database definition to "AlphaLC", dbreorg, and it works.

Make sure that no such translations are happening in the drill layer by ensuring that all data meets dbdef constraints.