Neophyte
LM Champion
Chiming in here to provide some public clarification as I've done some additional review of the issue and response that you've received from our support team-
It seems that there was some unfortunate misunderstanding when first receiving your ticket.
I did review the engineering plans that were referenced as the "incoming fix" and unfortunately they are unrelated to single or double-quote prematurely exiting strings and throwing parse errors. At this time there are no plans for this to be resolved through LM product changes.
Our suggested workarounds are to use escape characters embedded within the property value itself which should prevent these issues from occurring, as we have seen similar problems with "$" used in properties/credentials in the past. As you noted in the ticket you can also get the data via API and sanitize it by stripping the single or double quotation, etc. when declaring your variables.
