Config Console Standards dictate that in this context the one-to-many relation in this should be qu

I am trying to add a field I made over in WorkAssignment BC, over to the JobApplication BC. I can find the field and add it but it is grayed out and not editable by the user. When I look at the LPL, I see that it is underlined in yellow and giving this warning:

"Standards dictate that in this context the one-to-many relation in this <ParentLink> should be qualified with 'first' or 'last'"

Can I do this and if so, what is needed to make the field editable?

Thank you,

Chris

0911060553270289.pdf

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Accepted answers

All comments

Chad Dirst

It sounds like it needs to know what work assignment you are looking for. If you want the primary (active) work assignment you could use this reference:

ActivePrimaryWorkAssignmentRel.YourFieldName

unknown

if its one to many used in a list, it has to be identified by the first or last and will not be editable since the OTM is in a different business class

chris-mccullough

Thank you both for your quick reply! So it sounds like it is not editable regardless of me figuring out the warning? I have attached it here.

I guess I have to create another field in the JobApplication business class and then have a process to update the main field on the WorkAssignment business class? What does OTM stand for?

unknown

One to Many.

As a side note, it really depends how many work assignments per job you have to update the main field on the Work Assignment business class. It could be a very long running process

chris-mccullough

Thank you

chris-mccullough

Chad, I tried EmployeeRel.EmployeeRel.ActivePrimaryWorkAssignmentRel.UCHEXPDT
That did get rid of the warning, but it's still not an editable field the otm seems to be the issue then.

unknown

the relationship of ActivePrimaryWorkAssignmentRel is a one to one and you are grabbing a specific field. This value "might" show the incorrect value for a secondary work assignment since you are always referencing the Active primary (additionally if a person does not have an active primary, the relation would not work either)

chris-mccullough

Thank you- So when my custom field is used on the workassignment business class and lets say that employee has 2 works assignments...both active with one the primary... by adding this same field over in JobApplication, there is no way to tie it to the specifc job it is on then... I think this is making sense. Maybe I need to rething the entire thing.
HR wants a field called "Relevant Job Experience" that will house the years of experience you have in your field...they wanted it on the WorkAssingnment which makes sense because you can have multiple jobs each with their own years of experience. But now the Talent Acquisition team is responsible for adding that info when they are making an offer for the employee... I suppose I could make a new field in JobApplication and after that employyee is hired, take the field from JobApplication and then find the Workassignment that matches via Job/Position and update the field on the workassignment....would that work? Sorry, this is a bit too much

Copyright © 2025 Infor. All rights reserved.