Multiple criteria in filter string in transaction node

Is it possible to have multiple criteria in a filter string in a trx node for landmark:

_dataArea="<!appProdline>" & _module="hr" & _objectName="EmployeeIdentificationNumber" & _actionName="Find" & _actionOperator="NONE" & _actionType="MultipleRecordQuery" & _runAsUser="" & _authenticatedUser="" & _pageSize="30" & _filterString="PartOfIdentificationNumber= "<!poSS>" %26 IdentificationNumberDisplay= "<!SS>"" & _relationName="" & _setName="" & _asOfDate="" & _effectiveDate="" & HROrganization="1000" & IdentificationNumber="" & IdentificationNumberDisplay="" & PartOfIdentificationNumber & Employee & EmployeeIdentificationNumber

I tried this:

"PartOfIdentificationNumber= "<!poSS>" %26 IdentificationNumberDisplay= "<!SS>""

and this:

"PartOfIdentificationNumber= "<!poSS>" & IdentificationNumberDisplay= "<!SS>""

But its not working.

This new field search PartOfIdentificationNumber= <!poSS> is supposed to speed up the search of SS#'s in your system. You feed it the 2nd, 4th, 6th and 8th character and it will bring back matches very quickly...now I just need to get the exact match.

Thanks! Chris

Find more posts tagged with

Process Automation (IPA) - General Discussions

Accepted answers

All comments

unknown

Hi Chris - Try "and" in your statement. This is from the infocenter: "The filter string can contain a compound expression, using "and" or "or" (must be all lowercase) to separate expressions. Parentheses can be used for grouping. "

chris-mccullough

Thank you! I just tried this:

"PartOfIdentificationNumber= "<!poSS>" and IdentificationNumberDisplay= "<!SS>""

and

"PartOfIdentificationNumber= "<!poSS>"" and "IdentificationNumberDisplay= "<!SS>""

Neither seemed to work. Ill peak at infocenter too

chris-mccullough

This seemed to work -as in it brought back results - but was just a slow as IdentificationNumberDisplay= "123-45-6789"

_filterString="(PartOfIdentificationNumber= "2468" and IdentificationNumberDisplay= "123-45-6789")"

Was hoping it would be just as fast as PartOfIdentificationNumber= "2468"

jreese

I don't quote the _filterString statement and only the values if they are strings. So for your example I would try

_filterString=(PartOfIdentificationNumber = "<!poSS>" and IdentificationNumberDisplay="<!SS>")

I think we were told this should speed up searches even through Config Console but don't believe we saw any improvements either.

russel-cornelson

My test system is devoid of LTM data at the moment so I can't test it here right now with an LTM specific business class.

If I were going to test this though, I would try:

1. When building the transaction I would select SetName = "ByIdentificationNumber"
-- according to the lpl there is an index on this which includes: HROrganization,Country,PartOfIdentificationNumber,Employee,EmployeeIdentificationNumber.

2. After selecting the set, the index fields should appear in the builder as "key fields" double click on the PartOfIdentificationNumber, and the EmployeeIdentificationNumber fields so they are in the "Selected Fields/Values" section.

3. In the value column beside PartOfIdentificationNumber, double click and enter your 2468 part #

4. On the properties tab: in the filter section add EmployeeIdentificationNumber = "123456789"

5. When you have this done, make sure you test this with "Dataviews ON and OFF" for performance. That setting is on the bottom of the properties tab when the LmrkTransaction Node is selected.

NOTE: I would need to confirm this is what actually happens; but my belief is when you use the "filter" option then IPA is going to post process any records returned from the database to find the ones you want. By populating the key fields option; it should only return records that match that partial number, and spin through those results.

If I am right that should return much faster; if it doesn't ... then i need to get my ltm system back up and functional with data so I can test it further.

Example using IPA Data:

chris-mccullough

This is awesome - thank you Russ! I took your advise and tried your suggestions - but it still ran slow

I am trying this now and still getting slow responses. It's like it does not want to recognize the IdentificationNumberDisplay as part of the filter which would be the way to actually find someone's specific Identification number:

_dataArea="<!appProdline>" & _module="hr" & _objectName="EmployeeIdentificationNumber" & _actionName="Find" & _actionOperator="NONE" & _actionType="MultipleRecordQuery" & _pageSize="30" & _filterString="PartOfIdentificationNumber= <!poSS> and IdentificationNumberDisplay="<!SS>"" & _setName="ByIdentificationNumber" & HROrganization="1000" & Employee & EmployeeIdentificationNumber & IdentificationNumberDisplay & IdentificationNumber

chris-mccullough

This is working now....

_dataArea="<!appProdline>" & _module="hr" & _objectName="EmployeeIdentificationNumber" & _actionName="Find" & _actionOperator="NONE" & _actionType="MultipleRecordQuery" & _runAsUser="" & _authenticatedUser="" & _pageSize="30" & _filterString=IdentificationNumberDisplay="<!SS>" & _relationName="" & _setName="ByIdentificationNumber" & _asOfDate="" & _effectiveDate="" & HROrganization="1000" & Country="US" & PartOfIdentificationNumber="<!poSS>" & Employee & IdentificationNumber

russel-cornelson

Great, is it running faster than before? I see you populated addition fields in the index. Did that help with performance?

0712050808501819.doc

chris-mccullough

Yes, the additions helped. It now runs < 1 second - from 50 seconds. So awesome. Love this enhancement!!!

Copyright © 2025 Infor. All rights reserved.