Skip to main content

Setting a Sitecore Business Rule Operator Programatically

Normally when you create a Sitecore business rule you would define an operator configuration and let the user define the type of operator they want to use. An example of this is the "StringConditionOpertator" (found here /sitecore/system/Settings/Rules/Definitions/String Operators). In a lot of cases, the user would select what type of operation to perform on the value they set. By type I mean things like "equals" or "contains" etc. Below is a list of operators you can use for a string condition.

What if you wanted to create a custom rule that did a string operation but you always wanted it to be the same type of operator? You did not want to, for whatever reason, allow the user to specify how the string should be compared. You can do this by setting the OperatorId to the GUID from the item above. A word a warning here though. Make sure the string stays in the proper casing. If you create a constant for this and/or a GUID and do something like "ToString" the result could cause the casing to change. This is an issue because if you look at the "ConditionUtility" class you will notice all the methods in here setup enums based on a switch, and this switch expects an exact string match.

public static StringConditionOperator GetStringConditionOperatorById(string conditionOperatorId)
      if (string.IsNullOrEmpty(conditionOperatorId))
        return StringConditionOperator.Unknown;
      switch (conditionOperatorId)
        case "{10537C58-1684-4CAB-B4C0-40C10907CE31}":
          return StringConditionOperator.Equals;
        case "{22E1F05F-A17A-4D0C-B376-6F7661500F03}":
          return StringConditionOperator.EndsWith;
        case "{2E67477C-440C-4BCA-A358-3D29AED89F47}":
          return StringConditionOperator.Contains;
        case "{537244C2-3A3F-4B81-A6ED-02AF494C0563}":
          return StringConditionOperator.CaseInsensitivelyEquals;
        case "{6A7294DF-ECAE-4D5F-A8D2-C69CB1161C09}":
          return StringConditionOperator.NotCaseInsensitivelyEquals;
        case "{A6AC5A6B-F409-48B0-ACE7-C3E8C5EC6406}":
          return StringConditionOperator.NotEqual;
        case "{F8641C26-EE27-483C-9FEA-35529ECC8541}":
          return StringConditionOperator.MatchesRegularExpression;
        case "{FDD7C6B1-622A-4362-9CFF-DDE9866C68EA}":
          return StringConditionOperator.StartsWith;
          return StringConditionOperator.Unknown;

As you can see in the above code if for some reason your string casing was not all upper case you will not get a match on the operator. This will cause the "Compare" method to return false when you are expecting a true. This is because the operator ends up getting set to "Unknown".

// Setting the value to this means the operator will always be unknown. 
this.OperatorId = "{10537c58-1684-4cab-b4c0-40c10907ce31}"

// This is all upper case so it finds the correct match. 
this.OperatorId = "{10537C58-1684-4CAB-B4C0-40C10907CE31}"

Even though the Guid is correct it is not in the proper casing. It would be great if Sitecore updated this utility to be case insensitive since really they are after a GUID match and the casing does not matter. A simple "ToUpper" call on the switch would avoid people getting tripped up on this issue.


Popular posts from this blog

Experience Profile Anonymous, Unknown and Known contacts

When you first get started with Sitecore's experience profile the reporting for contacts can cause a little confusion. There are 3 terms that are thrown around, 1) Anonymous 2) Unknown 3) Known. When you read the docs they can bleed into each other a little. First, have a read through the Sitecore tracking documentation to get a feel for what Sitecore is trying to do. There are a couple key things here to first understand: Unless you call " IdentifyAs() " for request the contact is always anonymous.  Tracking of anonymous contacts is off by default.  Even if you call "IdentifyAs()" if you don't set facet values for the contact (like first name and email) the contact will still show up in your experience profile as "unknown" (because it has no facet data to display).  Enabled Anonymous contacts Notice in the picture I have two contacts marked in a red box. Those are my "known" contacts that I called "IdentifyAs"

Excel XIRR and C#

I have spend that last couple days trying to figure out how to run and Excel XIRR function in a C# application. This process has been more painful that I thought it would have been when started. To save others (or myself the pain in the future if I have to do it again) I thought I would right a post about this (as post about XIRR in C# have been hard to come by). Lets start with the easy part first. In order to make this call you need to use the Microsoft.Office.Interop.Excel dll. When you use this dll take note of what version of the dll you are using. If you are using a version less then 12 (at the time of this writing 12 was the highest version) you will not have an XIRR function call. This does not mean you cannot still do XIRR though. As of version 12 (a.k.a Office 2007) the XIRR function is a built in function to Excel. Prior version need an add-in to use this function. Even if you have version 12 of the interop though it does not mean you will be able to use the function. The

Uniting Testing Expression Predicate with Moq

I recently was setting up a repository in a project with an interface on all repositories that took a predicate. As part of this I needed to mock out this call so I could unit test my code. The vast majority of samples out there for mocking an expression predicate just is It.IsAny<> which is not very helpful as it does not test anything other then verify it got a predicate. What if you actually want to test that you got a certain predicate though? It is actually pretty easy to do but not very straight forward. Here is what you do for the It.IsAny<> approach in case someone is looking for that. this .bindingRepository.Setup(c => c.Get(It.IsAny<Expression<Func<UserBinding, bool >>>())) .Returns( new List<UserBinding>() { defaultBinding }.AsQueryable()); This example just says to always return a collection of UserBindings that contain “defaultBinding” (which is an object I setup previously). Here is what it looks like when you want to pass in an exp

Security Config in IIS Express

I have gotten tired of always having to look this up or remember where it is at. That means it is time to post to my blog so I can find it easier and hopefully others can too. If you are having issues with IIS Express authentication errors (like the Unauthorized 401.2 error I always get) here is some help. I can never remember what the last setting was I had IIS Express set to for authorization. To change IIS Express for windows auth or anonymous auth you want to work with the applicationhost.config file. It can be found here …Documents\IISExpress\config. You want to change the settings in the following area of the config file. < authentication > < anonymousAuthentication enabled ="true" userName ="" /> < basicAuthentication enabled ="false" /> < clientCertificateMappingAuthentication enabled ="false" /> < digestAuthentication enabled ="false" />

WPF Localization - RESX Option

About a year ago I was building a WPF project in .Net 3.0 and Visual Studio 2005. I wanted to revisit this subject and see what has changed in .Net 3.5 and Visual Studio 2008. I will make a few of these posts to try and cover all the different options (RESX option, LocBaml option, Resource Dictionary Option). In this blog I will focus on using a resx file to localize an application. To show how the resx option is done I created a WPF form with three labels on it. The first label has is text set inline in XAML, the second has it text set via code behind from the resx file and the third has its text set via XAML accessing the resx file. The first thing that needs to happen to setup a project for localization is a small change to the project file. To make this change you will need to open the project file in notepad (or some other generic editor). In the first PropertyGroup section you need to add the follow XML node <UICulture>en-US</UICulture>. So the project file node w