When saving on an existing HRMApplication immediately after having saved a different already-existing HRMApplication, the second record’s Application FK value was getting set to the previous record’s value. The issue turned out to be due to some Unit Of Work accommodation logic that was explicitly overwriting the HcmApplicant buffer in the case of an existing applicant being used in order to avoid UoW from doing an insert for that applicant, but the value used to retrieve the HcmApplicant buffer was from a form control that we couldn’t count on as being the correct value to retrieve by. When I updated this line of code to use the same applicant ID as was used to verify that the applicant already existed, the record stayed in sync just fine, and I was unable to repro the bug.
Id. de artículo: 4018228 - Última revisión: 30-03-2017 - Revisión: 1