There is an unsaved comment in progress. You will lose your changes if you continue. Are you sure you want to reopen the work item?
Join Fields object should accept empty fields
It has been found and experienced that, with the use of the Join Fields object of the Data Manipulation Integration Pack to "Translate International Characters" (i.e. è, ï, ô, ñ, and alike), it is quite useful to add an extra "dummy"
field (field03) beside the two obligatory field01 and field02 parameters in this object and the delimiter of course.
The reason is as follows: Whenever the value or contents for one of the two obligatory fields is missing or empty (or both for whatever reason, which poses another question), the "Join" cannot be executed, for it won't join something with nothing
- i.e. the missing value! By taking up an extra (dummy) field with a value that always exists, either hard coded or from a "get value" like in the "Query XML object, we most often use, the fields specified in the "Join Fields" object
can be joined and will pass on the data to the next objects and eventually to the "Split Fields" object. In that case it doesn't matter if the field is used or not in the work flow thereafter. It is just there to join something with nothing and then
something, just to be able to join!
This is only a workaround and it provided a quick, but sufficient, solution to issues we faced when one of the values of the fields we used (as in default configuration with only two fields and the delimiter) was found empty. The work flow went on and didn't
come to a halt, as it did without the extra field.
It leaves the 'two fields empty' question open though, but I think the answer will be self explanatory, given the scenario described previously.
The question we face here, and like to have answered, is however: Why can't a value be just "Empty" and, for that matter, make it possible join something with nothing? In that case one will be able to use the default configuration, if you do not have
that may text strings that need to be joined to process the text in one go.
The workaround presented here is something that might be added to the User Guide for this IP. With the secription of the object it only states: "• FieldXX – A series of 50 properties to be used as input strings to build the result. Field01 and Field02
are required properties while Field03 through Field50 are optional.", but in the way we are using it, it has been found quite a relief to just add one more and be out of worries. Especially when you suspect one of the fields may be empty.