Description When leveraging forms that use marketing automation with connections such as Salesforce, the forms may appear to be submitting on the front end, but no results are being submitted. If there is a lack of error messages being thrown this may be caused by custom fields within the forms. Steps An upgrade has been released within Episerver that allows for improved messaging in the forms. The site will require EPiServer.ConnectForMarketingAutomation version 5.5.0 and EPiServer.Mar...

Description This article discusses an issue when a form is submitted and a HTTP 500 error is thrown with an additional error as seen below. The required anti-forgery cookie "__RequestVerificationToken" is not present. If the Episerver Forms packages is upgraded to newer versions there will also be a requirement to add anti-forgery token within that file's form element: <%= Html.GenerateAntiForgeryToken(Model) %> When the page with the form would get reloaded it would not refresh the coo...

Description Here are several possible reasons why your forms may be slow when used with Marketing Automation Integration.  Resolution The site is not on a high enough Forms version. It should at least be on the following. EPiServer.ConnectForMarketingAutomation 4.2.0. The below should also be updated.EPiServer.MarketingAutomationIntegration.X (where X is a connector such as Saleforce)Episerver.Marketing.Automation.Forms For Marketo update to at least the following versions(la...