Sitecore EXM - issue on 3.1

-

 ECM 2 Brochure

 I am using EXM 3.1 for a customer and a POC...

However, I do come across quite the number of issues with the EXM module. We all know this module is still subject to some growing pains but as I am curing these, I will list some of the fixes and encountered issues on the blog just to help my colleagues along before another fix on Sitecore is released...

When using the EXM 3.1 I came across the following issue
When creating a new email message I seemed unable to save the item entirely.

I noticed saving was not performed correctly as the title and body fields were not sent out as I tested the email message.

However, when I went into the content editor and navigated to my email in the messages bucket under 'content', I changed the fields manually and tried to save it.
However, on doing so, Sitecore notified me that there were broken links in the value of that (freshly created) mail message.

The problem is on the MessageType field, my message holds the value "Triggered", while in previous versions that was "Trickle" (v3.0) as I saw in a different demo environment we have running.
I then changed my value to "Trickle" and was now able to save without errors from the Content Editor.

When I then went into the EXM interface and opened up my draft message, I got a big server side exception in code on the screen instead of the editing detail sceen.
Only when I changed the value of the MessageType field back to the wrong value did everything revert to normal again, but obviously I was then faced again with the problem of being unable to save...

Sigh :) So onwards to support of Sitecore -> They recognized the bug and the fix is quite simple:

Just rename the following items as mentioned:

Item /sitecore/system/Modules/E-mail Campaign Manager/System/Message Types/Ad-hoc rename to OneTime.
Item /sitecore/system/Modules/E-mail Campaign Manager/System/Message Types/Periodical rename to Subscription.
Item /sitecore/system/Modules/E-mail Campaign Manager/System/Message Types/Trickle rename to Triggered.

No more issues on save from the Content Editor... But some issues exists with updating lists from the ListManager as well as using the EXM interface to save some mail messages. To be continued as Support carries on.

Comments

Post a Comment

Popular posts from this blog

Stupid exception: Device is not ready – System.IOException .net

-
When installing a Sitecore implementation from an development server environment to my laptop I ran into an absolutely stupid error. And it's great to have this kind of errors pop up from time to time even if you have been in the development world for so long and are still unable to fix it immediately. So, what error did I get? Device is not ready – System.IOException .net That is right... Nothing at all related to Sitecore. But then you start to doubt that as my stacktrace showed to Lucene [IOException: The device is not ready. ] System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) +1091 System.IO.Directory.InternalCreateDirectory(String fullPath, String path, Object dirSecurityObj, Boolean checkHost) +1413 System.IO.Directory.InternalCreateDirectoryHelper(String path, Boolean checkHost) +92 Sitecore.IO.FileUtil.EnsureFolder(String path) +128 Sitecore.ContentSearch.LuceneProvider.LuceneIndex.CreateDirectory(String folder) +100 Sitecore.Co
Read more

Date Ranges in C#

-
DateRange utility class Throughout development there are a number of typical things that tend to recur. One of these is implementing a means to display start and end dates for News, Events, Symposiums, Lives etc etc Writing a little class that manages printing these dates seemed like a necessary task that just had to be done in order to make this tedious task be a thing of the past. Therefore I created my "DateRange" class (what's in a name) that should handle this entirely for you. The Idea The intriquities of displaying a datetime range should be an abstraction. You should only need to worry about passing the correct dates (start and end - if applicable) to the Utility class combined with an optional formatting. The class can be entirely configured through use of Enumerations for all the separate settings such as DayFormat etc. An additional class was used to implement this utility, the StringValue attribute class. You can easily use thie class to a
Read more

Sitecore 8.2 in-depth preview + 8.3 update info and Sitecore Ecommerce information

-
Image
During the last Sitecore User group session here in Belgium, Ryan Donovan was featured as the central speaker. The following two topics were on the agenda: Sitecore Commerce An in-depth information on 8.2 and 8.3 I was impressed by the drive behind Ryan and his team(s). It emphasized the drive that is pushing Sitecore forward. Sitecore is putting a lot of effort in producing well hardened and tested product releases that bring new features and rich applications. Sitecore Commerce Previous Sitecore commerce solutions were structured around either SCpbCS and SCpbMD. However, the vNext commerce product has been newly developed from the ground up. Previously, the commerce solution focussed itself around the architecture of Commerce Server to provide and API, manage the products and to derive the entire feature set from. With this Commerce vNext solution, Sitecore has set forward the aspiration to become one of the market leaders in commerce. The fist aim is to focu
Read more