If we decide to integrate dataflows into our pipelines there could potentially be three different ways to find and replace.
The current way we are using, pipeline built-in processor way, has an issue where non-matches that are also blank cells are filled in with the string "None." Currently the only way to avoid this is to do a second find and replace using find pattern: "None" (without quotes) and leave the replace with field blank.
pipeline processor - has "None" fill issue.
dataflow "find_replace" - unknown whether same issue as pipeline find replace.
custom flow. If all else fails we can write a custom find replace (python re) which seems silly to do but if it works then ....
adyork
commented
5 years ago
If we decide to integrate dataflows into our pipelines there could potentially be three different ways to find and replace.
The current way we are using, pipeline built-in processor way, has an issue where non-matches that are also blank cells are filled in with the string "None." Currently the only way to avoid this is to do a second find and replace using find pattern: "None" (without quotes) and leave the replace with field blank.