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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Integration Manager - ...
Microsoft Dynamics GP (Archived)

Integration Manager - ReActivate employees?

(0) ShareShare
ReportReport
Posted on by SaintFrag 207

Despite a field for Inactive in the Payroll Master destination, it seems to not allow an inactive employee to be switched to active.  Forcing the field to false does nothing.  I've scripted it to change the UPR00100 in SQL and get the following:

DOC 33 ERROR: Macro execution error, Dynamics.DEXTERITY_IM_MACRO_INACTIVE_HIT (error DEXTERITY_IM_MACRO_INACTIVE_HIT): MoveTo field 'Employee ID'

Any ideas?

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    L Vail Profile Picture
    L Vail 65,271 on at

    Hi,

    I haven't tried this, but it looks like the macro is trying to land on the field Employee ID and it can't do it. That makes sense because the employee ID field can't be selected after you have saved the employee. Do you get the same results if you pick Update Only as your integration type?

    Kind regards,

    Leslie

  • Suggested answer
    L Vail Profile Picture
    L Vail 65,271 on at

    Another thing,

    Disable the triggers for the HR Solution Series. Go to Tools > Customize>Customization status and disable the HR Solution Series item. Also, if you are using a modified or Alternate Employee window, go back to the original before attempting the integration.

    Kind regards,

    Leslie

  • Suggested answer
    Terry R Heley Profile Picture
    Terry R Heley Microsoft Employee on at

    Make sure you are using the core Microsoft Dynamics GP window and not an alternate.  Usually this type of error is related to a date field.  When you go from active to inactive or vice versa, dates open up and with IM this could cause problems like this date could not be before this date.  Try to key it in and if you get a warning as well or a date needs to be blanked out, that is your issue with IM.  Thanks

    Terry Heley

    Microsoft

  • SaintFrag Profile Picture
    SaintFrag 207 on at

    You may be on to something here.  I'm still looking into this path, but it may be that the Adjusted Hire Date is being changed to a date newer than the Last Day Worked, throwing an error.

  • Verified answer
    SaintFrag Profile Picture
    SaintFrag 207 on at

    Well... I confirmed that it's an issue with both Adjusted Hire Date and Last Day Worked.  Eliminating both of those eliminates the DEXTERITY_IM_MACRO_INACTIVE_HIT error.  So... now to figure out a way around this.  :(

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

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…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Community Member Profile Picture

Community Member 2

#2
mtabor Profile Picture

mtabor 1

#2
Victoria Yudin Profile Picture

Victoria Yudin 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans