Linking Employer Relationship end date to Employment History end date

When an end date is added to an Employee/Employer Relationship, the same end date should be automatically added to the related Employment History row. Currently, these two dates need to be maintained separately which introduces the possibility of the data being out of sync and adds an additional data processing step for staff. It's our opinion that an individual cannot be employed by an organization with which they no longer have a relationship with, thus necessitating the need to have these two end dates tied together.
  • Guest
  • Jun 29 2015
  • Reviewed: Voting Open
Organization Name (Please enter full organization name)
Reported Version
  • Attach files
  • Kelli Crispin commented
    10 Sep, 2019 01:45pm

    It would be nice if this went the other way around also... If the employer relationship already has an end date and you add a new job title, the relationship end date should be removed. There is a great deal of messy non-synced data in our system because of this, and I'm having difficulty finding easy ways to fix the errors programmatically, when this should be a system function.

  • Stephen Mally commented
    22 Jan, 2019 10:42pm

    Please add this functionality!

  • Liz Hackett commented
    22 Jan, 2019 10:29pm

    Agreed, this is a no brainer!

  • Becky Batman commented
    25 Aug, 2016 02:26pm

    Career level needs to be added to the Relationships section and not be a separate piece in Employment history.  Any step out of sync with the original process is easily forgotten by updaters. 

  • Stephanie Boyce commented
    27 Jul, 2016 06:52pm

    This is just a best practice issue, I don't know why this has not been set up before, this really needs to be set up. 

  • and 18 more