Is there a workaround for connector sources that have spaces in their column names?

We are using Scribe to transfer data...Our source connection has spaces in the columns (i.e. First Name vs. FirstName) and we create our PropertyDefinitions using this name. When we attempt to add a filter to a 'Query' block of this entity, the available field is FirstName with the space trimmed out. When the filter is applied the LookupCondition of the OperationInput object contains the column without the space so when that value is parsed and used against the source system, no results are found as there is no field that matches FirstName (without a space). The source system is not something we control, so my question is there any work around to this or perhaps a way to not have Scribe automatically trim space out of column names. Thank you.

(2) Answers