From our customer:
What process in Dynamics GP populates the DateInactivated field in the Users Master table (SY01400) - I’ve tried the following to no avail: Inactivating an active user Activating then inactivating an inactive user I also used GP Power Tools to profile what other tables interacted with the User’s Master table it looked like the Employee card has some interaction but when I tried setting up and inactivating an employee the field was not populated.
Sean,
I did a quick test with FastPath Config AD tool and took a user account that was already inactive. I monitored the SY01400 table and all that got changed after re-activating the user was the "UserStatus" field that switched from 2 to 1.
None of the other fields (like MODIFDT) were altered in the row.. which means that you can safely create a table trigger on UPDATE to set a timestamp on the "DateInactivated" field when the flag switches from 1 to 2 in the userStatus field.
I noticed this is kind of a bug from FP AD as GP updates the MODIFDT when switching the user status, which FP doesn't and I'm going to report them the issue.. Technically this field should always be updated when someone does a save on the record.
That's a great question! I'd have to check as I only have one client that uses FP SSO and haven't validated the way it handles inactive users, but I'd bet that it uses the 'inactive' field the same way, so you would be able to use the trigger technique the same way..
I'll check that and report back.
Great suggestion Beat! It's a shame this bug hasn't been addressed or the column removed because this information would be really helpful for both internal and external audit teams. We're using FastPath Assure to administer add/removing of users, would the trigger suggestion work in this case?
I've seen this bug for a long time now and it was never addressed..
What you could do is create a trigger with a condition that when a user status is set to 'inactivate' in the user maintenance form (which occurs in the SY01400 table), then you put a timestamp to update that field..
Worst case scenario, the trigger gets wiped out on the next update, so make sure you save the code somewhere and document the process.
At this point, there isn't any plans to fix it, probably due to the UserStatus field in that same table will give the same type of information, just not the exact date/time stamp.
Hi Derek -
Is this bug going to be addressed in any upcoming releases?
It should change when you set a user to be inactive in the User Setup window of Dynamics GP, but there's a bug with that not working.
The only change we see is the UserStatus value, in that same SY01400 table, will change to a value of '2' for the inactive user.
Thanks
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.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Mansi Soni as our August 2025 Community…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Sohaib Cheema 665 User Group Leader
Martin Dráb 595 Most Valuable Professional
Yng Lih 558
