First of all I wish you all merry christmas - and I assume that no one is crazy enough to connect to crossroads these days:)
Nevertheless, I am trying to use "submit hierarchy" to pull out of a hierarchy all the relevant files and via the output connection parameter (include folders/exclude folders) decide which path the files should take.
Unfortunately, the flow always takes all the files to all the paths - even though I defined for one path: include pattern: EPM*
and for the other "all the others"
Someone out there?
Thanks
Ariel
submit hierarchy - how does it work!!!
-
- Advanced member
- Posts: 230
- Joined: Thu Aug 07, 2014 10:04 am
submit hierarchy - how does it work!!!
The number of levels is also important when using "Submit hierarchy". Perhaps that is where your problem lies.
Freddy
Freddy
-
- Advanced member
- Posts: 230
- Joined: Thu Aug 07, 2014 10:04 am
submit hierarchy - how does it work!!!
it is good to have you back! Too long vacation is not healthy:)
No, put even a greater level than actually required.
I "solved" it now by adding hierarchy information to the files and later in the connection after an intermediate folder I filter according to the hierarchy info.
No, put even a greater level than actually required.
I "solved" it now by adding hierarchy information to the files and later in the connection after an intermediate folder I filter according to the hierarchy info.