Export conditions in Eofferix for tables, JSON, and XML

Export conditions decide whether the selected part of the data gets into the final export.

For example, you can skip an empty description, remove an empty XML tag, or skip a table row without an SKU.

Where to open export conditions

Where you work	How to open it	What is checked
Table	Open the settings of the required column.	The condition checks the value in the row. If the check fails, the row is not exported.
JSON	Click the required key or value in the JSON editor.	On a JSON value, For the node omits the key and keeps the object, while For the whole element removes the containing array object.
XML	Click the required tag, attribute, or value in the XML editor.	On an XML leaf value, For the node leaves an empty tag, while For the whole element removes only the selected leaf; the parent record remains. To remove a whole repeating record, configure the condition on its record node and select a child field as the checked source.

What to choose: “For the node” or “For the whole element”

In JSON and XML, the export conditions block has a scope choice. It defines which part of the data is removed from the export when the condition fails.

On a JSON value, For the node omits that key and keeps the object. For the whole element removes the containing array object.
On an XML leaf value, For the node omits the text but leaves an empty tag. For the whole element removes that leaf only; the parent record remains.
To exclude a whole JSON/XML record, configure the condition on its repeating record node, choose a child field as the checked source, then select Before transformations and For the whole element.
Tables do not show a scope selector: a failed export condition excludes the whole row.

For the node and For the whole element scope choice in XML export conditions — In XML, the scope is relative to the selected node. A condition on a leaf value does not remove the parent record.

What a condition contains

Setting	Meaning
Checked source	The current value, another XML/JSON node, a neighboring table column, or a system value.
Timing	Before transformations or After transformations. For a recipe that must behave the same in tables, JSON, and XML, use Before transformations and check the source value. Use After transformations only in a format-specific profile after checking both preview and result.
Operator	Empty, Not empty, Equals, Greater than, Contains substring, Regular expression, and other checks.

Result examples

JSON: remove an empty description key

The condition is set in the description value settings: Current value, Before transformations, Not empty, For the node. The value is empty, so the description key is omitted and the product object remains.

Input

JSON

{
  "sku": "SKU-1001",
  "name": "Jacket",
  "description": ""
}

Export result

JSON

{
  "sku": "SKU-1001",
  "name": "Jacket"
}

XML: keep the record and leave an empty description tag

The condition is set on the leaf value inside description: Current value, Before transformations, Not empty, For the node. The value is omitted, but the XML serializer keeps an empty <description> tag and the parent offer remains.

Input

XML

<?xml version="1.0" encoding="UTF-8"?>
<offer>
  <sku>SKU-1001</sku>
  <name>Jacket</name>
  <description></description>
</offer>

Export result

XML

<?xml version="1.0" encoding="UTF-8"?>
<offer>
  <sku>SKU-1001</sku>
  <name>Jacket</name>
  <description></description>
</offer>

Table: skip a row with an empty required field

In the sku column settings, select Not empty. If sku is empty, the whole row is not exported.

sku	name	Export result
`SKU-1001`	Jacket	The row is exported.
	No SKU item	The row is not exported.

How this differs from an action in transformations

Transformation rules include an Export control group. It is an action inside the transformation chain of the selected value, not a structural filter for a row, JSON node, or XML element.

Do not export field is a transformation action. It clears only the current final value, ends the rule chain for that value, and does not delete the row or parent JSON/XML element.
Skip skips the current transformation rule and continues with the next rules.
For a cross-format whole-record filter, use Export conditions. Tables have no scope switch: a failed condition excludes the row. In JSON/XML, open the repeating record node (for example item), select a child field as the checked source, and choose Before transformations and For the whole element.

Which mechanism to use

Task	Use this
Remove an empty key from JSON	Export condition on that JSON value: Not empty and For the node.
Remove an empty tag from XML	Export condition on the XML leaf value: Not empty and For the whole element. Only the selected tag is removed; the parent record remains.
Skip a table row with an empty SKU	Export condition in the `sku` column settings: Not empty.
Only change a field value	A rule in Transformations.