Weekly Time Crew Entry - Union Local value

​@frocido - I typically start with the help for that particular field.  For that screen, the help is pretty sparse. For the regular time entries screen, it either defaults to the employee or blank in all cases. I think what’s happening here is that the Crew default Union Local is defaulted for the first employee added, then the Union Local of the first employee added to the crew for all subsequent lines.  This makes sense if Acumatica assumes that the crew is working under a single union.

@frocido The only source for that column is the Union Local on the employee record. When a line gets its employee, the system copies the employee's Union Local to the line, as long as the project on the line either has no union locals listed or lists that one. If the project lists union locals and the employee's isn't among them, the line stays blank. There isn't a crew or workgroup level union setting behind that screen.

I ran your steps on 2026 R1. First line: blank until I picked an employee, then it filled with that employee's union. Second line: blank before an employee, even with a union employee on the line above, and it followed whichever employee I picked.

So what you expect is how it behaves for me. If yours fills in before an employee is selected, check whether the value matches the employee on the line above. If it does, that's worth a support case with your build number.

​@Steve Milner  Our version is 2025 R2, and we are seeing different behavior. When a new line is added, the Union Local field is automatically populated before an employee is selected, and the value is not always the same from one line to the next.

For reference, the project does not have any Union Locals defined. 

Based on your testing in 2026 R1, where the Union Local remains blank until an employee is selected, I am assuming this issue may have been fixed in that release.

​@nickcerri32  

For my case, the first line's Union Local remains blank and does not default to any value. However, when additional lines are added, the Union Local field is automatically populated before an employee is selected.

What's more unusual is that when multiple lines are entered, the Union Local does not consistently use the same value. Instead, it defaults to different Union Local values across the lines and does not retain the value from the first employee entered.

@frocido Good call. I fired up a 2025 R2 instance (25.200.0248) and got exactly what you're seeing.

First line stays blank, even after I pick an employee who has a Union Local. Every line after that comes in already filled, and what it's filled with is the union of whoever is on the line you had selected when you hit Add Row. That's why yours jumps around. And once it's there it sticks. I put a non-union guy on a line that came in with a union and it didn't clear.

Same steps on 2026 R1 (26.101.0225) and each line just follows its own employee, so it did get fixed somewhere in between. I couldn't find it in the 2026 R1 release notes, so I don't have a fix number for you. Support should be able to tell you which build, and whether there's a 2025 R2 update that has it.

Until then I'd eyeball that column on every line before releasing the time.

​@Steve Milner  Thank you for taking the time to test this and for confirming how the functionality behaves in 2025 R2. I appreciate your help and the additional details you provided.