nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

WFTask::AddFile() issue

rajit

Hi All,

I'm facing a peculiar issue with the WFTask::AddFile() function in an external task we have to attach the referenced files.

While most of the referenced files are getting attached successfully, some are left out. The AddFile() function seems to return nothing for these cases, as the captured result string is empty. (For successful ones, it returns 1)

The only 'pattern' I see between the files that are not attached, is that all of them have a fairly long filepath string (150-200 characters).

Has anyone seen this issue before. Any directions to resolve this issue will be really helpful.

Thanks in advance for sharing your valuable thoughts.

Regards,
Rajit
TS 6.7.2 on Windows 2003

Find more posts tagged with

Comments

ISCBorisB

Hi All,

I'm facing a peculiar issue with the WFTask::AddFile() function in an external task we have to attach the referenced files.

While most of the referenced files are getting attached successfully, some are left out. The AddFile() function seems to return nothing for these cases, as the captured result string is empty. (For successful ones, it returns 1)

The only 'pattern' I see between the files that are not attached, is that all of them have a fairly long filepath string (150-200 characters).

Has anyone seen this issue before. Any directions to resolve this issue will be really helpful.

Thanks in advance for sharing your valuable thoughts.

Regards,
Rajit
TS 6.7.2 on Windows 2003

Try to run CLT "iwaddtaskfile" with one of these Files, that's what AddFile Method is using. STDERR/STDOUT output may provide some clues

Adam Stoller

Hi All,

I'm facing a peculiar issue with the WFTask::AddFile() function in an external task we have to attach the referenced files.

While most of the referenced files are getting attached successfully, some are left out. The AddFile() function seems to return nothing for these cases, as the captured result string is empty. (For successful ones, it returns 1)

The only 'pattern' I see between the files that are not attached, is that all of them have a fairly long filepath string (150-200 characters).

Has anyone seen this issue before. Any directions to resolve this issue will be really helpful.

Thanks in advance for sharing your valuable thoughts.

Regards,
Rajit
TS 6.7.2 on Windows 2003

I suggest you add debugging to your code to do something like:

If that doesn't shed light on the issue, replace the use of the method call with a CLT call (iwaddtaskfile) and capture not only the return code, but the output on both STDOUT and STDERR and log that information.If you still can't figure out what's happening, you'll need to post the code and the debugging log information for anyone here to be able to assist you.

rajit

As I had already printed the return code, this time I tried the CLT route and found that the file paths contained '%20' in place of spaces, and the AddFile() function was not able to locate the file with the %20 in the filepath.

I replaced %20 back with a space before feeding it to the function, and it seems to work fine. Still trying out all other cases..

Thanks for your practical tips, ISCBorisB and ghoti! Appreciate your guidance...

expandAndCollapse.rptdesign

Adam Stoller

As I had already printed the return code, this time I tried the CLT route and found that the file paths contained '%20' in place of spaces, and the AddFile() function was not able to locate the file with the %20 in the filepath.

I replaced %20 back with a space before feeding it to the function, and it seems to work fine. Still trying out all other cases..

Thanks for your practical tips, ISCBorisB and ghoti! Appreciate your guidance...

You're welcome - now for the next tip: