I'm using a workspace that utilizes the UpdateDetector and the fme_db_operation INSERT, UPDATE, and DELETE functions to synchronize a table called Topology. In the Topology table there is a field called PASSWORDX that contains encrypted characters like "...." . When the database was first empty, the INSERT went fine, but a few weeks later when the password changed from "...." to "/_,|", FME says that the updates were written to the table, but actually were not.
I was able to run this script in SQL Server Manager and successfully update the table:
UPDATE dbo.TOPOLOGY
set PASSWORDX='/_,|'
where NOINS = '0EB2996'
GO
Could this be something with the FME UpdateDetector transformer? I'm using FME Desktop 2017, latest build on a Windows 10 machine.
