Tony F White

@msrivastav13 @SalesforceDevs @gregwhitworth is refreshEvent still broken for LWC quickActions? salesforce.stackexchange.com/questions/4085… salesforce.stackexchange.com/questions/4108…

@tonyfwhite @SalesforceDevs @gregwhitworth Any ideas on this?

@msrivastav13 @SalesforceDevs Any idea if there any plan to allow/fix sending refresh events from modals? salesforce.stackexchange.com/questions/4085…

@asksalesforce Thanks! For anyone else with this issue - SF Support now have been provided bug: W-17668353 There is no known issue available for this, but provided confirmation there is a bug in the new Enhanced Custom Report Type setup, and suggested a work around:

@tonyfwhite Thank you for alerting us, Tony. We have shared this with the team. ^RG

@salesforce #reporting #Spring2025 Seems you have an error updating report types with the new #Spring2025 interface when updating a Custom Report Type: Error notification. java.lang.IllegalStateException: Duplicate key Case (attempted merging values Case and Case)

@asksalesforce Was directed to this known issue for Joined Reports - issues.salesforce.com/issue/a028c000… I am not using joined reports, and removing all fields from the report type we still get the error trying to update the report type. And if I update the report type via the metadata it works as expected

@tonyfwhite Thank you for submitting the support case, Tony. Our team will investigate and follow up with you. ^PK

Further info: removing all fields and sections from the layout and you still get the same error. Replicate: Primary Object = Case Object B: Initiated Cases (custom field > lookup to Case)

1) Creating the same report type in production works fine. 2) Using metadata API to create/update the report type works fine. The error only occurs in Spring25 with the new edit interface (which is a much improved interface) A SF case has been created

Here is the known issue for the GraphQL Custom Date field Grouping error- issues.salesforce.com/issue/a028c000…

FYI, Salesforce are classifying it as a bug, and should be raising it as a known issue. For full response details please see: salesforce.stackexchange.com/a/429136/754

@msrivastav13 I am trying to work out how to do a aggregate graphql on a date field, but am getting an error: Couldn't find apiElementInfo for field: Assigned_Date__c I believe it is supported - developer.salesforce.com/docs/platform/… SOQL I can aggregate on it np. Any idea? #salesforce #lwc

@smackinnon Salesforce Support are still trying get an answer on this issue.

@tonyfwhite Hi Tony, I’m no longer at Salesforce and didn’t do the implementation for the aggregation capabilities within GraphQL, only the design. Opening a case is right, and insist on them getting an answer from the dev team whether this is intended or not. If it’s not intended, then

@smackinnon Thanks, saw you had moved on after I posted, but thanks for the suggestions.

@tonyfwhite the error message could at least be better.

@rossbelmont @sunnydalelow Thanks. Ended up using legacy as more effort for the new implement for no benefit. And not seen any plan to appreciate the legacy. We did use the new one for another service that does have authentication.

@sunnydalelow I have had an interesting question raised about Named Credentials, and thought perhaps you might be able to provide your thoughts as I see you wrote medium.com/salesforce-arc… last year. 1/2

If the API service has no credentials and all users can use it, would you use Legacy Named Credentials or the New Named Credentials. 2/2