Can you share a bit more information about the file you're importing and the template you're using?

For example:

Are you including Rate Source and Rate Level as part of your template or are you relying on the rules you have set up in Client Information?

If you're using the Rate Source and Rate Level field in your template, what are the values you're assigning to these field?
(Are you able to cut and paste a couple lines from the import file here for us to see?)

Thank you. I am relying on the client as we did in TS 2011.We are not including those fields in the template.

Interesting. That sounds like how I use it.
I have names of timekeepers, clients, and tasks for each slip in my import file, and I rely on the default rate assigned in each client to establish the rate on the slip.

So in your case, after the slip is created what is the Rate Source and Rate Level set to on the slip, versus what you're expecting it to be?

Since TSImport is so customizable, I wonder if you are using Defaults (select Templates > Defaults) or something else that is working different than before.

We are using client override rate rules per Timekeeper set up in the client. When the slip gets imported, the rate is blank if the timekeeper has an override rule set up in the client. If it does not exist there, their level one rate from their timekeeper field is brought into the slip. I am also having similar issues with expense templates but I will create another post for that. Thank you for posting and helping.

Can you give an example of your rate override rules?

For me, I just tried a simple test and it worked.
- I imported a slip for Timekeeper1, Client2, Task3.
- I set up an exception rule for Client2 that was: for Timekeeper1 and Task3, use rate source Client, rate level 8.
That all worked for me.

How are your rate exceptions usually set up?
Do they always include both a Timekeeper and a Task?

They are set up for certain timekeepers. They include all tasks and a set hourly rate for each timekeeper which you the client as a rate source. Our database was converted incrementally from 2011 where all these rules worked. They have always included timekeepers and tasks.

They are set up for certain timekeepers. They include all tasks and a set hourly rate for each timekeeper which you the client as a rate source. Our database was converted incrementally from 2011 where all these rules worked. They have always included timekeepers and tasks.

By the way, the journal says there are no errors during import but I do not think that is entirely accurate.

That's one of the disadvantages of override rate rules. That is standard problem on imports. Override rate rules also don't update like regular rates.

So there are no workarounds? Why would it work in 2011 and not in 2017?