Back to forum list… Back to How Do I?...

Fixed Width Writer Transform Inserted a Blank Row (4 replies)

Arline Welty
3 months ago
Arline Welty 3 months ago

Question here on a fixed width writer transform. We have a job that creates a .txt file of bank transactions that is then uploaded to a bank's FTP site for a positive pay job. It's been in place for a week with no real issues. Last night the Fixed Width Writer Transform inserted a blank row into the file. The weird thing is, the row that should have been there was inserted at the very bottom of the file. 

So essentially, all the data were accounted for, but why was the blank row inserted? And why was the "missing" row inserted at the bottom?

The transforms are:

DB read Transform>Map Transform>Fixed Width Writer transform

There have not been blank rows inserted into previous .txt files that that IMAN job generated.

I'm not sure if this will be an issue for the bank but am slightly concerned about that - suggestions on how I can understand how this happened and how to prevent it?

Support
3 months ago
Support 3 months ago

Arline, not sure.

Have you checked the source data (i.e. the query) which ultimately generated the file?

Thanks

Arline Welty
3 months ago
Arline Welty 3 months ago

Hmm - makes sense. The db read queries a table. But I queried the table for blank rows and am not getting any results. 

Support
3 months ago
Support 3 months ago

What did the query do yesterday? Can you replicate the query from yesterday?

If you can, then step through IMan to see if you spot the issue.

Arline Welty
3 months ago
Arline Welty 3 months ago

It's quite involved to capture the exact data set from yesterday because of the way the records are flagged (it's not just "was it updated yesterday".) I think what I might do is put in an ORDER BY clause in the query going forward. I think (?) that would have prevented this issue. It is still very odd to me that there was a blank row inserted, and the "missing" row was appended at the bottom of the file. I don't think that's how SQL would have returned the rows in the first place - I suspect it had something to do with the fixed width writer itself. 

I do appreciate that if I could duplicate the exact behavior from yesterday we'd have better info here. I am monitoring the job closely so will post again if the situation repeats itself after the ORDER BY clause.

 

Contact

Realisable Software Ltd provides code-free, cost-effective applications integration solutions for SMEs. Our core IMan product is designed to integrate almost any application with a number of Sage solutions and online payment processors.

Looking to purchase IMan, please see our resellers here.

Realisable Software
Ph: +44 (0) 208 123 1017

Copyright © Realisable. All rights reserved.
Realisable is a registered trademark

Close

Request Demo

Realisable Software Ltd provides code-free, cost-effective applications integration solutions for SMEs. Our core IMan product is designed to integrate almost any application with a number of Sage solutions and online payment processors.

Looking to purchase IMan, please see our resellers here.

Realisable Software
Ph: +44 (0) 208 123 1017

Copyright © Realisable. All rights reserved.
Realisable is a registered trademark

Close

Access Downloads

Realisable Software Ltd provides code-free, cost-effective applications integration solutions for SMEs. Our core IMan product is designed to integrate almost any application with a number of Sage solutions and online payment processors.

Looking to purchase IMan, please see our resellers here.

Realisable Software
Ph: +44 (0) 208 123 1017

Copyright © Realisable. All rights reserved.
Realisable is a registered trademark

Close