Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 9215885
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 18, 20262026-06-18T02:18:06+00:00 2026-06-18T02:18:06+00:00

I have a pdf with several text fields. I have used Echosign’s tutorial on

  • 0

I have a pdf with several text fields. I have used Echosign’s tutorial on creating text tags to create the tags but the Echosign API expert told me that the API method I’ve been told to use (createURLWidget) does not allow data to be prefilled using the prefill suffix.

I am using Ruby to run the methods.

my field name is full_name and I switched the actual document key with a fake one.

params = 
{
  :name => 'Agreement',
  :document_key => '3434hkfhegeg',
  :mime_type => 'application/pdf',
  :fields => 
  {
    :full_name => 'Mary'
  }
}

the text tags that I’ve tried are:

full_name_es_:sender:fullname
full_name_es_:signer
full_name_es_:signer1
full_name_es_:signer2
full_name_es_:sender

Here’s the naming syntax:

<field_name>_es_<:Role><:Field Type>

I’ve tried them Read-only and not.

When I run “ruby create_url_widget.rb” in terminal

This is the relevant part of my response:

<mergeFieldInfo><ns9:MergeFields/><ns9:fieldName>full_name</ns9:fieldName>
<ns9:defaultValue>Mary</ns9:defaultValue></ns9:MergeFields></mergeFieldInfo> 

a URL is also generated with the correct PDF embedded in the page on echosign’s site. However, no text has been places where the full_name field is located. If I have made that text “read-only,” it’s no longer a box to fill-in, if I make it required, the box is red-outlined and when I have a date text tag that I test, it fills it in appropriately so I know it’s doing something.

I have used soupUI to try to change up my code with still no luck.

If anyone needs more code from me, let me know. If anyone has any suggestions, let me know, I am really stuck. I don’t even know for sure if this API method will do this for sure, does anyone know this or should I be using another method?

Thank you for your time in advance!

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-18T02:18:08+00:00Added an answer on June 18, 2026 at 2:18 am

    I solved it! I needed to add a MergeField parameter in addition to the pre-existing mergeFieldInfo and mergeFields. Since each text field needed it’s own MergeField parameter, it had to be placed within the each_pair do loop.

    code in my xml builder:

    if has?( :fields, Hash )
      xml.mergeFieldInfo do
         xml.tag! 'ns9:mergeFields' do
           fields.each_pair do | key, value |
             xml.tag! 'ns9:MergeField' do 
               xml.tag! 'ns9:fieldName', key.to_s
               xml.tag! 'ns9:defaultValue', value.to_s
             end
           end
         end
      end
    end
    

    working text tag example:

    full_name_es_:signer1
    

    what my response looks like:

    <mergeFieldInfo><ns9:mergeFields>
    <ns9:MergeField><ns9:defaultValue>Kristoph</ns9:defaultValue><ns9:fieldName>full_name</ns9:fieldName></ns9:MergeField>
    <ns9:MergeField><ns9:defaultValue>123 Mockingbird Lane</ns9:defaultValue><ns9:fieldName>address_1</ns9:fieldName></ns9:MergeField>
    </ns9:mergeFields></mergeFieldInfo> 
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have to create a pdf report from several classes that are going to
I have a PDF document that has several hundred fields. All of the field
I have PDF documents containing several images/pages of scanned documents. Their (OCR-produced) text content
I have several PDF templates that I would like to load and modify and
I have several PDF files stored in Amazon S3. Each file is associated with
I have several pdf files of some lecture slides. I want to do the
I have the binary for several pdf files stored in a collection of Byte
I have to read a pdf file which contains a table with several columns.
I have tree with several nodes and also create one tree listener for that,now
I have a huge amount of PDF/Word/Excel/etc. files to index (40GB now, but maybe

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.