In this blog, we will discuss how we can create Global Email Template programmatically.
\nEmail templates contain prefilled data that you specify, so you don\u2019t have to re-enter the same information for each article.<\/p>\n
To create an Email template for a specific entity (for Contact) we use logical name of the Entity \u201ctemplatetypecode=contact\u201d.<\/em><\/p>\n Similarly, to create a Global Email template we do not have any specific entity. Therefore, In order to create a record of the Global Email template, Microsoft has provided a solution, i.e. set the field value of the \u201ctemplatetypecode = systemuser\u201d<\/em> as shown in the examples below:<\/p>\n \/\/This function is used to create a Global Email Template in Dynamics 365 CRM<\/p>\n function createEmailTemplate() {<\/p>\n try {<\/p>\n var objEmailTemp = new Object();<\/p>\n objEmailTemp.title = “Created Email Template using JS”; \/\/Title<\/p>\n objEmailTemp.templatetypecode = “systemuser”; \/\/Global<\/p>\n \/*We can use the Entity logical name to create a template for a specific entity*\/<\/p>\n objEmailTemp.languagecode = 1033; \/\/Language<\/p>\n objEmailTemp.subjectpresentationxml = “<template><text><![CDATA[Test Subject]]><\/text><\/template>”; \/\/Subject<\/p>\n objEmailTemp.presentationxml = “<template><text><![CDATA[Body of the Template]]><\/text><\/template>”; \/\/Body<\/p>\n objEmailTemp.ispersonal = true;<\/p>\n \/\/ Create account record<\/p>\n Xrm.WebApi.createRecord(“template”, objEmailTemp).then(<\/p>\n function success(result) {<\/p>\n \/\/ Perform operations on record creation<\/p>\n showMessage(“template created with ID: ” + result.id);<\/p>\n },<\/p>\n function (error) {<\/p>\n \/\/ Handle error conditions<\/p>\n showMessage(error.message);<\/p>\n }<\/p>\n );<\/p>\n } catch (error) {<\/p>\n showMessage(error.message);<\/p>\n }<\/p>\n }<\/p>\n \/\/This function is used to show the Message<\/p>\n function showMessage(message) {<\/p>\n try {<\/p>\n var alertStrings = { confirmButtonLabel: “OK”, text: message };<\/p>\n var alertOptions = { height: 120, width: 260 };<\/p>\n Xrm.Navigation.openAlertDialog(alertStrings, alertOptions).then(function success(result) {<\/p>\n console.log(success);<\/p>\n }, function (error) {<\/p>\n console.log(error);<\/p>\n });<\/p>\n }<\/p>\n catch (ex) {<\/p>\n }<\/p>\n }<\/p>\n \/\/\/ <summary><\/p>\n \/\/\/ This method is used to create an Email Template in Dynamics 365 CRM of type “Global”<\/p>\n \/\/\/ <\/summary><\/p>\n public void CreateEmailTemplate()<\/p>\n {<\/p>\n try<\/p>\n {<\/p>\n \/\/Entity object<\/p>\n Entity entEmailTemplate = new Entity(“template”);<\/p>\n entEmailTemplate[“title”] = “Created Template using C#”;\/\/title<\/p>\n entEmailTemplate[“templatetypecode”] = “systemuser”;\/\/Global<\/p>\n entEmailTemplate[“languagecode”] = 1033;\/\/Language = English<\/p>\n entEmailTemplate[“presentationxml”] = “<template><text><![CDATA[Body of the Template]]><\/text><\/template>”;\/\/Body of the email<\/p>\n entEmailTemplate[“subjectpresentationxml”] = “<template><text><![CDATA[Test Subject]]><\/text><\/template>”;\/\/Subject of the email<\/p>\n entEmailTemplate[“ispersonal”] = true;\/\/True = Individual and False = Organization<\/p>\n \/\/Create the Record<\/p>\n Service.Create(entEmailTemplate);<\/p>\n }<\/p>\n catch (Exception ex)<\/p>\n {<\/p>\n throw new Exception(ex.Message);<\/p>\n }<\/p>\n }<\/p>\n Using the above custom code we can create the Global Email Template record in Dynamics 365 CRM.<\/p>\n Note<\/strong>: We cannot create Email templates using OOB Workflows or Actions.<\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":" Introduction In this blog, we will discuss how we can create Global Email Template programmatically. Email templates contain prefilled data that you specify, so you don\u2019t have to re-enter the same information for each article. To create an Email template for a specific entity (for Contact) we use logical name of the Entity \u201ctemplatetypecode=contact\u201d. Similarly,\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":19167,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[13,16,18,19],"tags":[545],"class_list":["post-19165","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-customizations","category-dynamics-365","category-dynamics-365-v9-2","category-dynamics-crm","tag-dynamics-365-crm"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/19165","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=19165"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/19165\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media\/19167"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=19165"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=19165"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=19165"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Using XRM.WebAPI<\/h2>\n
Using C# code<\/h2>\n
Conclusion<\/h2>\n