Announcement

Collapse
No announcement yet.

Feed randomly wrapping quotes on rendered product name when prefix used before token.

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Feed randomly wrapping quotes on rendered product name when prefix used before token.

    Feed rendered value is randomly wrapping by double quotes when one or more spaces and/or characters are used as a prefix before &mvt:record:name; token in Feed > Iterator Template field.

    Note: Using pipe character as delimiter:

    |&mvt:record:name;| renders product name without double quote wrapper (e.g.: A Tale of Two Cities by Charles Dickens).

    However, the following variations would render prefix followed by product name wrapped in double quote wrapper (e.g.:[*]"A Tale of Two Cities by Charles Dickens"):

    Examples:

    1. | &mvt:record:name;| Space after first pipe delimiter followed by product name token renders:
    [ ]"A Tale of Two Cities by Charles Dickens"


    2. |Test &mvt:record:name;| Character(s) and/or space after first pipe delimiter followed by product name token renders:
    [Test ]"A Tale of Two Cities by Charles Dickens"


    We do not know how long this problem has been occurring, but it was not an issue when feed was first created.

    Feeds should always render as-is.

    Example:

    |Test &mvt:record:name;| Should always renders:

    Test A Tale of Two Cities by Charles Dickens


    Could this be a bug?
    Last edited by William Davis; 11-22-23, 11:06 AM.
    Thank you, Bill Davis

    #2
    Wow, nobody? Everyone too busy preparing for Thanksgiving. I really could use some help. Don't know if this is a bug.
    Thank you, Bill Davis

    Comment


      #3
      William Davis are you using the native Marketing Feeds module?

      The native Marketing Feed module will render what is outputted in the template and not automatically add quotes.

      Can you DM me the file that is being exported?
      Nicholas Adkins
      Technical Training Specialist / Miva, Inc.
      [email protected]
      https://www.miva.com/mivalearn

      Comment


        #4
        For those following along the issue ending up being the encoding setting on the feed was set to CSV which caused issues with the data that was outputting. Updating the encoding type to none and wrapping everything in double quotes resolved the issue.
        Nicholas Adkins
        Technical Training Specialist / Miva, Inc.
        [email protected]
        https://www.miva.com/mivalearn

        Comment

        Working...
        X