Does IPA allow nested relation fields to be included in Landmark transaction node

If I include a field like PrimaryWorkAssignment.HROrganizationUnit.Description on the LPL customized forms like Employee at a Glance it works but I am unable to do so in IPA

It only seems to work till PrimaryWorkAssignment.HROrganizationUnit level when trying to fetch data.

However PrimaryWorkAssignment.HROrganizationUnit.Description values works in filters on the Employee business class.

I have a workaround but wanted to know if this is a limitation in IPA or a bug.

_dataArea="<!appProdline>" & _module="hr" & _objectName="Employee" & _actionName="Find" & _actionOperator="NONE" & _actionType="MultipleRecordQuery" & _runAsUser="" & _authenticatedUser="" & _pageSize="300" & _filterString=PrimaryWorkAssignment.HROrganizationUnit.Description="XYZ" & _relationName="" & _setName="SymbolicKey" & _asOfDate="" & _effectiveDate="" & HROrganization="123" & Employee & PrimaryWorkAssignment & PrimaryWorkAssignment.HROrganizationUnit & PrimaryWorkAssignment.HROrganizationUnit.Description

Find more posts tagged with

Process Automation (IPA) - General Discussions

Accepted answers

unknown

I would use the Relationship name. Try this.. ActivePrimaryWorkAssignmentRel.HROrgUnitTeamStructureRel.Description

All comments

unknown

I would use the Relationship name. Try this.. ActivePrimaryWorkAssignmentRel.HROrgUnitTeamStructureRel.Description

unknown

This works. thanks

jreese

I was told by Infor that IPA can only go down two levels so even if you see it in the LPL code you can't access everything using the relationships to pull through IPA. One suggestion, if you are only needing to link to the Primary Work Assignment, you can enter IsPrimary = true in the filterString to only access information on the Primary Work Assignment and you should be able to enter HROrganizationUnit.Description to get the value you are looking for. Not asked by just an FYI, if you need the description of the ProcessLevel that the HROrganizationUnit roles up to you would use HROrgUnitTeamStructureRel.ParentUnitShortDescription to access that information.

One last bit of information, if you haven't looked at the File Creation Utility that was recently added by Infor, you might want to look at this as another tool to extract data from GHR. It isn't the quickest utility to run, yet, but it allows you to access fields at a level IPA might not be able to access in one query, create headers and footers, do one to many links, map data fields, and trigger a flow if necessary after it completes the extract.

russel-cornelson

I need to weigh in on this conversation with a word of warning to everyone.

@OriginalPoster
I would be very careful with that query.

- That query is declaring the "setName=symbolickey"; set=index. symbolickey=primary index.

- The primary index/symbolic key for employee is HROrganization,Employee.

- HROrganization="123" sets 1 field of the primary index

- Employee is not set, so we are providing 1 of 2 fields for the primary index.

This means the call to the database will return ALL employee records for HROrganization=123. The system will then post process the records returned from the database. But to do that you are using related fields inside the filter.

I have a sneaking suspicion that this landmark transaction is going to be extremely expensive to execute. At a bare minimum it's gonna return ...

All employee records where hrorganization=123;
All Work assignment records
All HrOrganizationUnit records

And if there is more than 1 page of results it might do this for every single page. If you are on Multi-tenant you are likely going to get memory utilization warnings.

@jreese
If you are using <busclass>.<busclass> you are correct. If you are using <relation>.<relation> you can drill deeper; however I urge extreme caution doing this.

Doing this in a filter could have detrimental effects on your system.
Doing this in a landmark transaction that is NOT populating all fields of an index could have detrimental effects on your system.

say i had 10,000 employees in my hrorg=123.
say i add a filter that will filter out all but 10.

if I put a relation1.relation2.field in the output, the database is going to return:
10,000 employee records
10,000 related table 1 records
10,000 related table 2 records

Then the LPA node has to spin through all that and ultimately throw out all of it except for 10 records.

andy

What is the recommended alternative if you need to filter by a related business class field like this example and there is no sufficient index to accommodate? Rep Set and Data Lake pull?

Copyright © 2025 Infor. All rights reserved.