Skip to main content
R
ricko89170530
Participant
August 25, 2020
Answered

How to add custom fields in Mega Sign?

  • August 25, 2020
  • 3 replies
  • 3332 views

Question - How can I incorporate custom fields into a Mega Sign workflow? For example, the EXAMPLE CSV file has fields "Phone" and "zipcode_es_signer" when you download the example CSV file. How would one drop those custom fields into the PDF as part of the Mega Sign workflow? The fields never appear when I try to configure the document for signature blocks, names, etc. locations after uploading into the Mega Sign workflow.

 

Thanks!

-Rick

    This topic has been closed for replies.
    Correct answer chrisw53748869

    The steps in this article explain how to add custom text tags.

    Adobe Sign Text Tag Guide

    https://helpx.adobe.com/sign/using/text-tag.html

    3 replies

    C
    chrisw53748869Correct answer
    Participant
    March 14, 2022

    The steps in this article explain how to add custom text tags.

    Adobe Sign Text Tag Guide

    https://helpx.adobe.com/sign/using/text-tag.html

    D
    defaulttplhf2aa15oc
    Participant
    May 14, 2021

    I found this helpful  https://helpx.adobe.com/sign/using/mega-sign.html

    T
    timv65744291
    Participant
    October 14, 2020

    Did you ever figure this out? I'm running into the same problem...

    T
    timv65744291
    Participant
    October 14, 2020

    I figured this out...

    You need to edit the PDF beforehand and put in a prefilled field (Field Type: Text, Participant Role: Prefille, Read Only) with matching names between the field name end the column header in the CSV file.

    R
    ricko89170530Author
    Participant
    October 14, 2020

    Yup - that's how I did it. Though you -can- add those fields in after-the-fact, in the Sign fields setup. You can manually add a Text data field, and if you give it the exact same name as the header in the mega sign merge file, it will pre-populate it. Takes a few test runs to figure it out. And the UI is... a bit clunky. This should be a lot easier to do, and docs should have more examples.

    -Rick

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices