Hello,
We have come across an issue where by we are not able to save data for a new record entered in employee maintenance.
We can enter in the address for the new employee, select save, close out of the card and go back in and the data entered is missing - the name and id will display fine. What is weird is that we can type the employee number in the field and bring up the employee, enter the data in and save it - close the record and type in the employee number and it will show the address entered but as soon as we try and use the search and select the employee record the address is missing.
We are also unable to enter in a new employee record as it will display the employee # of the above employee except all the data is blank. I am not sure what this issue is and how to resolve it.
Thanks
Was it always doing this or did this just start?
1) Try doing this logged into GP as 'sa'. There may be a table permission issue
2) Run GRANT.SQL
3) Run SQL Profiler for the GP user try to do this and see if there are any anomalies.
4) Has anyone added any triggers to the UPR00102 or UPR00100 table?
Richard E. Wheeler 2013 MVP
MS Dynamics GP Support
www.rbsolutions.com Revered Business Solutions Ballston Lake, NY 518-877-0763 x10
This happened once before but we were able to simply delete the record and the user was able to enter the entire employee record. This time this did not solve the problem.
I have tried doing this as sa but I encounter the same problem. No triggers have been added as far as I know.
Please try running the SQL Profiler when doing this and see what is going on is SQL. You can send me the trace and I will take a look at it.
We are having a similar issue at a client's and they have added FastPath and i believe some triggers to review information when it changes at the UPR00100. Can you elaborate on if the Grant SQL script would help if a trigger has been added? If not, how the trigger can impact the GP table?
GRANT.SQL will set access rights to all objects in the company database to all users in the DYNGRP. Triggers are attached to tables so it will.
We have run the grant scripts and still having a problem. We will be working with Microsoft via a case to research, but can anyone confirm what corrected / caused this issue for the other customer?
Have you tried running SQL Profiler while adding the address? Something is preventing the address from being commited to the database. Does the same thing happen when logged in as 'sa'? Are there any third-party products involved?
Was there resolution to this issue? We are having something like this as well at a client.
We never found out what was causing this but we would notice that the primary address was not in the addess table, even though employee ID seemed fine. User would log out and log back in and it would take. Please let us know if you find the trigger.
I have a client with a similar issue. Please update us if there was ever a resolution found for this.
The latest year-end update fixed this issue. However, you have to use the standard GP window in employee maintenance and not the HRMS Employee maintence window.
We were actually using Binary Stream so we had to use an alternate window.