May 23, 2012

I wanted an incrementing Assembly version, but I didn’t want to have to do it manually. Some quick Googling and I found this nice solution:

I’ve been using SubWCRev that’s in the TortoiseSvn installation (I think it’s downloadable seperately too).
First i create a “template”-file for the AssemblyInfo.cs called AssemblyInfo.cs.in
This is created as a copy of the exisiting one.
Then replace the parts you want changed with SubWCRev placeholders like this:
[assembly: AssemblyVersion(“1.2.3.$WCREV$”)]
Then create a PreBuildEvent to run SubWCRev with appropriate parameters:
SubWCRev <wcpath> AssemblyInfo.cs.in AssemblyInfo.cs
Done.

May 9, 2012

Unica’s Customer Insight product can quickly generate an EasySet of data allowing a user to start mining their customer base. The problem comes into play when the out of box configuration doesn’t match what you want to display.

By default, CustomerInsight will take all numeric data types from the source table and create “bins”. The “bins” created sometimes do not align with the desired buckets that a business may be accustomed to. Follow this process to create your own bins.

Scenario

We desire to set the bins for an attribute into 100 point increments to the following values:

1 – 99

100 – 199

200 – 299

300 – 399

400 – 499

…

900 – 1000

XML Modifications

File: cadimensions.xml

This file defines the bucket values that will be displayed. Within the existing <defaults><fields> tags, we will insert the following:

1:<fieldname="ABILITY_TO_PAY">

2:<dimensionname="ability_to_pay0"dimdisplay="Ability To Pay"singlefilterdisplay="Ability To Pay"multiplefilterdisplay="Ability To Pay"onlyincludedisplay="Ability To Pay"selectadisplay="%NTR_SELECTA_VALUE%"variable="ability_to_pay0code"filtertype="list"fill="true"keylookup="false"cgikey="abilitytopay0z">

3:<listsource="self">

4:<itemvalue="1"display="1 - 99"/>

5:<itemvalue="2"display="100 - 199"/>

6:<itemvalue="3"display="200 - 299"/>

7:<itemvalue="4"display="300 - 399"/>

8:<itemvalue="5"display="400 - 499"/>

9:<itemvalue="6"display="500 - 599"/>

10:<itemvalue="7"display="600 - 699"/>

11:<itemvalue="8"display="700 - 799"/>

12:<itemvalue="9"display="800 - 899"/>

13:<itemvalue="10"display="900 - 1000"/>

14:<itemvalue="11"display="0"/>

15:</list>

16:</dimension>

17:</field>

File: cavariables.xml

This file will create a variable for the translated codes. It defines the bins and maps those definitions back to the dimensions defined above. In the dimension definition above, note that we reference a variable ability_to_pay0code. This same variable name is used in the snippet below. The following would be inserted within the <defaults><fields> tags: