Answered

Merging Document Template Data

Hi, Support has tried to help but we cannot get the document templates to work.  They will simply not merge the data from Insightly into the Word document.  Has anyone else had this issue and can you help provide some advice please?

We can get email templates to work fine, just not document templates.

Thanks.

1

Comments

12 comments
  • Kevin document templates seem to work fine for us. Two things that are important

    a) You need to use the  field name and not the field label

    b) The field label must be enclosed in two brackets {{label}}

     

    1
    Comment actions Permalink
  • Hi Anton, Thanks for the reply.  I am using the field name and that was confirmed by support.  I did structure the document with 2 brackets, too, and support confirmed that as well.  Support is telling me I have to pay for their professional services to do it because support can't figure out why it is not working.  So, any other advice is much appreciated.  Thanks again.

    0
    Comment actions Permalink
  • Kevin

    If you want you can send me your document in question and I can try and replicate it on my side to determine if we are looking at an issue with the template or your system. You can send it to anton(at)disruptedba.com. 

    0
    Comment actions Permalink
  • Kevin, I have sent you an email but I thought I would post here so that others may learn from it.

    The insightly help documentation is wrong. It states 

    When you add the Field Names to your document, it should be arranged like this: {{Object.Field_name}}

    For example, if you want your contact's first name in the document, add: {{CONTACT.FIRST_NAME}}

    This is wrong, for my version of Insightly at least. The OBJECT must not be included in the reference since this seems to be inferred when you upload and associate the template with a specific object. So {{OBJECT.FIELD_NAME}} would attempt to return {{OBJECT.OBJECT.FIELD_NAME}} i.e. am empty value will return.

    1
    Comment actions Permalink
  • Hello Kevin Pannebecker,

    I see a ticket is currently opened for this topic. The ticket # is 229042. I've gone ahead and looped in our Senior Tech Team on this matter. And, my colleague will follow up on the ticket with the best practices and solution to help clarify things for what you are looking to accomplish. 

    I do appreciate your patience and time. 

    0
    Comment actions Permalink
  • Hello Anton Oosthuizen,

    Thanks for your input and help with this topic as well. It is greatly appreciated. Do you mind sharing the documentation link where you stated the help article is incorrect? 

    0
    Comment actions Permalink
  • Alejandro

    I must say that it is very disappointing that the user has raised this issue on 6FEB2020 already but did not seem to get any joy on something that should have been a 1-minute investigation.

    The reference in question is https://support.insight.ly/hc/en-us/articles/360015708614-How-to-format-and-upload-a-document-template under the Formatting section about halfway down. To be honest there are many such errors in the on-line documentation.

    0
    Comment actions Permalink
  • I absolutely agree with Anton.  It would have been simple for Insightly to check the documentation, but I'm also getting terrible advice from the support department.  The last direct support response was to tell me that document templates are only available in the Enterprise edition, which I know is not the case.  Here's what was sent to me:

    "Correct, these are a portion of the Products, Pricebooks and Quotes features. Please let me know if you'd like me to connect you with one of our colleagues to review your options. Aside from these features, you will also be able to take advantage of Calculated FieldsCustom Apps, and some other really powerful tools. 

    Best, 

    Alex P"

     

    I'm sorry, but support has to do a better job of reading the question and then actually doing some research when trying to help your customers. All they seem to want to do is sell an upgrade.

    0
    Comment actions Permalink
  • Hello Anton Oosthuizen,

    Thanks for your feedback and for helping improve the overall Insightly experience for our users. I have escalated this to further help Kevin Pannebecker. 

    In regards to the post you linked me too, it looks like the documentation is correct. When you add the Field Names to your document it should be arranged like this {{CONTACT.FIRST_NAME}}. 

    Do you have screenshots you are able to provide me showing that this format does not work for you during import? I'd like to take a closer look at this and possibly escalate if the process is different for you. Lastly, may I ask if you are using Insightly's standard fields or custom fields when creating your documentation and if you happen to be using API as well? 

    Thanks for your time. 

    0
    Comment actions Permalink
  • Alejandro

    The test were done using Kevin's template which uses standard fields. I did the same test with my own templates that uses both standard and custom field and using the object name does not work. I am not sure what screenshot will make sense because it is as simple as this:

    {{CONTACT.FIRST_NAME}} - Return empty when doing a merge document.

    {{FIRST_NAME}} - Return the first name of the object to which the template is assigned i.e. Contact.

    This has nothing to do with import or integration. I will test this via postman tomorrow.

    So if the documentation is correct then the system is broken because I can confirm 100% that using the object name as a preamble to the field name does NOT work on my system.

     

     

    0
    Comment actions Permalink
  • I have made a video showing the steps

    https://www.dropbox.com/s/eetraguopptydzx/Document%20merge.mp4?dl=0

    Also, I checked the response from an API call and there is no reference to the object name in the response

     

    0
    Comment actions Permalink
  • Anton is correct.  When you follow the documentation that says use {{contact.first_name}} it returns an empty field.  If you remove the word "contact" from the above , then the system returns the first name of the contact.  The documentation says one thing, but something else entirely is what works.

    Anton was able to point that out to me and since then I have been able to merge documents successfully with the proper data.

     

    0
    Comment actions Permalink

Please sign in to leave a comment.