Second Quarter of 2024

Release Date: June 21, 2024

This topic provides a list of product changes released for this module on this date.

Table 1. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
A new meta-SQL function, String_Agg, has been introduced that concatenates string values and places separator values between them. This separator is not added at the end of concatenated string.280932
To enhance performance, the View Query page is no longer refreshed when you switch between pages. You must select the Run button () to refresh the query results.541947
Table 2. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, if you configured picklist behavior in a query, but the query did not contain a prompt, an error occurred when you executed the query. This issue has been resolved.533657
Previously, if a query contained a DateAdd function with a prompt and a default value, an error occurred. This issue has been resolved.531643
Previously, if a subquery contained special characters in the alias, and if the same column was used in the SELECT condition, an error occurred when you filtered the query results. This issue has been resolved.532767
Previously, when you attempted to run a query that contained the MI_SM_STATE_ID_C field from a join query, an error occurred. This issue has been resolved.532764
Previously, when you ran a query in formatted mode, the results displayed for date values were not formatted. This issue has been resolved.562652
Previously, in the Results workspace, when you selected the search icon (), the advanced search icon () did not populate in the columns containing character field values. This issue has been resolved. 562651
Previously, if a query contained the ORDER BY command on a field that was not included in the SELECT list, when you filtered the query results, an error occurred. This issue has been resolved.504018
Previously, in the Advanced section of the Expression Builder window, if you selected an incorrect data type for default prompt values, an error occurred. This issue has been resolved.367892
Previously, when you attempted to create a query containing the COUNT function with *, an error occurred. This issue has been resolved.159788
Table 3. Known Issues

The following known issues and limitations exist.

DescriptionTracking ID
If you configure a date-time field to use the RCF1123 date format behavior, and if you include that field in a formatted query, the date is displayed in English, regardless of your language preference.571424

Release Date: April 5, 2024

This topic provides a list of product changes released for this module on this date.

Table 4. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, a common time zone was not used for all date constants in a query. This issue has been resolved. Now, the user's time zone is considered for all date constants.US603779
Previously, if the Family ID Template contained a hyperlink field, the generated ID included the full anchor tag. This has been resolved. Now, the generated ID contains only the embedded text.DE211926
Previously, on a PostgreSQL datasource, if you attempted to run a query that used constant time, an error occurred. For example, if you run the following query, an error occurred:
SELECT (# :t '00:00:00') "Time"
FROM [AQA REG All Fld Types
This issue has been resolved.		DE210430
Previously, if you added a hyperlink in a query, and a value returned by the query that was inserted into the hyperlink as a parameter included special characters that must be encoded (for example, ?, %, or &), the hyperlink did not work as expected. This issue has been resolved.

To enable the resolution of this defect, now, when you add a manual hyperlink definition in a query that includes an explicit parameter value containing a special character, you must enter the URL-encoded value of the parameter. For example, the manual hyperlink to open a record in Record Manager using a datasheet with the ID TEST?&% must be entered as #record- manager/{1}?datasheetid= TEST%3F%26%25, assuming that the entity key of the record appears in column 1 of the query. However, if a parameter value used in a hyperlink appears in the query result, and is represented in the hyperlink definition by the column reference {n}, you need not encode it.

To support this fix, a utility that identifies affected query hyperlinks has been made available. Please refer to KBA 000069850. Contact GE Vernova support if you need help in updating existing query hyperlink definitions.

DE210003

Previously, the State Caption and Operation Caption fields were not translated to the language based on your culture settings. This issue has been resolved.DE206277