Release Notes

2023.1.0

June 2023

Release notes describe the enhancements and bug fixes contained in new releases and maintenance releases.

  Tip:  To find the release note that contains a specific issue, search on the Prophix Support Desk ticket number.

What's new

Jobs now have steps

• The job definition hierarchy now includes a new level: steps.

• A step is a container for one or more tasks; the new hierarchy appears as follows:

  

• The main benefit of steps is that they run serially, and thus allow you to control the running order of your tasks.
• Steps also offer better control of dependencies: if a step fails, the subsequent steps are automatically canceled.

Query code editor

• A code editor now replaces the text editor In the Query tab of the following agents:
  • MySQL
  • ODBC
  • Script
  • SQL Server

  

Resolved issues

Note that the current build is always cumulative: it contains all previous patches.

At this time Data Integration has no resolved issues to report.

Ticket number	Area	Description
151317	SQL Server Agent	Failed to read the result set.
152744, 152319, 152593	ODBC32 Agent	If the query returned more than 1,000 records, the process failed.

Known issues

Area	Description	Workaround
Acumatica	When using Acumatica as the Source and AcccountSummaryInquiry as the query object, and if there are no query filters, the Data Integration process fails, returning the error message [Error: Timedout]: The job timed out.	In the query, add a filter condition to the Period field.
ODBC	When using ODBC as the Destination, field names that contain keywords or reserved words from the Source will not map and the process will fail.	An upcoming release will address this issue.
ODBC	When using ODBC as the Destination and with text or Excel as the Source, if the Connection has Column name in first row turned off, then mapping will fail and the process will fail.	An upcoming release will address this issue.
SFTP and AWS S3	In a job definition, if Delete source file(s) after transfer is turned on, and if the transfer fails, the task still deletes the originating file.	An upcoming release will address this issue.
ODBC32 Agent	If a Data Integration process runs a job that uses an ODBC32 agent, the job may fail if the number of records fetched exceeds the ODBC32 driver's data threshold. (The number of records varies depending on the specific ODBC32 driver.) In the Result Details for the process, the following error message normally indicates this issue: Status(StatusCode="ResourceExhausted" ,"Received message exceeds the maximum configured message size"	This issue was resolved in June. After confirming the failing jobs are using an ODBC 32-bit agent, upgrade to a 64-bit agent as follows: 1. Request that your IT team generate a 64-bit Data Integration agent similar to your 32-bit ODBC connection. 2. After you receive 64-bit ODBC credentials, create a new ODBC agent and connection. 3. Copy the queries from ODBC32 to ODBC64. 4. Update the job so that it points to the new connection you created (or create a new job that uses the new connection).