web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

When trying to add a new dependent [in the Employee Dependents window] to this Employee ID I am receiving the error message: "This record has been created since your attempt to create it. Changes won't be saved."

(0) ShareShare
ReportReport
Posted on by 110

When trying to add a new dependent [in the Employee Dependents window] to this Employee ID I am receiving the error message: "This record has been created since your attempt to create it. Changes won't be saved." Seems to only happen on this one Employee ID.  I had all users exit GP and have replicated this in the Test company and it don’t receive this error.  

FYI…the client had a server freeze last week that may have contributed to these issues.  

The “Dependents” option is showing up twice under HR > Employee.  When clicking on the first “Dependents” I receive the error message: "This module isn't registered. To register this module, contact your Microsoft Dynamics GP representative."  Again the Test company and the Fabrikam company do NOT have this showing.  

 

I have thus tried to run checklinks on the payroll module, but that didn't help and neither did running the dex lock dex session.  Any other advice?

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    soma Profile Picture
    24,410 on at

    Run the below query after all the users logged off from GP and try again.

    DELETE DYNAMICS..ACTIVITY

    DELETE TEMPDB..DEX_LOCK

    DELETE TEMPDB_DEX_SESSION

    DELETE DYNAMICS..SY00800

    DELETE DYNAMICS..SY00801

    Hope this helps!!!

  • Suggested answer
    Rob White Profile Picture
    15 on at

    I had this same problem and found that when dependents are added records are inserted to table UPR00111 and this table has a trigger that inserts records into table APR_UPR00111.  But if a dependent is deleted it does not get deleted from the APR_UPR00111 table and adding future dependents to this employee will fail because of a primary key error.  You have to remove the record for the dependent that was deleted in the APR_UPR00111 table

    delete from APR_UPR00111

    from  APR_UPR00111 full outer join UPR00111

    on UPR00111.EMPLOYID = APR_UPR00111.EMPLOYID and UPR00111.SEQNUMBR = APR_UPR00111.SEQNUMBR

    where APR_UPR00111.EMPLOYID='108511' and UPR00111.EMPLOYID is null

  • tknow Profile Picture
    817 on at

    Rob,

    Thanks for posting.  This solution worked for me.

  • Community Member Profile Picture
    on at

    I am having the same issue.  We have two Dependent options under the HR menu list - 1 option throws the error module isn't registered and the 2nd option seems to work.  How do I get rid of the "extra" menu option?

  • Shakil khan Profile Picture
    507 on at

    Thanks. It solved our problem.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Season of Giving Solutions is Here!

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans