Expose the Request ID in a transaction & also show it against ApexLog records - Ideas - Salesforce Trailblazer Community
Trailblazer Community

All Ideas

Idea Details

Post an Idea
270  Points
Idea has been posted. Give it an upvote or downvote.

Expose the Request ID in a transaction & also show it against ApexLog records

Development (Apex, LWC & VF)

Event Monitoring currently exposes the REQUEST_ID as a field:

The unique ID of a single transaction. A transaction can contain one or more events. Each event in a given transaction has the same REQUEST_ID.

This detail could be extremely useful for tying together a transaction with its corresponding ApexLog, Event Monitoring, and Change Data Capture. 

For instance, if there was an exception the message that is displayed to the user could include unique Request ID. That could then be used by someone providing support to directly find a corresponding ApexLog and/or EventLog entry.

Mock up exposing Request ID

This would need a method in Apex that returns the request ID string.

Merge Idea · Flag

  • Upvotes
  • Downvotes



from AppExchange


No results found.

Help us to keep IdeaExchange clean by pointing out overlapping ideas. We'll investigate your suggestion and merge the ideas if it makes sense.



Thanks for your merge suggestion. We will review it shortly and merge the ideas if applicable.

Salesforce takes abuse situations very seriously. Examples of abuse include but are not limited to posting of offensive language or fraudulent statements. To help us process your request as quickly as possible, please fill out the form below describing the situation. For privacy and security reasons, the final outcome of an abuse case may not be revealed to the person who reported it.


Thank you for your feedback. We take abuse seriously and will investigate this issue and take appropriate action.