Tony F White

13x Certified Salesforce Dev/Application Architect ☁️⚡ Avid 📸 - 🤓 - Teacher - 🇦🇺 - Human

[Tony F White @tonyfwhite]

@msrivastav13 @SalesforceDevs @gregwhitworth is refreshEvent still broken for LWC quickActions?
https://t.co/aoHyFvRRza
https://t.co/qej6Wddyva

[Tony F White @tonyfwhite]

@msrivastav13 @SalesforceDevs Any idea if there any plan to allow/fix sending refresh events from modals?
https://t.co/aoHyFvRRza

[Tony F White @tonyfwhite]

@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:

[Tony F White @tonyfwhite]

@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)

[Tony F White @tonyfwhite]

@asksalesforce Was directed to this known issue for Joined Reports - https://t.co/rAtceEo5O6
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

[Tony F White @tonyfwhite]

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)

[Tony F White @tonyfwhite]

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

[Tony F White @tonyfwhite]

Here is the known issue for the GraphQL Custom Date field Grouping error- https://t.co/nv8odOIqtb

[Tony F White @tonyfwhite]

@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 - https://t.co/3wfor0kYCd
SOQL I can aggregate on it np.
Any idea?
#salesforce #lwc

[Tony F White @tonyfwhite]

FYI, Salesforce are classifying it as a bug, and should be raising it as a known issue.
For full response details please see:
https://t.co/C18tvKeSzW

[Tony F White @tonyfwhite]

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

[Tony F White @tonyfwhite]

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

[Tony F White @tonyfwhite]

@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.

[Tony F White @tonyfwhite]

@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 https://t.co/nHSEAiFWvg last year.

1/2

[Tony F White @tonyfwhite]

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