I am providing you a copy of our scope agreement for your issue.
Customer is getting error message “Error number = 1254 Store Procedure = taPATimeSheetLineInsert Error Description = Employee access does notexist for this project in the PA01408 table
The project number is <NONE>” when sending a time sheet with eConnect.
The scope of this case is to advise customer on the error message “Error number = 1254 Store Procedure = taPATimeSheetLineInsert Error Description = Employee access does notexist for this project in the PA01408 table The project number is <NONE>” when sending a time sheet with eConnect.
You had a phone call with Mike yesterday and are going to first attempt to mark the option Allow Add Access on the fly per below in your test company.
In Dynamics GP, go to Tools > Setup > Project > Timesheets. Click the Options button. The last line in Timesheet Setup Options is “Allow Add Access on the fly”. Be sure this is check marked and please verify you no longer receive the error.
If you do not agree with the scope defined above, or would like to amend it, please let me know as soon as possible. Please let me know if you have any questions or concerns in the meantime. I will follow up with you in a few days if I don’t hear back. Have a great afternoon!
The solution worked – however need to understand the consequence.
1) When the time sheet with none project was sent access to the none project was to be provided to user.
2) The only way access to none project can be provided was to let permission be provided on fly.
3) Because we gave the permission on for access release on fly for none projects, this is having allowing provisioning of access to all projects on the fly which is not what we want.
Can we first enable on the fly – get all user access to Non and then take away on the fly – this should solve the problem for now correct ?
Your analysis is correct and I understand in your 3rd remark that they do not want to allow access to on all projects by using the grant access on the fly. This is actually a known issue (TFS#86337) that is marked to be fixed in the next release of GP16 later this year.