Hi,

 

 

In FME 2013, you should use the AttributeRemover to make null value.

 

According to this documentation, FME 2014 will support null value. How does FME handle null attribute values?

 

http://fmepedia.safe.com/articles/FAQ/How-does-FME-handle-Null-attribute-values#heading_toc_j_3

 

Takashi

---

Writing "" yields a Null.

 

So test your attribute for null and empty, tester/testfilter has a switch for that in the Operater (click and roll it out)

 

 

 

Alsowhen u have more then 1 stream entering a writer and one has a certain attribute and the other hasnt, the one without will yield null values for those missing attributes.

---

i use tcl [string compare string ""] to test for null or empty values btw

 

 

I understand that writing "" does not yield null to certain filetypes (?)

---

Assume the destination dataset is a database.

 

When the field is a numeric type, writing a string (including "") makes null. Maybe the writer log a warning.

 

But when the field is a character string type, sending "" will write an empty string into the field. It's not null.

 

If you have to write null into a field, you have to remove the attribute (FME 2013).

 

 

Talking about Tcl...

 

The AttributeRemover is generally used, but the TclCaller can be also used to remove attributes. For example, the TclCaller with this script removes "attr1" and "attr2" if it's empty.

 

-----

 

proc setNull {} {

 

  foreach name {attr1 attr2} {

 

    if {pFME_AttributeExists $name]  \\

 

        &&  string compare pFME_GetAttribute $name] ""] == 0} {

 

        FME_UnsetAttributes $name

 

    }

 

  }

 

}

 

-----

 

 

Naturally, the PythonCaller can be also used

---

For 2013 when we read a null value then it won't be an empty value, the attribute will be missing entirely. That's why the Tester lets you test for Missing. Actually if you set it to test for Null, it will just test for missing too.

 

 

Again in 2013 you can't set a null value in an attribute. But if the attribute is missing when it is written then that would probably force a null in a database. For non-databases it would be format dependent (eg in MapInfo I think we write -9999, which is the MapInfo equivalent to Null).

 

 

In 2014 we support nulls properly.  The beta build is online if you want to try it. We'll read a value as null and the Tester will now test for null values (and give a different result to testing for Missing). Many other transformers have been updated to use and account for null values.

 

 

Similarly we'll now write nulls directly to a dataset/database.

 

 

The new NullValueMapper is the transformer that you can use to set features as null or not.

 

 

You can find more info on fmepedia (http://fmepedia.safe.com/articles/FAQ/How-does-FME-handle-Null-attribute-values) and I'll be writing an FME Evangelist blog post shortly to explain all the 2014 updates.

 

 

Hope this helps. I'm really looking forward to 2014 being out there and our customers getting to use the null functionality,

 

 

Regards

 

 

Mark

 

 

Mark Ireland

 

Product Evangelist

 

Safe Software Inc.

---