Tony F White

1.8K posts

Tony F White banner
Tony F White

Tony F White

@tonyfwhite

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

Brisbane, Australia Katılım Haziran 2011
476 Takip Edilen363 Takipçiler
Tony F White
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 tweet media
English
0
0
0
20
Tony F White
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)
English
3
0
1
64
Tony F White
Tony F White@tonyfwhite·
@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
English
1
0
0
20
Tony F White
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)
English
1
0
0
45
Tony F White
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
English
1
0
0
34
Tony F White
Tony F White@tonyfwhite·
@smackinnon Salesforce Support are still trying get an answer on this issue.
English
0
0
1
144
Spencer MacKinnon
Spencer MacKinnon@smackinnon·
@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
English
2
0
1
64
Tony F White
Tony F White@tonyfwhite·
@smackinnon Thanks, saw you had moved on after I posted, but thanks for the suggestions.
English
0
0
1
51
Tony F White
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.
English
0
0
0
18
Tony F White
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
English
0
0
0
24