[Req] Easier way to split column & generate multiple files

Hellos,
The current way to spilt a column require 
1. a calculation
2. changes in the output file 
3. not clear if can be used in packages

Other ETL program a 1 mouse click(ok maybe two) to select a variable , define location & bam multiple files as needed in location of choice.

Can I request for
1. something similar (simple)
2. the ability to use the same in package 
3. ability to preserve the new file location and load them in mail packages.

 

Just letting you know that we have just added a new transformation function "Create New File"
It makes easier working with dynamic file names

www.etl-tools.com/wiki/advanced-etl-proc...ous/create-new-file/

I hope you will find it useful.

Hellos,
1. When loading the 'Create New File' , can we've a default <file_name> variable loaded for users ? (or something else you like)
2. I see that in example , we need to reference the variable with GetVariable ---->   {GetVariable('<file_name>')}  .I personally feel 'GetVariable' add the extra complexity here , since I have already defined the variable inside, or maybe near filename dialog we can have a text saying Use above syntax . It's not a dealbreaker but would be a good reminder for users
3. I am getting the following error , when trying to run this
4. Does this transformation need to have outgoing connection to a variable always?



 

 
 

When loading the 'Create New File' , can we've a default <file_name> variable loaded for users ? (or something else you like)

That was implemented in the latest release, we used #file_name# variable

I see that in example , we need to reference the variable with GetVariable ---->   {GetVariable('<file_name>')}  .I personally feel 'GetVariable' add the extra complexity here , since I have already defined the variable inside, or maybe near filename dialog we can have a text saying Use above syntax . It's not a dealbreaker but would be a good reminder for users

Totally agree with you, I think how our software works with variables and parameters is very confusing and it must be made easier to use and understand

I am getting the following error , when trying to run this

That was corrected in the latest release.

Does this transformation need to have outgoing connection to a variable always?

Not really

Hellos,
1. With new release , error disappears 
2. For Future readers the variable now is {GetVariable('#file-name#')}.html ( I am using HTML table , that's why format is HTML)
3. To make it easier for new users , some sort of indication , where and which variables can be entered will be useful or even a dropdown (that might be too hard) 

Can we now build on top of this to send HTML emails (with html tables)  using packages from this release or we expecting some improvements ?

Can we now build on top of this to send HTML emails (with html tables)  using packages from this release or we expecting some improvements ?

We are not going to to make any further changes to this functionality so please go ahead and use it.