Handling Empty Attributes in Jama Data Exchange (JDE)

Overview

This article explains how Jama Data Exchange (JDE) handles empty attributes when synchronizing data. Specifically, it addresses whether NULL values or empty strings ("") impact attribute clearing in Jama Connect.

1. Expected Behavior for Empty Attributes in JDE

✔ If an attribute is NULL (completely absent), JDE does NOT clear the attribute in Jama.
✔ If an attribute is an empty string (""), JDE DOES clear the attribute in Jama.

This behavior ensures that existing attribute values are not unintentionally erased when a NULL value is encountered.

2. Why Does JDE Handle NULL and Empty Strings Differently?

• NULL values indicate a missing attribute, not an intentional reset.

• Empty strings ("") represent an explicit change to a blank value.

Since NULL values do not explicitly instruct JDE to update the field, the existing data in Jama remains unchanged.

3. Best Practices for Managing Attribute Clearing in JDE

✅ Use empty strings ("") if the goal is to clear an attribute value in Jama.
✅ Ensure mapping configurations align with intended data handling.
✅ Validate data sources before import to avoid unintended NULL behaviors.
✅ Use scripts or data preprocessing to convert NULL values to empty strings if attribute clearing is required.

4. Conclusion

• NULL attributes do not clear existing values in Jama.

• Empty strings ("") explicitly clear values when imported via JDE.

• Users needing to reset attributes should ensure data sources contain empty strings instead of NULLs.