Landmark Transaction - Confirm All Warnings

Do you know if there is a parameter that you can pass to a Landmark Transaction in a flow to "Confirm All Warnings", similar to the option you get in the Infor Spreadsheet Designer?

Find more posts tagged with

Process Automation (IPA) - General Discussions

Comments

unknown

Hi Octavio - I've never seen IPA stop on a warning. What are you updating that is throwing the warning?

Can you post what you are seeing in the workunit log (suitably scrubbed for privacy)? Ideally, the call string and the response information...

Kelly

unknown

Hi Kelly,

I am trying to update the user field "EffectiveDateMHS" in the work assignment.

Please, see below the workunit log file for the Landmark Transaction LMTxn6010.

The response from the Landmark Transaction is "Work Assignment Updated". However, the field does not get updated.

I went into the Rich Client and manually performed the same update and that's when I got the warning.

The Landmark transaction does not error out, it just does not do the update to the work assignment.

Workunit Log File
-------------------

Activity name:LMTxn6010 id:58 started @ 03/09/2016 11:16:16.950 AM
Landmark:LMTxn6010 Executing transaction_dataArea="tmprod" & _module="hr" & _objectName="WorkAssignment" & _actionName="Update" & _actionOperator="NONE" & _actionType="CreateUpdateDelete" & _runAsUser="" & _authenticatedUser="" & _pageSize="30" & _relationName="" & _setName="" & _asOfDate="" & _effectiveDate="" & HROrganization="" & Employee="" & WorkAssignment="" & WorkAssignment_effective_date="" & WorkAssignment_reason_code="" & WorkAssignment_subject="HCM" & WorkAssignment_action_comment=""
Landmark:LMTxn6010 Executing transaction_dataArea="tmprod" & _module="hr" & _objectName="WorkAssignment" & _actionName="Update" & _actionOperator="NONE" & _actionType="CreateUpdateDelete" & _runAsUser="" & _authenticatedUser="" & _pageSize="30" & _relationName="" & _setName="" & _asOfDate="" & _effectiveDate="" & HROrganization="1" & Employee="80611" & WorkAssignment="1" & WorkAssignment_effective_date="20160225" & WorkAssignment_reason_code="PROMO" & WorkAssignment_subject="HCM" & WorkAssignment_action_comment="Import from 2XB" & EffectiveDateMHS="20160221"
Landmark:LMTxn6010 transaction complete:true,
response message:Work Assignment Updated,
record count:1,
results header string: HROrganization,Employee,WorkAssignment,WorkAssignment_effective_date,WorkAssignment_reason_code,WorkAssignment_subject,WorkAssignment_action_comment,
results string:1,80611,1,00000000,,HCM,,
has next:false,
has prev:false
LMTxn6010_complete = true
LMTxn6010_recordCount = 1
LMTxn6010_hasNext = false
LMTxn6010_hasPrevious = false
LMTxn6010_resultsHeader = HROrganization,Employee,WorkAssignment,WorkAssignment_effective_date,WorkAssignment_reason_code,WorkAssignment_subject,WorkAssignment_action_comment
Landmark:LMTxn6010 Page 1 retrieved
LMTxn6010_recordCount = 1
Activity name:LMTxn6010 id:58 completed @ 03/09/2016 11:16:17.592 AM
LMTxn6010_errorCode = 0
LMTxn6010_informationCode = 0
LMTxn6010_returnMessage = Work Assignment Updated
LMTxn6010_outputData = 1,80611,1,00000000,,HCM,
LandmarkLMTxn6010: Executing loop 1 of 1 (Page 1)
LMTxn6010_WorkAssignment_effective_date = 00000000
LMTxn6010_WorkAssignment_action_comment =
LMTxn6010_WorkAssignment_subject = HCM
LMTxn6010_HROrganization = 1
LMTxn6010_WorkAssignment = 1
LMTxn6010_Employee = 80611
LMTxn6010_WorkAssignment_reason_code =

Activity name:LMTxn6090 id:59 started @ 03/09/2016 11:16:17.806 AM
Landmark:LMTxn6090 Executing transaction_dataArea="" & _module="GenericInterface" & _objectName="EmployeeExport" & _actionName="Find" & _actionOperator="NONE" & _actionType="MultipleRecordQuery" & _runAsUser="" & _pageSize="30" & _filterString=RecordStatus="1" and ActionReason="" & _relationName="" & _setName="" & _asOfDate="" & _effectiveDate="" & Employee="" & HROrganization="" & UniqueID & SystemTimeStamp & TransactionId & HROrganization & Employee
Landmark:LMTxn6090 Executing transaction_dataArea="tmprod" & _module="GenericInterface" & _objectName="EmployeeExport" & _actionName="Find" & _actionOperator="NONE" & _actionType="MultipleRecordQuery" & _runAsUser="" & _pageSize="30" & _filterString=RecordStatus="1" and ActionReason="PROMO" & _relationName="" & _setName="" & _asOfDate="" & _effectiveDate="" & Employee="80611" & HROrganization="1" & UniqueID & SystemTimeStamp & TransactionId & HROrganization & Employee
Landmark:LMTxn6090 transaction complete:true,
response message:null,
record count:1,
results header string: UniqueID,SystemTimeStamp,TransactionId,HROrganization,Employee,
results string:01534517-1768-0000-000a-afb855f9c5ce,2016030916160849,155369,1,80611,
has next:false,
has prev:false
LMTxn6090_complete = true
LMTxn6090_recordCount = 1
LMTxn6090_hasNext = false
LMTxn6090_hasPrevious = false
LMTxn6090_resultsHeader = UniqueID,SystemTimeStamp,TransactionId,HROrganization,Employee
Landmark:LMTxn6090 Page 1 retrieved
LMTxn6090_recordCount = 1
Activity name:LMTxn6090 id:59 completed @ 03/09/2016 11:16:18.219 AM
LMTxn6090_errorCode = 0
LMTxn6090_informationCode = 0
LMTxn6090_returnMessage =
LMTxn6090_outputData = 01534517-1768-0000-000a-afb855f9c5ce,2016030916160849,155369,1,80611
LandmarkLMTxn6090: Executing loop 1 of 1 (Page 1)
LMTxn6090_TransactionId = 155369
LMTxn6090_HROrganization = 1
LMTxn6090_UniqueID = 01534517-1768-0000-000a-afb855f9c5ce
LMTxn6090_SystemTimeStamp = 2016030916160849
LMTxn6090_Employee = 80611

unknown

Odd. What is the warning do you get in Rich Client?

Since the warning doesn't appear in the log, that makes me think that isn't the issue - though I could be wrong. So, I'm going to go a different direction from your original question, so please forgive me. There are a couple of things I notice which may be worth investigating.

I don't see EffectiveDateMHC in our system - is it a user defined field? If so, can you confirm that it is not a derived or calculated field?

From looking at your log on line 7 (results header string) it ends with "WorkAssignment_action_comment" and then a comma. Based on this, it appears that the transaction node doesn't recognize that field. It also looks like there are other problems - effective date, action comment, and reason code are also not being populated correctly (as far as I can tell from the log). This could be because of the warning/error - but since we aren't seeing that message...

For investigation, you may want to copy the call from line 3, starting with _dataArea, and paste it into a Landmark Node in IPA Designer, then go into Build mode and verify that all the fields exist, then go into the "Test" tab and try doing the update from there. Try removing or modifying fields and retesting to see if you can figure out what's going on. Also, you might try building the call again from scratch in case there is a special character hidden in there somewhere (finger lying on the control key or something strange).

Unfortunately, Landmark transactions don't handle things that confuse them very well. They don't provide any feedback about fields they don't recognize, so it's very tough to troubleshoot.

I hope this helps...
Kelly

unknown

EffectiveDateMHS is a custom user field created with the Configuration Console. It is not derived or calculated.

See below the warning from the Rich Client:

unknown

Hmmm. It appears that LSD is sending allMessagesConfirmed="true". I guess you could try that, though the mechanisms used are different.

I'm curious - if this flow runs against a record where the PayRate is within the pay range (i.e. no warning is generated) does the update work correctly and the userfield get populated as expected?

unknown

I was using the variable in the Landmark Transaction which was populated with & EffectiveDateMHS="20160221"

The variable was replaced into the Landmark Transaction at run time.

I just replaced the variable in the Landmark Transaction with the following:

& EffectiveDateMHS=""

where the variable waEffectiveDateMHS is populated with “20160221”

That update was optional in another flow where I copied the code from. In this flow that update is required. Therefore, I can always specify that field in the update.

We'll be testing shortly. I'll let you know if it works.

unknown

It worked.

Thanks a lot for looking into this.

Copyright © 2025 Infor. All rights reserved.