Use DFDM on JC_CostCode and confirm the length of the CostCode in the file. In my 2018 install, regardless of segment length selected under JC Options, the CostCode is zero padded on the right to 3 characters for each segment regardless of whether or not the CostCode is numeric or alpha-numeric.

Use DFDM on JC_CostCode and confirm the length of the CostCode in the file. In my 2018 install, regardless of segment length selected under JC Options, the CostCode is zero padded on the right to 3 characters for each segment regardless of whether or not the CostCode is numeric or alpha-numeric.

Also, it seems Job Posting Entry automatically pads zeros on the left for each segment but VI doesn't do any automatic padding and i have been unable to find a method available to do this with the available business objects.

I did however find that VI would not let me use the Next operation on the EntryNo field but i was able to make this work by using the following in a Calculated statement.

""; coBusiness'GetNextEntryNo(Var$)

And... that was it.  THANK YOU!!!!!!!!!!

And ... someone can't add

Was that with or without the GetNextEntry method?

Without - I just assigned them all to the same batch this time.  I'll worry about the Next once we have real data to play with.  I looked through my detail log and yup, I had a lot more red lines than TWO.  Which I should have had, because I had some lines with no jobs.  I'm thinking that if there was no job, it skipped it and did not count it as a fail BUT didn't count it as a skip because I had no skip criteria.  Or something else, who knows - but the count wasn't accurate but the imported records appeared to be doing what they should have been doing.

One caveat of the GetNextEntry method is that because it is a calculated field, VI does not compare its value between the last record and the current record. So make sure you are setting something to a Header field from your source file using the Replace operation.

Using these settings.

With this source.

Gave me these results.

Thanks.  For this particular thing, it's just one big entry anyway, but when I start working on two other upgrades for Job Cost clients, I will need this info...