Troubleshoot timesheet import errors in the Project Journal

1. A timesheet line fails validation and isn't imported

Problem

You run the import and one or more timesheet lines don't appear in the project journal. An error message shows against the failed lines.

Cause

The import validates each line's mapped job and job task against active Wiise records before it creates a journal line. A line fails when its job or task is missing or inactive. A failed line isn't saved to the journal.

Solution

1. Read the error message against the failed line to identify the problem.
2. Check the mapped Job No. and Job Task No. exist in Wiise and are active.
3. Correct the record or the mapping so the job and task are valid.
4. Retrigger the sync to reprocess the failed line.

2. No default project task mapping is set

Problem

You run the Import Wiise Timesheets on your Project Journal and it fails. You don't see a count of imported timesheets, and the lines don't reach the job journal.

Cause

The import needs a default project task mapping. Without one, the import has nothing to map unmatched lines to, so it can't proceed.

Solution

1. Go to the Timesheet Project Mapping page.
2. Set a default project task mapping.
3. Retrigger the sync.
4. Check the Timesheet Import Log shows the lines as successful, and the lines appear in the project journal.

3. A resource is blocked

Problem

A timesheet for a particular employee doesn't import, and the Timesheet Import Log shows an error for that line.

Cause

The Resource linked to the Project Journal is blocked in Wiise. A blocked resource can't take a posting, so the line can't be created.

Solution

1. Open the Timesheet Import Log and identify the resource named in the error.
2. Check the resource's status in Wiise and unblock it if appropriate.
3. Retrigger the sync to reprocess the line.

4. I can't tell which lines imported and which failed

Problem

After running the import, you're not sure whether every timesheet transferred.

Cause

You haven't checked the batch result. The import reports a summary of successful and failed lines each time it runs.

Solution

1. Read the on-screen summary shown after the transfer. It gives counts of successful and failed lines.
2. Open the import log to see each line's status in detail.
3. For any failed line, follow the matching section above to fix and reprocess.

If the issue persists

If a line keeps failing after you've checked the mapping, the job and task, and the resource, contact Wiise support at support@wiise.com with the Timesheet Import Log.