HOTFIX: Nested Merge Nuances Resolved

A merge with settings that contain other merge codes will no longer be processed until the inner merge codes are processed. Due to this change, any # characters that need to be processed as part of the settings but not part of another merge code must be escaped with a backslash (\).

Ex: ## PRODUCTCUSTOMFIELD[CustomField\#1]##  when you name your custom field Name#1, preferably though, keep special characters out of custom field names.