We have a user ID field that sometimes includes leading zeroes. In MIIS/ILM, this imported just fine, retaining the leading zeroes on import. In FIM, the leading zeroes are dropped. I note that the SQL Server data type is nvarchar, which should support it fine. Has the sync engine changed in a way that causes these leading zeroes to be dropped? What can be done to retain the leading zeroes?

Nevermind, this was a PEBKAC error...