Possible cause: 


Missing paycode


Troubleshooting:

  1. Generate a Time Summary report for the date range you're exporting (most likely previous pay period). Change the "Second Group" property to "None."
  2. Take a look at the hour types included in the report, and take note of whether the numbers appear under Reg, OT1, and/or OT2.
  3. Go to Setup >> Export Definitions, and double-click on the export definition you're using. Look at the hour types which were included in the report, and see if there are codes under the Reg, OT1, and OT2 columns. 


Solution: 


If you see any blanks where you had numbers, you will need to add a code.


Error message:


Csla.DataPortalException: DataPortal.Fetch failed (The given key was not present in the dictionary.)
   at Microsoft.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at Microsoft.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccess(Task task)
   at Csla.DataPortal`1.<BeginFetch>d__1e.MoveNext()


Possible cause:


Changed or deleted Tracking Level


Troubleshooting:


Setup >> Export Definitions, and double-click on the export definition you're using. See if there are any blanks for "Job Cost" fields, in particular between fields that are filled in. I.e., if Job Cost1 and Job Cost3 have Tracking Levels assigned, but Job Cost2 does not. This could mean that a Tracking Level's name was changed, so the Export definition dropped it.


Solution:


Select the Tracking Level whose name was changed, and select the Code to use along with it.