Good morning,
We’re looking for information on these Part fields which appear very similar.
For example, Part.AttHeat is on the Part Entry UI but we don’t see where Part.LotHeat gets used. Part.LotHeat appears to be false in all cases, irrespective of the value of Part.AttHeat.
Anyone able to shed some light on these? Thanks very much.
These lot-releated fields in Part turn on and off the collection of the selected items during Lot transactions.
The actual values will be stored in PartLot record, one for each lot. Look in the Lot command to see the values.
@Mark_Wonsil , thanks, I appreciate the reply.
We’re comfortable with Lot Tracking in general, we lot-track most of our parts. I’ll be more specific.
We use Part.AttHeat = “M” on many parts.
What does Part.LotHeat = true do?
You know, that’s a damn good question. I’m guessing those are the previous fields since they were boolean/checkboxes but when they added Manadory/Tracked/Not Tracked, they needed to add new ones. 
Good guess @Mark_Wonsil , I think you are probably correct. I would check 8, but they did not exist yet!
It appears that Part.LotHeat is always false in our database, irrespective of the value of Part.AttHeat.
I’m going to run with the assumption that the boolean fields are vestigial. I’ll post back if I run in to any issues.
Thanks.
