2.3.8.5 release notes

2.3.8.5

• Implemented several enhancements and fixes for the GraphQL support features added in 2.3.8.4:
  • Issue 2865 - Addressed numerous gaps in the SOQL-to-GraphQL query conversion logic:
    • Added conversion of all known supported SOQL functions and aggregates in ORDER BY and GROUP BY clauses including the DISTANCE() and GEOLOCATION() functions. Note that these two specific functions are not supported in GraphQL in the SELECT clause (at least as far as I can tell) and are emitted as a comment if found in that clause in the source SOQL query.
    • Added conversion of the SOQL GROUP BY CUBE and GROUP BY ROLLUP clauses.
    • Added conversion of the SOQL LIMIT clause into the corresponding GraphQL first clause.
    • Added conversion of the SOQL FOR REFERENCE/VIEW clauses into the corresponding GraphQL updateMRU: true clause.
    • Added conversion of polymorphic fields. Note that only one matching target type is added to the resulting GraphQL query, but a comment is also added denoting the field as being polymorphic. Note also that the resulting GraphQL query may be incorrectly flagged as invalid because of issues with the Salesforce GraphQL schema where the intermediate schema types are named TargetTypeAggregate instead of TargetType as expected by the Salesforce GraphQL API endpoint.
    • Added conversion of queries that use aliases.
    • Fixed an issue with conversion of SOQL NOT expressions.
    • Fixed issues with conversion of queries against SObject types and fields with namespaces.
    • Comments are now added to the GraphQL query for unsupported SOQL clause types.

    Note that in order to implement several of these features and fixes, IC first "normalizes" the provided SOQL query to inline all aliases, remove all but the first queried entity from the FROM clause (which is safe since references to them have been inlined), and replace all SObject type and field names with their respective canonical forms as expected by the Salesforce GraphQL schema.

    With these enhancements, I believe that all of the documented use cases for SOQL-to-GraphQL conversion are covered. I'm sure that there are still some things that are missing, and there are almost certainly some things that are present but result in incorrect GraphQL. If so, please bring those to my attention and I'll be happy to address them.

  • The Salesforce GraphQL schema is generally larger than the JetBrains GraphQL plugin's default allowed size. I haven't really seen this be an issue in 2025.2+, but in 2025.1 it can result in GraphQL language features not working properly. IC now provides assistance with configuring the GraphQL schema type limit if needed. Note that because that configuration is via an IDE registry setting, IC cannot change the value itself and instead guides the user to the IDE's registry editor, specifying the exact registry key and value required for the retrieved GraphQL schema.
• Issue 2880 - Added numeric as an allowed value for the LWC lightning-formatted-date-time component's month attribute.
• Other related fixes and improvements.