---
title: Naming Convention For Salesforce
description: "**Impact area** Manageability **Severity** Medium **Affected element** All Configuration Element Types ## Rule ID **SF-NM-***  The wildcard (*) means that we have a specific rule for each Configuration Element Type in Salesforce. * Example: SF-NM-DSH for setting the Views naming rules.*…"
url: "https://community-staging.qualityclouds.com/qcdocs/qc/salesforce-rules/naming-convention-for-salesforce/"
updated: "2025-03-21"
category: Rules
---

# Naming Convention For Salesforce

**Impact area**

Manageability

**Severity**

Medium

**Affected element**

All Configuration Element Types

## Rule ID

**SF-NM-***

 The wildcard (*) means that we have a specific rule for each Configuration Element Type in Salesforce.

* Example: SF-NM-DSH for setting the Views naming rules.*

## Impact

The Salesforce best practices and ecosystem enforces the Pro-Code and Low-Code audiences to follow specific patterns in order to have a consistent file naming that helps keep all the elements easy to recognise and find. We provide 2 types of naming convention out of the box:

- PascalCase: [applied to Pro-Code elements](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_naming_conventions.htm).
- Natural Case: applied to Low-Code elements.

## Remediation

We highly recommend that you bookmark [the naming conventions table](https://salesforce.quip.com/MW5cAPVwat8k) (or print it out, if you’re old-school), so you can find it quickly when you need it, until you become more familiar with the contents or finish defining your own naming conventions.

### Time to fix

10 min