Activity Slips - Import Error - Warning 600: Payroll category requires a non-zero unit; ignored.

Hi CloudMindAcc , appreciate the shout-out, but I don't know this one! The help documentation suggests that units allow 2 decimal places, so you could try writing 2.50 instead of 2.5. 

Can you attach the source text file with a few rows including the one that gives the warning?

Hi CloudMindAcc , Mike_James 

This is a known issue in the system whereby activities which are set up with the type Hourly, are imported with a Warning : Payroll category requires a non-zero unit; ignored, if decimals are entered in the Payroll category field.

If a whole number is entered, the import works fine, however, this has been raised with the product development team already for a permanent fix. 

In the meantime, if the activities are set up as Non Hourly and hours are written in the Unit field, they can be imported successfully without any warnings or errors. 

Thank you for that feedback again Paul_SHF . I will let the development team know of this issue as well. 

Thanks Komal_S , I presume you mean "if decimals are entered in the Unit field"

Hi Mike_James 

Sorry, my bad. Yes, I meant the Units field. 

Hi Komal_S 

Thank you for rasing this to the product development team already for a permanent fix. Given this is a known issue and the fact that you can manually enter a decimal of an hour ie 1.5 and it will accept for Payroll however when you attempt an import with a decimal Warning : Payroll category requires a non-zero unit; ignored, appears! Fixing this anomaly so that Activity Slips Import "Units" field to be able to accept decimal would be fantastic.  

With respect to the interim /workaround solution  "activities are set up as Non Hourly and hours are written in the Unit field" this doesnt work as imports reslts in Error -5051: ActivitySlip_ActivityIsNotHourly.

Hi Paul_SHF 

For the import to work, you will have to ensure that the activity itself is setup as non-hourly first by going to Lists>>Activities. Can you please change that and confirm if it still doesn't work. 

Hi Komal_S

I can confrim I changed activities to non-hourly and tested it before my response yesterday.

Dev Team fixing the Units to accept a decimal solves everything! - Just saying and I know you are aware :-)