You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dynamic templates: {{Subject}} not printed into my template using SendGridMessage.SetSubject("a subject") or SendGridMessage.SetGlobalSubject("a subject")#1212
Open
MarGraz opened this issue
Sep 12, 2024
· 0 comments
I'm using SendGrid version 9.29.3 and I noticed that when I use SendGridMessage.SetSubject("my subject title") or SendGridMessage.SetGlobalSubject("another subject"), neither is rendered in my template using the {{Subject}} placeholder.
I was only able to display the subject when I added it into myDynamicTemplateData, which I passed to SendGridMessage.SetTemplateData(myDynamicTemplateData);, using a lowercase property like "subject". In my SendGrid template, I then used it as {{subject}}.
Please fix this bug, as I spent several hours trying to figure out what was wrong.
Thank you 😊
The text was updated successfully, but these errors were encountered:
MarGraz
changed the title
Dynamic templates: SendGridMessage.SetSubject("a subject") and SendGridMessage.SetGlobalSubject("a subject") are not working into the template using placeholder {{Subject}}
Dynamic templates: {{Subject}} not printed into my template using SendGridMessage.SetSubject("a subject") or SendGridMessage.SetGlobalSubject("a subject")Sep 12, 2024
Hi,
I'm using SendGrid version 9.29.3 and I noticed that when I use
SendGridMessage.SetSubject("my subject title")
orSendGridMessage.SetGlobalSubject("another subject")
, neither is rendered in my template using the{{Subject}}
placeholder.I was only able to display the subject when I added it into
myDynamicTemplateData
, which I passed toSendGridMessage.SetTemplateData(myDynamicTemplateData);
, using a lowercase property like"subject"
. In my SendGrid template, I then used it as{{subject}}
.Please fix this bug, as I spent several hours trying to figure out what was wrong.
Thank you 😊
The text was updated successfully, but these errors were encountered: