I spoke with product support this week. Confirmed it was a known issue with no workaround. No commitment to whether or when it will be fixed.
