Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics GP (Archived)

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

(0) ShareShare
ReportReport
Posted on by Microsoft Employee

Hey everyone,

I've seen a couple other discussion on this issue and didn't see any responses that helped in my situation. We are importing several hundred employees and without fail 1 - 2 always get this error: Macro execution error, Dynamics.DEXTERITY_IM_MACRO_INACTIVE_HIT (error DEXTERITY_IM_MACRO_INACTIVE_HIT): MoveTo field 'Employee ID'.

I have tried the following:

- Recreated the excel file

- Verified that everything is setup correctly in integration manager

- I have disabled the HRM Solution 

- I have tried importing as Update Only instead of Insert and Update

- I have uninstalled and re-installed Integration Manager and GP (it happens on IM across multiple stations so I don't think this is the problem)

- This employee has not been inactivated. He had a hire date of last year and nothing being imported is date related (we manually enter the hire date after import).

- We are not using an alternate window. Default GP windows only.

Here is the interesting thing I discovered. If you remove the imported line above the one that fails. The integration works normally. It isn't the line itself that is failing, but the line above which is causing the next line to fail. I have tested this in several different ways and am positive that one specific lines causes the next one to fail. My question would be, how can that happen and is there a way to resolve it? It doesn't seem to be any different from the others.

*This post is locked for comments

  • Tim Wappat Profile Picture
    Tim Wappat 5,701 on at
    RE: Macro execution error, Dynamics.DEXTERITY_IM_MACRO_INACTIVE_HIT (error DEXTERITY_IM_MACRO_INACTIVE_HIT): MoveTo field 'Employee ID'

    I don't know the specifics of your problem, but I would interpret this as being the previous line(s) are causing the user interface of GP to be in a different state to what the macro is expecting to find, and indeed different to the state the user interface is for the other records. Something is causing the employee id field to be unavailable for those records. (the import is automating the input of the records).

    Try entering some manually and see if you can spot what the difference is. If you import it twice or more into a test company will it always be the same records that get stuck?

    Tim.

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

Congratulations 2024 Spotlight Honorees

Kudos to all of our 2024 community stars! 🎉

Meet the Top 10 leaders for December

Congratulations to our December super stars! 🥳

Start Your Super User Journey Pt 2

Join the ranks of our community heros! 🦹

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,820 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,514 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans