Questions in topic: "unexpected behaviour" https://knowledge.亚搏在线safe.com/questions/topics/single/69874.html The latest questions for the topic "unexpected behaviour" BulkAttributeRenamer bug with non-ascii attribute names https://knowledge.亚搏在线safe.com/questions/96483/bulkattributerenamer-bug-with-non-ascii-attribute.html

Just upgraded to 2019.0.2.0 and the BulkAttributeRenamer shows some unexpected behaviour,when an attribute's name contains special characters (in my case German umlauts "äöü",but I assume any non-ascii trigger the problem).Problem did NOT occur in 2017.1.2.

The transformer's mode of operation (prefix,regex etc.) doesn't seem to matter: simply adding a prefix is enough to trigger the bug.

Minimal example to reproduce:

  1. Create a feature with an attribute name,e.g."ÄTTRIBUTE" = 1
  2. Add a prefix to it with BulkAttributeRenamer,e.g."FOO_"
  3. Note you now have "FOO_ÄTTRIBUTE" as expected,but with an empty value (instead of =1) AND you still have "ÄTTRIBUTE" carrying the original value (only visible when inspecting all of the feature's attributes,i.e.click the row in inspector)

Can anyone else reproduce this?BulkAttributeRenamerBug.fmw

 bulkattributerenamer special characters unexpected behaviour Tue,06 Aug 2019 16:02:21 GMT schauri Workbench deleting all files (including itself) from FME_MF_DIR https://knowledge.亚搏在线safe.com/questions/84036/workbench-deleting-all-files-including-itself-from.html

Hi,

I have developed a workbench to process some spreadsheet information (as you would).There are no Python callers,system callers or startup/shutdown scripts in the workbench,and never have been.Opens excels,writes excels.

At some point this morning it suddenly decided that when it is run,it deletes all files (not folders) within the folder it is being run from,including itself (as it is open I can hit save after it runs).

I cannot think of anything that should be causing this unexpected behaviour.Has anyone seen anything like this before?

FME 2018.1.0.3 Build 18552 - WIN64 on Windows Server 2008 R2 Enterprise SP1 64bit.

Regards


John

 workbench delete unexpected behaviour Mon,10 Dec 2018 11:57:47 GMT johnt Why is an empty date parameter of different type when running it from FME Server or Workbench? https://knowledge.亚搏在线safe.com/questions/69876/why-is-an-empty-date-parameter-of-different-type-w.html

Hello,

I have a workbench with an optional DATE-parameter.When I use a tester to handle that empty date,I get different 'outcomes' when running from within FME Workbench compared to running it from FME Server.FME Server says an empty date parameter 'HAS A VALUE',but directly in Workbench an empty date parameter is an 'EMPTY STRING'.I use the exact same versions for Server and Desktop (version 2018 build 18301 Win64).

Is this a bug?How can I properly handle empty dates passed via parameters?

Regards,

Frank van Doorne

 unexpected behaviour different variable types handling empty date parameters Tue,08 May 2018 15:02:53 GMT frankvandoorne