Understanding Salesforce Suffixes

When working in Salesforce, especially as a developer or admin, you’ve likely encountered various suffixes like __c, __r, or __mdt in your objects and fields. These aren’t random – they each serve a purpose and provide critical insight into the nature of the data you’re working with.

In this blog post, let’s dive deep into what these salesforce suffixes mean and how they help in understanding and navigating Salesforce architecture more efficiently.

Why Do Salesforce Suffixes Matter?

Suffixes in Salesforce help identify:

  • Whether an object is custom or standard
  • If the object represents a relationship, metadata, or event
  • Whether it was generated from a geolocation, external system, or data change event

Understanding these suffixes enables you to write cleaner SOQL, debug integrations effectively, and build scalable solutions.

Common Salesforce Suffixes & Their Meanings

Suffix / ExtensionDescription
__cCustom object
__rRelationship field (used in SOQL to traverse to related records)
__xExternal object (used in Salesforce Connect to link to outside systems)
__mdtCustom Metadata Type (used for storing app configurations)
__ePlatform Event (used for event-driven architecture)
__changeEventChange Data Capture event (for tracking data changes in real-time)
__bBig Object (for handling massive volumes of data without hitting limits)
__HistoryField History Tracking for Custom Objects
__shareSharing object (controls sharing access manually or via sharing rules)
__feedChatter feed object (e.g., AccountFeed, CaseFeed for collaboration)
__tagTag object (deprecated but used in older tagging implementations)
__kaKnowledgeArticle
__kavKnowledgeArticleVersion
__FeedCustom Object Feed
__xoSalesforce-to-Salesforce (S2S) spoke/proxy object
__pcCustom Person Account Field
__prUsed for traversing custom Person Account relationship fields
__latitude__sStores the latitude value of a location
__Longitude__sStores the longitude value of a location
__Location__sCompound field that stores both latitude and longitude

Understanding these suffixes is essential for anyone working in Salesforce – whether you’re building LWC components, writing Apex triggers, integrating with external APIs, or analyzing security models.

Author

  • Satyam parasa

    Satyam Parasa is a Salesforce and Mobile application developer. Passionate about learning new technologies, he is the founder of Flutterant.com, where he shares his knowledge and insights.

    View all posts

Leave a Comment