Transforming data is a necessity when you are importing data into any other system or when you are preparing a report or list. In
this post
we already wrote about data transformations that come with DataBridge and that can be a life saver when you set up an import. But what if you would need to perform multiple transformations in a row before you can safely say that the data fits the target platform? That's where the data domino comes in.
Now, data domino sounds really nice, but our marketing colleagues decided to name the feature 'chained transformations'. Yes, we know, less appealing. But they say it is much more businessy.
Whatever the name is, we like the feature! Let's look at a few real life examples where chained transformations helped us.
Dutch zip codes
In the Netherlands, zip codes consist of 4 numbers and 2 letters, like this: '1234AB'. The ways users enter them are numerous.
- 1234 AB
- 1234AB
- 1234 ab
- 1234ab
- 1234 Ab
- 1234-AB
- 12 34 AB
You probably see the challenge...
With just two transformations these entries are formatted properly. The first transformation we apply is to capitalize all characters. The second is to get rid of all spaces and other characters we don't want in there. If you are proficient with regex (or just a good Googler), you can even apply a mask to the output.
Let's look at another example where our domino skills can be of assistance.
Create and assign tasks
You have a website where questions can be asked about either of your products. Your esteemed visitor fills in a web form with the inquiry and selects the product he or she is interested in. The details from the web form are emailed to... DataBridge of course.
The goal is to make sure that a task is created in SuperOffice CRM, assigned to the right colleague. The challenge is to use the product selection to link it to the colleague. Let's come up with a very simple example.
The product code tells us what the product group and the product is. The first character is the product group and that is what we want to use to match the colleague. The part after the hyphen is the product; we will not use that.
The first transformation we'll do is Split Field. With this one, we'll create an additional field with only the p, r or x as a result. The split will, of course, be done on the hyphen.
Now that we have our 'product group indicator' we can throw in a Map List transformation that makes sure the p is mapped to Clair, the r to John and the x to David.
I'm sure you see the time you save here not having to talk to the website builder or the administrator of the ERP platform. Agree?