Articles in this section

See more

Select/Cut FIelds - "conflicts"

Avatar
Documentation Team
  • Updated
Follow

Selects rows that share a common value in the Key field, but have non-identical values in at least one other field.

Example 1

conflicts_example_1.png

Example Input 1
dim_A dim_B metric_1
AAA DDD 111
AAA DDD 111
AAA DDD 222
BBB DDD 333
BBB EEE 333
CCC FFF 555
CCC FFF 555
CCC FFF 666
Example Output 1
dim_A dim_B metric_1
AAA DDD 111
AAA DDD 222
BBB DDD 333
BBB EEE 333
CCC FFF 555
CCC FFF 666

 

Example 2

Here, we have excluded "metric_1" from being parsed, meaning that conflicts in that column will not be flagged, only those present in "dim_B".

conflicts_example_2.png

Example Input 2
dim_A dim_B metric_1
AAA DDD 111
AAA DDD 111
AAA DDD 222
BBB DDD 333
BBB EEE 333
CCC FFF 555
CCC FFF 555
CCC FFF 666
Example Output 2
dim_A dim_B metric_1
BBB DDD 333
BBB EEE 333

 

I Ain't Afraid of No Code!

Example 1 
[
   "conflicts",
   {
        "subtable": null,
        "presorted": false,
        "key": [
            "dim_A"
        ],
        "exclude": [],
        "include": [],
        "_comment": null
    }
]

 

Example 2 
[
    "conflicts",
    {
        "subtable": null,
        "presorted": false,
        "key": [
            "dim_A"
        ],
        "exclude": [
            "metric_1"
        ],
        "include": [],
        "_comment": null
    }
]

param str subtable: Name a subtable in which output will be stored (will create subtable where necessary).

param boolean presorted: Default is false.

param list key: The (optional) field key(s).

param str exclude: Fields to be specifically excluded from parsing.

param str include: If present, only those fields listed here will be parsed.

param str missing: Missing values are not considered conflicts. By default, None is treated as the missing value, but can be overridden using the contents of this field.

param str comment: A comment that will appear in the Transformation UI.

Comments

0 comments

Article is closed for comments.