Issues Importing Maps in Data Exchange/Management with Comma in Source Value

Summary: We have a number of maps that utilize commas within their Source Value definition. This has never presented as a problem, as wrapping them in double-quotes during an Import historically alleviated any issues. Now those same maps when imported are being completely ignored during the Import process with no errors/warnings from either Data Exchange or Data Management.

The below is the test file. Lines 2-3 both have commas, both wrapped in double-quotes.

After import using Replace, No Validate, Online as options for Import process, the following is visible in the mapping definition. The import process completely ignored lines 2 and 3; both mappings with commas present.