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 to Activat...
Microsoft Dynamics GP (Archived)

Integration to Activate Previously Inactive Employees in US Payroll

(0) ShareShare
ReportReport
Posted on by David Layten 1,819

Hello,

I am trying to create an Integration for a Customer to re-activate employees in GP that were previously made Inactive. These employees that have be re-hired are coming over from a file from PeopleMatter. I have created two integrations:

1. For New Hires

2. For Re-hires

The New employee integration works fine. The Rehired Integration does not want to work correctly. Here are some of the particular items I have tried.

1. In the Destination Mapping set the INACTIVE Line to "FALSE" to re-activate the employee.

2. Update the existing Address ID. It seems that only way to update the Address is to create a new Address ID.

3. Use the Employee Reactivation Option on the Integration. Only needing to re-activate Pay Codes, State and Local Taxes.

Either the employee records do not become active or it opens up windows after the integration is complete.

I am looking for any advice from anyone who has attempted this before.

We are on GP 2013 R2.

Thanks,

David

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Bill Campbell Profile Picture
    Bill Campbell 12 on at

    David, I am sure that this is too basic to the matter, but I am prone to ask the easy first.

    Can you confirm that the Re-Hire integration has the option UPDATE and INSERT selected.

    The reason I ask this, is that the only way your comment in point 2 makes sense.  Your correct the only way to update an address to ADD a new one - holds only if the options are not set to allow UPDATES.

    Let me know if this helps.

  • David Layten Profile Picture
    David Layten 1,819 on at

    Bill,

    Thanks for the response and sorry that it has taken me so long to respond. Yes, I do have the integration set to Insert and Update.

    The customer is in a hurry to get this working so I might be starting a case with Microsoft Technical Support on this. I will update this question with whatever answer that they might provide.

    In the meantime, any suggestions that anyone has will be greatly appreciated.

    David

  • SaintFrag Profile Picture
    SaintFrag 207 on at

    Did you ever get anywhere with activating the inactive employees through Integration Manager?

  • SaintFrag Profile Picture
    SaintFrag 207 on at

    I tried this method, but on some of my employees I get the following error:  DOC 33 ERROR: Macro execution error, Dynamics.DEXTERITY_IM_MACRO_INACTIVE_HIT (error DEXTERITY_IM_MACRO_INACTIVE_HIT): MoveTo field 'Employee ID'

    Anyway, in my Inactive field I use the following script:

    if SourceFields("Status") = "1" then
	'Open a connection to the SQL database
	Set MyCon = CreateObject("ADODB.Connection")
	MyCon.ConnectionString = "database=" & GPConnection.GPConnInterCompanyID
	GPConnection.Open(MyCon)

	'Create the SQL query and execute
	sSQL = "UPDATE UPR00100 set INACTIVE=0 WHERE EMPLOYID='"
	sSQL = sSQL &  DestinationFields("Employee ID") & "'"
	'msgbox(sSQL)
	MyCon.Execute(sSQL)

	'Close connection when finished
	Call Mycon.Close

	'Release the object
	Set MyCon = Nothing
end if

    In my instance, I'm pulling in from another database, hence the SourceFields 'if' statement.  Still banging my head against that error.

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

    Hi,

    I did this without any problems. Have you tried disabling the add-on modules like the HR Series? That has worked for me in past integrations for payroll.

    Kind regards,

    Leslie

  • SaintFrag Profile Picture
    SaintFrag 207 on at

    Yes, with no change.

  • David Layten Profile Picture
    David Layten 1,819 on at

    Sorry for my delay in responding to this. I got Microsoft Support to help with this issue and did get it to work somewhat.

    The client determined that in their case, it took less time for them to re-activate the employee manually then running the integration and then verifying the data.

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

    Hi David,

    What did Microsoft think the problem was? Would you share with us what they did to get it to work somewhat?

    Kind regards,

    Leslie

  • Suggested answer
    David Layten Profile Picture
    David Layten 1,819 on at

    Leslie,

    Here is what Microsoft replied in the case. The issue was mainly with the dates that I was trying to use:

    "I got a chance to look at your file today.  As I indicated prior, typically this error has to do with dates.

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

    When I received the integration, there was a script attached to it, so I removed that to rule anything out.

    Then I changed these areas below, the 1900 will not work, nor will 00/00/0000 as it wants the date last day worked to be 0’d out or AFTER the hire date

    By stating system date, then it always is after, which then you can run a script to zero it out if you want.

    The issue appears to be with the fact that when you activate an employee record, that was previously inactive, the last day worked field is not cleared.  

    If you try to populate the last day worked field, via Integration Manager, with 00/00/0000 or 01/01/1900, etc. you will receive errors  that state the last day worked cannot be less than the birthdate for the employee.  

    Even though the integration runs without error, the employees in question are not updated because of the error that is occurring behind the scenes.

    What you could do is set these fields to Use System Date. That is typically want a customer may do in this scenario."

    As I stated in my earlier response to this case, my customer determined that it took less time to re-activate the employee than run an integration to do it. Also, in this customer's case, it was not just that they simply hired them back. They could be working at a different location, have new state and local tax codes and also the Employee Class could change.

    Hope this information helps someone.

    David

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

    Thank you for sharing David. This will definitely help someone out!

    Kind regards,

    Leslie

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
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans