Text File As Source/Target Release Notes

Release notes are displayed in descending order from the most recent release to the oldest. Known Issues are listed with the most recent release.

See TIBCO Scribe® Online Text File As Source and TIBCO Scribe® Online Text File As Target for more information.

Version 2.2.0 Release

Released February 28, 2023.

New And Noteworthy

Changes In Functionality

Migration and Compatibility

If you have a Dropbox connection that has not been used for some time, open the Connection dialog and reauthenticate. If you do not reauthenticate you may see errors similar to the following: Invalid Response (SCTXTS-536)

Closed Issues

14450 / SCTXTS-109

If the header row for a Source text file changes after the Text File as Source Connection has been configured, when a flow using that Connection executes, the fields in the header row that do not match the original configuration are skipped. For example, if the original CSV had a field called “TransactionDate” and the latest CSV file has a field called “Transaction Date”, values for that field are not included when the flow executes and no errors are generated. (Case # 80293)

SCTXTS-113

When using the Text Connector to connect to Dropbox, if you modify the path in the Remote Directory field you have to reauthenticate.

SCTXTS-114

The Text as a Target connector is not using the file encoding setting manually configured in the Connection dialog. The Connector is basing the encoding on the data sent to the target file.

SCTXTS-115

Text as a Target mapping generates a Fatal Error when attempting to open the target file. The error is similar to the following:

Error Occurred opening target file /<filename>.csv. Exception: This stream does not support seek operations.

SCTXTS-120

When using OneDrive as a source where a refresh token is requested, the Text as Source Connector sometimes cannot store the updated authentication token and errors similar to the following are generated: (Case # 01853223, 01891926)

error":"invalid_grant","error_description":"The request was denied because one or more scopes requested are unauthorized or expired. The user must first sign in and grant the client application access to the requested scope.

error":"invalid_grant","error_description":"The user could not be authenticated as the grant is expired. The user must sign in again.

error":"invalid_grant","error_description":"The provided value for the input parameter 'refresh_token' or 'assertion' is not valid. The token was issued for a different client id

SCTXTS-121

When configuring a Text connection, if a duplicate field name is entered on the Fields tab, no error is generated. However, if you do a Query Preview of the data or you run the flow in debug mode, an error similar to the following is generated: (Case # 01868482)

Invalid Query. 58873 record failures occurred. The first failure occurred at record 1 with the following exception: An item with the same key has already been added

SCTXTS-122

When a new SFTP server is updated and a new certificate is generated, configured text connections could be updated with the new fingerprint, requiring users to configure a new connection.

SCTXTS-123

When an app runs with multiple flows that reference the same SFTP Connection, if any of those flows run longer than the SFTP server inactivity period, the connection is closed by the server and subsequent flows in the app cannot connect. An error similar to the following is generated: (Case # 01812018, 01813944, 01815566, 01826496)

‘FATAL Error : "invalid query. could not get oldest file name"

SCTXTS-130

Text Qualifier setting in the TIBCO Cloud™ Integration - Connect Text File As Target connector does not produce desired output for two entities accessing the same file.

SCTXTS-131

Updated the SFTP libraries and added additional logging for some customers who have had durability issues with connectivity.

SCTXTS-286

Text File as a Target Connector appending different entities to the same text file within the same flow causes blank rows.

SCTXTS-380/SCTXTS-412

Auth tokens for Dropbox now expire after four hours and currently there is no refresh token, causing connections to fail.

SCTXTS-531

Addressed issues associated with source and target text files that were Fixed Width format, including: (Case # 02152933, 02152934, 02152967, 02152973, 02153041, 02153159)

Known Issues

SCTXTS-548

Summary: When the Text Connector tries to connect to an SFTP server, some connections generate errors similar to the following: (Case # 02168068, 02167827)

Error - Text Connector: Collection was modified; enumeration operation may not execute.

Workaround: Contact Support for Hotfix SCTXTS-547 / SCTXTS-548.

SCTXTS-547

Summary: Depending on the SFTP server used, some SFTP connections have issues with connections timing out and generate errors similar to the following: (Case # 02168382, 02169188, 02168738, 02168726, 02169205, 02168068, 02169681, 02169684, 02169687, 02169690, 02169700, 02169715, 02169717, 02169766, 02169778, 02169784, 02169789, 02169791, 02169825, 02170010, 02169699, 02170329, 02170400, 02171319, 02171343)

Invalid Query. Could not get oldest file name.
The following error has occurred in the Text Connector: Could not check if directory exists.
Client not connected.

Workaround: Contact Support for Hotfix SCTXTS-547 / SCTXTS-548.

SCTXTS-542

Summary: If you have a Source Text Connection where some entities have a post processing rule of Delete File or Move File and other entities have a post processing rule of Do Nothing, using that same connection in multiple flows may cause all flows after the first one to fail with an error similar to the following: 

Failed to open one or more connections: The following error has occurred in the Text Connector: Could not find file <file name>

Workaround: Configure all entities in the connection with the same post processing rule.

SCTXTS-539

Summary: For files that are Fixed Width format, if you modify the datatype on a field in the Fields tab to anything other than Text, the Field Width column is not reset to a hyphen (-).

Workaround: Edit the Field Width column manually.

SCTXTS-479

Summary: When integrating data from a Source text file to a Target text file, both the Source and Target text connections must have a matching First Row setting on the Entities tab. If one connection has the First Row option set to Field Names and the other connection has the option set to Data, when you try to configure the Create Block in the flow, there is a data mismatch and you cannot configure the block.

Workaround: Select the same option in the First Row field on the Entities tab for both connections.

SCTXTS-471

Summary: The Test button is disabled on the Connection dialog when a Text or Binary file format is selected for one entity and a Delimited or Fixed Width format is selected for another entity on the same connection. Text/Binary file formats cannot be combined with Delimited/Fixed Width formats on the same connection.

Workaround: Create separate connections for Text/Binary and Delimited/Fixed Width file formats.

SCTXTS-459

Summary: For fields configured as datatype Boolean on the Fields tab of the Connection dialog, if the data returned for those fields contains values other than 0, 1, true, or false, some records may be skipped or interpreted incorrectly.

Workaround: Review the data before running flows to make sure there are no unsupported values in Boolean fields.

SCTXTS-455

Summary: When creating a Source connection with a Fixed width file format, in the Fields tab for the Trim column you can only select the default value ‘Both’ from the drop-down list.

Workaround: None.

SCTXTS-453

Summary: If you create or edit a file directly in OneDrive using Tab as your field delimiter, the Text Connector interprets the tabs as spaces and does not generate the fields schema correctly.

Workaround: Create a new file using Tab as the field delimiter on your local drive. Copy that file into OneDrive, and do not edit it on OneDrive.

SCTXTS-452

Summary: For connections to OneDrive, if a Source field is set to one Decimal type and the mapped Target field is set to a different Decimal type, when the field is written to the target, the Source Decimal type is used. For example, if the Source field is set to 'Decimal type' = Period and the Target field is set to 'Decimal Type' = Comma, Source data 11.5 is written to the Target as 11.5 instead of 11,5.

Workaround: None.

SCTXTS-435

Summary: When configuring a Text Connection for Binary Content or Text Content type files, if the files do not exist in the directory specified on the Connection, you cannot save the connection and a "file missing" error is generated.

Workaround: Make sure the files exist in the specified directory or use a different file type, such as Delimited or Fixed Width.

SCTXTS-128

Summary: Processing an extremely large local CSV file can cause the Agent to exceed its memory limit and shut down. (Case # 01918124)

Workaround: Break the CSV file down into several smaller files that can be processed separately.

SCTXTS-126

Summary: Creating a duplicate Text Connection to an SFTP server fails during validation with an error similar to the following: (Case # 01889455)

FTPException: Could not connect to SFTP Server

Workaround: Configure and validate the duplicate connection with a Connect cloud agent instead of a Connect on-premise agent

72423 / SCTXTS-112

Summary: Processing large source text files stored in Dropbox generates errors similar to the following: (Case # 68590)

Invalid Query. This stream does not support seek operations.

Workaround: Break the file up into two or more smaller files.

SCTXTS-111

Summary: The Text as a Source connector expects dates to be in full datetime format including seconds. For example, 01/04/2019 01:01:00 AM is accepted by the connector, but 01/04/2019 01:01 AM returns Null when previewing source data. (Case # 01749249)

Workaround: Change the data type on the field to string instead of datetime.

64919

Summary: The Text File as Source Connector does not use the latest ciphers when accessing text files on an SFTP site. (Case # 64139 , 01728710, 01871406)

Workaround: None.

61000

Summary: When configuring a Text as a Source connection the Fields tab has the option to Generate a fields schema from your data. If the header row in the source file has quotes around the field names, source data is lost when sent to the target system. (Case # 59004, 58871, 63863)

Workaround: On the Fields tab, edit the Field Name to include the quotes for any header field that has quotes around it. For example, change LastName to “LastName”. Save the Connection settings and reset metadata for that connection. See Resetting Metadata.

58133 / SCTXTS-108

Summary: If there is invalid data in a source text file, some apps end with a fatal error instead of skipping the records with invalid data and continuing to process the source file. The error message does not indicate which fields caused the problem. (Case # 60046, 01720414)

Workaround: Correct the data in the source file and reprocess.

55848

Summary: If you open an existing Text as a Target Connection and choose an agent that does not have the text files associated with the entities specified in the Connection configuration, instead of indicating the nature of the problem, the following error is generated:

Please contact Scribe support.

Workaround: Verify that the text files associated with this Target connection are on the computer where the selected Connect on-premise agent is installed. If they are not, select the correct agent in the Connection dialog.

46333

Summary: When the Text Connector for Source is configured to move source text files after processing them, the file is not moved when the app execution completes. The text file is moved at the beginning of the next execution of the app.

Workaround: None.

44408

Summary: When the source contains an invalid date, Previewing the data in the Query Block Preview tab data does not provide an error, but displays "NULL". When data contains a valid date that matches the DateTime Mask defined in Connector it displays correctly. (Case # 58472, 58645)

Workaround: Modify the source data to comply with the supported date/time formats. See Text Connector DateTime Formats.

37700

Summary: When using a Text as a Source Connection, the Query Block Properties Preview tab does not display date field values in the format specified on the Connection Configuration Fields tab. The data is sent to the Target correctly when the Source text file is processed.

Workaround: None.

 

Version 2.1.1 Release

Released July 8, 2019.

New And Noteworthy

Updated the Text File as Source and Text File as Target Connectors to use the OneDrive Graph API.

Closed Issues

SCTXTS -1 / SCTXTS - 2

Due to a modification in the OneDrive API, the Text Connector was not able to complete the authentication process. (Case # 01729525, 01729442)

SCTXTS-8 / 74886 / 50842

When using Text File as a Target, the Target Processing Rule Stop if file exists did not work as expected if the secondary parameter First Row = "field names" was set. The field names were not created as the first row of the target text file. (Case # 01729981, 69862, 59898)

SCTXTS-99 / 74903

When using Text File as a Target, the Target Processing Rule Append to existing did not work as expected if the secondary parameter First Row = "field names" was set. If there was no existing file, the field names were not created as the first row of the target text file.

Version 2.0.1 Release

Released January 4, 2019.

New And Noteworthy

The Text Connector is no longer installed automatically when you install an agent. This Connector is now two separate Connectors, Text File as Source and Text File as Target, available for download in the Marketplace. (62048, 62116, 71429)

Upgrade Notes:

Closed Issues

71026

When the Text File as Target option, Target Processing Rule, was set to Append, existing target text files were overwritten during subsequent executions of apps using that Connection instead of the new data being appended to the end of the file. (Case # 58211, 65520)

Version 2.0.0 Release

TIBCO Scribe® released the Version 2.0.0 update to the Text File as Source and Text File as Target Connectors on October 19, 2018

New And Noteworthy

There are no new features in this release.

Closed Issues

44483

Updated security for SFTP Connections. The prior security settings generated errors similar to the following: ( Case # 65083)

Error:
Win32 ThreadId:10276
Message: Exception Type : FTPException
Message : Could not connect to SFTP Server
Message : Key exchange failed. Requested service is not implemented.

44487 / 68392

When processing a source text file containing quotes with the Text Qualifier field on the Text Connection Entities tab set to None, the Connector was still processing it using double quotes as the delimiter. To work around this issue, users were required to specify a User Defined text qualifier that was guaranteed not to exist in the text file, such as carat (^). (Case # 66515)

Note: If you have used this workaround you may need to modify the setting for the Text Qualifier field to None.

If the text qualifier field is set to None and data in a field contains double-quotes, the quotes are included in the string sent to the target.

66040

Refreshing metadata for an SFTP or FTP connection with a large text file as a source sometimes caused server timeouts. (Case # 65664, 66290, 66328)

 

January 19, 2018 Release

New And Noteworthy

There are no new features in this release.

Closed Issues

When using the Text Connector some users could not create connections to Dropbox or OneDrive accounts. (55379, 55382 / # Case 62147)

 

June 2017 Release

New And Noteworthy

Note: These changes require an agent update. The agent updates automatically after completing any app executions that are currently running. If for any reason your agent does not update, stop and restart the agent to trigger an update.

Closed Issues

46238

Added retry logic to prevent errors when processing multiple maps. (Case # 58954, 58816, 58602)

43434

Added additional retry logic to improve connection stability to SFTP endpoints. (Case # 57810)

 

January 2017 Release

New And Noteworthy

There are no new features in this release.

Closed Issues

35203

When configuring a Text as a Target Connection, you are no longer required to have a target file with a header row of information in the target location. The file can be generated by TIBCO Cloud™ Integration - Connect based on the Connection Configuration.

35697

Text as a Source Connections using a file with fixed width fields displayed field length as 1 in Query Preview and Fields tabs on the Block Properties dialog regardless of the setting in the Text Connection.

Related Topics

Release Notes And Known Issues