Ready for these one, alterego?
So since the colon is an illegal character, the custom SQL query failed since all the text would be cut off after it. Well I was not going to let this stop me. What I discovered is that if you used the standard macro (${Node.CustomProperty}), you could push ANY character you wanted as long as it was in that field for that node. Furthermore, I learned that I could EMBED a macro within a custom SQL query. As such, I created a custom property on the Node called "COLON" and populated it with...you guessed it, a single ":". Once done I could use that field via the macro to inject the previously illegal character into the SQL query and have it execute.
This is the end result of my toil.
${SQL${Node.COLON}Select Platform_Application_Contact FROM APM_ApplicationCustomProperties WHERE ApplicationID = ${ApplicationID}}