Hi Arline,

Unsure from this height what's happening. Is there a field named value in the previous that is not being imported?

Also were these jobs upgraded from an old IMan version to v4?

Q: Is there a field named value in the previous that is not being imported?

A: No, this is just renaming an existing field "DTGSEASON." Just double-checked and there is no field named 'VALUE' in any previous transform.

Q: Also were these jobs upgraded from an old IMan version to v4?

A: No

OK thanks, can I assume the value follows through if the field is not renamed?

Also does the value appear in subsequent transforms?

You may also want to clear the IMan cache c:\Iman\cache

Q: can I assume the value follows through if the field is not renamed?

A: Yes, before I renamed it, the value was coming through.

Q: Also does the value appear in subsequent transforms?

A: Well, the field DTGSEASON that was renamed VALUE does appear in the subsequent transform (a DB update transform) but it's got a null value. So the field appears but the value is not there. 

How do I clear the IMan cache? I see multiple files in that directory - some are .cache and others are .dat. Am I to delete any .cache files associated with the entire IMAN job?

(FYI I tried searching for the answer, got this page, but it returns a 404 error:)

Just FYI:

I deleted the .cache files to no avail. Interestingly, when I deleted & re-built the flatten transform, I got the exact same results. I wonder if it's an issue using the field name "VALUE". The reason I named it that way was to successfully update a Sage 300 ERP Order Header optional field using DB update. Anyway, I ended up keeping the field name the same in the flatten transform; adding a map transform where I renamed it to VALUE, and then the DB update transform follows. It's working now with this approach.