topic Re: TOS for Data integration v8.0.1 [tFileOutputDelimited] : can't create non-existant pathes in the path selector in Installing and Upgrading

TOS for Data integration v8.0.1 [tFileOutputDelimited] : can't create non-existant pathes in the path selector

schwarben — Fri, 15 Nov 2024 22:31:59 GMT

I am currently transitioning from v7.4 to v8, and it seems some behaviors have changed.

in v6 and v7 I was used to use the path selector of a tFileOutputDelimited in order to fill up the base part of a path. In the image bellow a click on button (1) opens a popup window, in this window I can select an existing path (2) and optionally fill up the name of a (possibly non-existent) file (3). When I close that window, the full path is reported in the area (4).

It seems in v8.0.1 this is no longer possible : before I close the "path selection window" it checks if the path I just filled-up exists as a regular file. In particular I cannot leave the text area (3) empty, nor can I enter the name of a non-existing file. See picture 2.

NB: I tried with tFileOutputExcel and the behavior is the same.

Did I miss something ? Is this a bug or a new functionality.

Thank you for your help

Re: TOS for Data integration v8.0.1 [tFileOutputDelimited] : can't create non-existant pathes in the path selector

Anonymous — Fri, 23 Sep 2022 02:12:57 GMT

@benjamin schwarz , I have been trying to understand your issue, what is the path selector? How do you use on tFileOutputDelimited? Can you explain it with a bit details.

Regards

Shong

Re: TOS for Data integration v8.0.1 [tFileOutputDelimited] : can't create non-existant pathes in the path selector

schwarben — Fri, 23 Sep 2022 09:49:39 GMT

Hi Shong, you are right my message was a bit messy and elusive, I rewrote it including images. Thank you for pointing that out.

Re: TOS for Data integration v8.0.1 [tFileOutputDelimited] : can't create non-existant pathes in the path selector

Anonymous — Thu, 29 Sep 2022 07:33:47 GMT

@benjamin schwarz , thanks for your explanations! I have reproduced the issue and open a jira issue to R&D team. I will update to you once I have any news.

Regards

Shong