Skip to main content

Currently I am testing the upgrade of FME Form 2024 (from FME form 2022) for my electrical company. When doing auto-update I found out that my stringcasechanger set on lowercase were updated to UPPERCASE. The same behaviour occurs when you update the transformer manually and choosing the default setting. It would be better if it can take over the old setting. 

Currently I am testing the upgrade of FME Form 2024 (from FME form 2022) for my electrical company. When doing auto-update I found out that my stringcasechanger set on lowercase were updated to UPPERCASE. The same behaviour occurs when you update the transformer manually and choosing the default setting. It would be better if it can take over the old setting. 

Great question.


There must have been a considerable backend change to the transformer for that to happen. I agree it would be best for it to maintain the original, and does seem like a bug (of sorts).

However what it does highlight, is that care needs to be taken when upgrading transformers! I’m a big fan of having the ‘Upgrade All Transformers’ option in newer versions - it saves a lot of time! It’s always important to understand the changes of each transformer and to make sure sufficient post upgrade testing is undertaken to ensure there is no regression.


Hi ​@sijmensp, I totally agree that it shouldn’t be switching cases on you, sorry for the surprise! 

The good news is that it seems to be fixed in FME 2025.0 and newer. Otherwise it looks like it last worked correctly back in FME 2024.0 (build 24202 was what I tested) in case that might be an easier option for you. 

I’ve gone ahead and filed a problem report anyways tracked internally as (FMEFORM-33579) and I’ll update as soon as it has been addressed. Since it works in 2025.0, I can’t guarantee it’ll get a fix for 2024.x but I’ll ask and see (:

 

@hkingsbury there really was! My understanding is that the ‘upgrade transformer’ does it’s best to match the old selection and should try to make the transformer red or ‘incomplete’ if it can’t, but this one seems to have been an escaped bug. This one however wasn’t really noted in the upgrade csv log though so there’s definitely room to improve. 

Thanks ​@sijmensp for raising this!

 


Reply