Missing field in the Email Notification

  • DesktopSigmanet
    Perguntado em 10 de julho de 2023 às 16:38

    Boa tarde,


    meu formulários https://form.jotform.com/DesktopSigmanet/incidentes-gpon não está trazendo todos os campos na resposta do e-mail.

    A configuração dele está correta, por exemplo aqui consta o número do Ticket, porém na resposta não chega.

    Missing field in the Email Notification Image 1 Screenshot 30


    chega assim:


    Missing field in the Email Notification Image 2 Screenshot 41


    poderia verificar, por favor, o problema está ocorrendo desde 06/07/23.


  • Billy Jotform Support
    Respondido em 11 de julho de 2023 às 01:50

    Hi DesktopSigmanet,

    Thank you for reaching out to Jotform Support. Our Portuguese support is currently not available so we'll respond to you in English but if you prefer to receive assistance in your native language, let us know.

    I was able to replicate the issue on a cloned version of your form. To fix this, we need to delete the form's Email Notification and add it back. Let me show you:

    1. In Form Builder, in the orange navigation bar at the top of the page, click on Settings.
    2. Click on Emails in the menu on the left side of the page.
    3. Hover your mouse over the Email Notification and click on the Trash Can icon.
    4. After deleting it, click on Add an Email
    5. Select Email Notification and click on Save.

    Reach out again if you need any other help.

  • DesktopSigmanet
    Respondido em 11 de julho de 2023 às 08:33

    Bom dia,


    Fiz o procedimento informado, e continua com o mesmo erro.


    o número do ticket não aparece


    Missing field in the Email Notification Image 1 Screenshot 20

  • Rayzel Jotform Support
    Respondido em 11 de julho de 2023 às 11:32

    Hi DesktopSigmanet,

    Thanks for reaching out to Jotform Support. I cloned your form and tested it to see if I could replicate the issue, and I saw that your form does not have the field Número do Ticket with the Unique Name {numeroDo} as seen in the current Notification Email. Please see the screenshot below:

    Missing field in the Email Notification Image 1 Screenshot 70

    I tried searching the field and there are no similar labels to Número do Ticket.

    Missing field in the Email Notification Image 2 Screenshot 81

    But, I did see another hidden field labeled Ticket# with the unique name {ticket52}.

    Missing field in the Email Notification Image 3 Screenshot 92

    Is this the ticket number that you want to be presented in the notification email? If so, you can just change the field's unique ID in the notification email from {numeroDo}  to {ticket52}. Let me show you how:

    1. In Form Builder, click on Settings in the orange navigation bar at the top of the page.

    2. Click on Emails on the left menu.

    3. Select the Notification Email and click on the pencil icon to edit.

    Missing field in the Email Notification Image 4 Screenshot 103

    4. Change the unique id of the field Número do Ticket from {numeroDo}  to {ticket52}.

    Missing field in the Email Notification Image 5 Screenshot 114

    That's it. You will be receiving a notification email with whatever field value is set.

    If by any chance, you want to have a random number generated into the form and display it as a ticket number, you may make use of the Unique ID Widget. Here's how:

    1. In Form Builder, click on Add Form Element menu on the left side of the screen.

    2. Go to the Widgets tab and search for Unique ID.

    3. Drag and drop the widget into the form.

    4. Set the widget's details on the Widget Settings panel on the right.

    Missing field in the Email Notification Image 6 Screenshot 125

    5. Next, to add it to the form, you can delete the notification email and create a new one as suggested by my colleague, Billy or you can just edit the unique ID as per my instructions above.

    Give it a try and let us know if you need any help.

  • DesktopSigmanet
    Respondido em 17 de julho de 2023 às 11:18

    Boa tarde,

    O problema era os acentos na identificação dos campos, depois que retirei resolveu .