Split BiBlend table based on dimension value

[Jones]

Hey Community, 

So I am wondering if anyone has any smart idea how to split into multiple BiBlend tables when loading a file into workflow with workflow name Blend.

My current DataSource is using Delimited files. And I have a column in table that I map towards a attribute dimension which contains of 5 different values. I would like to split the tables based on these values instead of loading file in 5 different workflow steps. 

In earlier projects working with data mgmt export sequence data sources I have accomplished similar result by using connector setting "SourceFieldName" to do this. But this option is not available for Delimited File.

So if anyone have any code snippet examples on how to hook any businessrule up with the data source or similar that would be extremely helpful! 

[ckattookaran]

It is not straightforward. You can use a TransformationEventHandler, check whether the operation is Case Is = BREventOperationType.Transformation.BiBlend.EndBiBlendProcessing and then split your Table using SQL. I had to do this one for archiving purposes. The client didn't want it to be always an overwrite.

[JackLacava · Accepted solution]

Instead of risking with Event Handlers, we could use a "Blend, Workspace" profile, so that we get a Dashboard after the blend operation - have a button there that triggers an Extender via Data Management, and do the SQL splitting in the Extender.

[Jones]

Thank you Jack,

I actually ended up with doing exactly this, so happy to hear that this was recommended process!