Anyone else having trouble after the April CU running their Employee Export from GHR to S3?

We started having trouble running the Employee Export from GHR to S3 since the monday after the april CU. Originally we were receiving -

S3 Transaction WriteRcvr: AGS Error com.lawson.security.authen.httpclient.LawsonHttpClientException: Login Failed

but after recommendation by support we got the process to give us a true error in the logs. we eventually were directed to KB 2295640 and asked to follow those steps in adding the extra lines of javascript to the GetValue assign node.

// Landmark 2023.04 Encoding Enforcement Change//

GetEmployeeExport_PreferredNonWorkPhoneInternationalPrefix = GetEmployeeExport_PreferredNonWorkPhoneInternationalPrefix.replace(/s/g,"");

GetEmployeeExport_WorkPhoneInternationalPrefix = GetEmployeeExport_WorkPhoneInternationalPrefix.replace(/s/g,"");

GetEmployeeExport_Name_FamilyNamePrefix = encodeURI(GetEmployeeExport_Name_FamilyNamePrefix);

GetEmployeeExport_Name_FamilyName = encodeURI(GetEmployeeExport_Name_FamilyName);

GetEmployeeExport_Name_GivenName = encodeURI(GetEmployeeExport_Name_GivenName);

GetEmployeeExport_Name_PreferredGivenName = encodeURI(GetEmployeeExport_Name_PreferredGivenName);

GetEmployeeExport_Name_MiddleName = encodeURI(GetEmployeeExport_Name_MiddleName);

------

After doing so we began seeing records moving to 'processed' status but in S3 the record made it there BUT no fields were actually updated. This has been a frustration in trying to get this to work without issue since last monday. I'm curious if anyone began having trouble with the same process. The standard defined process name is - HRMEmployeeExport10

Ford GTL.pdf

Find more posts tagged with

Process Automation (IPA) - General Discussions

Accepted answers

All comments

unknown

Hi Noe,

We got the Login Failed, but in a different situation. First, here is a blurb that Infor put out:

In our case, I was using a Lawson Query in an IPA flow. When building the Query, I had been using a pipe delimiter for the results and it was working fine. After the CU I got Login Failed for my query. After reaching out to Infor, they had me change the delimiter to something other than a pipe. That fixed the issue.

In other words, I changed DELIM=| to DELIM=* at the end of the this string. That's all it took to make it work.

PROD=LSAPPS&FILE=PAEMPPOS&FIELD=EMPLOYEE;POS-LEVEL;PAY-RATE;WORK-ASSIGNMNT;EFFECT-DATE&SELECT=END-DATE=&OUT=CSV&DELIM=*

Bottom line, I think that with the changes, a Login Failed error can come up in different circumstances. It seems to be a generic error and does not indicate what the error really is. It could be anything that is not meeting "HTTP Standard Encoding".

David

russel-cornelson

In order to assist you I would need to see the actual call that is failing; have you opened an incident with Infor Process Automation Support?

Inquiry Tab Placement.docx

unknown

KB 2295640 has the information on this issue. It includes notes on how to get the actual error message. It mentions the Delimiter which is what I brought up in my earlier comment.

0904080826502268.xls

Noe Ramos

thank you for the responses. so the initial issue we had was resolved for the most part BUT what it ended up doing was sending records to S3 and showing processed without updating all the fields it should have updated. There are no 'errors' mentioned on the logging for the work unit.

for example - we have a team member new hire that has over 20 fields that should be updating in S3 but the only field that truly updated was the Union field.

we do have a incident open with infor but still trying to resolve.

the only place i show we have delim mentioned on the WriteRcvr node i show it to have the ending be -

&_DELIM=%09&_OUT=XML&_EOT=TRUE

i've updated the _DELIM above to be _DELIM=* and we continue to have 20+ fields supposed to be updating but only the UNION field gets updated on S3.

So i'm curious, does your team know if records being passed to S3 via this export are truly updating all fields? the employee export shows everything to be processed so the only way to know would be to look at the fields that should be updating and comparing to what updated in S3.

Infor has gone in circles with us.

looking at KB 2295640 there was a James who commented giving that a 1 star stating to be having the same issue.

Noe Ramos

thank you all for the responses. we ended up finding a few more fields but all looks to be working now.

Copyright © 2025 Infor. All rights reserved.