Does your solution have to be in BO or do you have access to the underlying database?
If you have DB access I’d put a view between the table and BO and you can do some pretty swell tricks in that layer. Adding hidden column that include a type conversion lets you avoid the nasty BO Universe syntax.
As a general note, I always try to use a view between the data source and the tool. Even if there is no additional logic in it. It is a huge help if for political reasons the BO developers are not allowed to be in the database. You can usually get a separate schema set up where you are permitted to create views (after all you won’t be messing with data) and then you can do anything you need in that location.