Is it possible to terminate a landmark transaction multi-record-find (IPD) before processing all the

I prefer to bail out of the multi-find loop as soon as I find the two records I'm seeking. Is there an end-of- fetch condition I can manually set to exit prematurely? Something like LMTxn8920_hasNext = false?

My objective is to retrieve the two latest file extracts for FileCreationSetups 252 & 256. They must be concatenated before transmission to our partner.

VID031_ARSC_How to Force or Clear Form Validation.zip

Find more posts tagged with

General Discussions

Accepted answers

unknown

Yes, there is an option. In the IterEnd node of the LMRK txn, the "Break Condition" can be defined and when the condition becomes true it would break out of the loop.

For example, a variable called exit can be defined in the start node and inside the LMRK txn loop, the variable exit can be set to true and then the below condition can be defined in the "Break Condition" section of the IterEnd node.

exit == true

This would break out of the landmark transaction loop when the exit is set to true inside the loop when your conditions are met.

0811181026417683.xls

sthiemann

Just had a chance to test this, and it works! Thanks for the assist. Been a while since I paid much attention to an End-LMTxn node, but this was just the ticket.

All comments

unknown

Yes, there is an option. In the IterEnd node of the LMRK txn, the "Break Condition" can be defined and when the condition becomes true it would break out of the loop.

exit == true

This would break out of the landmark transaction loop when the exit is set to true inside the loop when your conditions are met.

0811181026417683.xls

sthiemann

Just had a chance to test this, and it works! Thanks for the assist. Been a while since I paid much attention to an End-LMTxn node, but this was just the ticket.

unknown

You're welcome! Did it work with <!> variable format? Can you check in the workunit log for any errors? If you find any errors related to this or does not work as expected then try it without <!> format as shown below,

FileProcessCount > 1

November 2020 webinar with David Foster.mp4

sthiemann

FileProcessCount is incremented in the final assign node of the FileCreationFile loop. The log shows the next node performed is SetVars, which is outside the loop. So it worked as expected with the <!> notation. I coded the condition in End-FCFile node using the Ctl-space selection, which supplied the variable as <!FileProcessCount>. Testing revealed that either expression produces the same result.

FileProcessCount same result

Copyright © 2025 Infor. All rights reserved.