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

AGS call returns Invalid Date error, regardless of format used

 5 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
TBonney
Veteran Member Send Private Message
Posts: 281
Veteran Member
2/11/2011 5:24 PM
Has anyone ever goptten an invalid date error on an AGS call, that, if processed manually through Portal, submits just fine?

I have a call that I am updating a batch job with. When I update the job manually in Portal, with all the exact same data as is being uised in the call, the job updates successfully.

However, if I submit the call from process flow, I get an error that says invalid date format. I even tested it directly through the browser and it returns the same error.

It's the As Of Date on BN106 (field #98) and it doesn't matter what format I try to use (02012011, 02/01/2011, 20110201, etc.), I still get the error. The error data returned from the call is as follows:
Invalid Date: 02/01/2011
  127
  001
  98

Please help if you can. Thank you!
TBonney
Veteran Member Send Private Message
Posts: 281
Veteran Member
2/11/2011 8:16 PM
Sorry all...I did end up getting my date working. It had to be sent in the AGS as yyyymmdd instead of mmddyyyy.

However, I'm still getting the "Fild is Required" error. I've even gone so far as to submit the call with a value present for every field on the form.

Lawson can't seem to figure out why...can anyone here?

Has anyone seen anything like this with an AGS call before?

Any direction on how to trouobleshoot this would be appreciated. I'm at my wits end.

Thanks.
David Williams
Veteran Member Send Private Message
Posts: 1127
Veteran Member
2/12/2011 12:06 PM
If submit the AGS call from the API builder it usually shows you which field it's referring to when it returns the error. Is that not happening? You are updating BN106?
David Williams
TBonney
Veteran Member Send Private Message
Posts: 281
Veteran Member
2/14/2011 3:03 PM
David,

Yes, it is BN106 that I am updating.

I am receiving the error, regardless of whether I submit the AGS call from P-Flow Log/Workbench window, directly through the browser, or through the API builder.

I get the error message at the end f the call, but it doesn't seem to tell me which "Field is Required" unless the file referenced directly following the erorr message is the field it's referring to, which doesn't make sense either because that is the TC field which is a hidden field and shouldn't be required to be sent in the call anyway.

So, I'm pretty confused because I can't figure out what field is causing the error. I've tried sending additional fields to see if maybe I was omitting a required field, but that didn't make the error go away either.

Do you have any suggestions or ideas? Thanks!
David Williams
Veteran Member Send Private Message
Posts: 1127
Veteran Member
2/14/2011 3:56 PM
Can you put your AGS call here so I can see it (or you can email it to me)?
David Williams
TBonney
Veteran Member Send Private Message
Posts: 281
Veteran Member
2/18/2011 8:26 PM
Here it is David.

Thank you for your assistance. Lawson says it is likely an IOS issue and suggests aplying any LSF patches that are out there to update the verison of IOS.

Any ideas you might have would be appreciated...

_PDL=<!--pProdli-->&_TKN=BN106&_EVT=CHG&_RTN=DATA&_LFN=ALL&_TDS=IGNORE&FC=C&JOB-NAME=BN106&USER-NAME=lawson&JOB-DESCRIPTION=BN106&COMPANY=2000&INS-CARRIER=RMSC&PLAN-TYPE=HL&PLAN-CODE1=MPPO&FILE-OPTION=2&DELETE-OPTION=N&TRAN-PURPOSE=2&AS-OF-DATE=20110301<!--rstofMon-->&RERUN-OPTION=1&ID-CODE=TBD<!--Co-->&MASTER-POLICY-NBR=N&EMP-RES-ADD=1&EMP-MAIL-ADD=1&EMP-CONT-NBR=1&INC-COV-OPT=Y&INC-PREM-AMT=N&MARITAL-STAT=Y&SMOKER-STAT=N&STUDENT-STAT=N&DISABLED-STAT=N&PRIOR-MONTHS-COV=N&PRIMARY-CARE-PROV=N&EMPLOYMENT-BEGIN=2&_DELIM=%09&_OUT=XML&_EOT=TRUE