What is your MDM version? If you are able to validate the ORS and use the transformation with your desired value then you can go ahead with the approach.
I'm on 10.3 hf 2.. Yes I know I can go ahead but I do not think it i nice to be forced to hav columns in the BO that need to be null in order to use Concatenation and Data Formats.
I am interested to know how the Cleanse functions are supposed to work since the documention is quite unclear on using Cleanse rules in in BE to View transformations.
Some screenshots of your config would help.
And have you tried the clense function setup in Hub. You can reuse the same in Provisioning as well
THe problem is that without adding a column that contains NULLS in each table i cannot use the Concatinate cleanse function in a BE > VIEW transformation in provisioning tool.
Here is a picture from provisioning:
THe "Null" in string one is a field in the data base that is always null so i have mappet it in the BE and called it null. If i leave "Field Name" empty i do not get anyting when calling on the API if i enter a random string it works but since that string is not in a BE i get an error in validation which mean i cannot propagate from UTV to TEST enviroment.
So, as stated, erlier the workaround is the make sure to have a field in the BE that points to a BE column that always contains a null value, The string in the Value field only gets used when the BE field in "Field Name" is null.
This is not in in accordance to how it works when using the same cleanse function in a mapping since the mapping can use a constant. THe documentation suggest that leaving "Field Name" empty will make the "Value" a constant but, at least, 10.3 hf 2 it does not work like that..
Could it be a bug??
That KB link is exactly what i needed.. To me the manual does not clearly describe the complete process.
To clarify, one needs to create custom cleanse functions in the hub console where you enter the constants and the use those in the the BE to View transformation in Provisioning tool..