Currently if a blob storage data source is consumed and mapped to interactions/profiles, if there is an error with pulling and parsing data due to type/type casting errors, nothing is exposed to the user. From the users point of view nothing appears to be wrong then, expect that no data is being pulled into the interactions/profiles.3 votes
Currently you would have to define any currency type field as a double or a string if they are prefixed with a currency symbol already. A currency type will allow for better handling of these issues.2 votes
- Don't see your idea?