function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
EricBEricB 

HEADS UP - $Profile.Name for standard profiles is changing in the Summer '07 release

Prior to the Summer '07 release, the $Profile.Name merge field uses special internal values (e.g., PT1, PT2, etc.) to represent standard profiles (System Administrator, Standard User, etc.).  These special values will be replaced with the externally visible names in the Summer ’07 release.  This means that current uses of the $Profile.Name field must be changed in order to continue functioning after the Summer ’07 release. Note that the new $Profile.Name values are translated in the org's default language at runtime.

If you are only using custom profile names, there is no impact.

Standard Profile Name

Old (Spring ’07)
$Profile.Name Value

New (Summer ’07)
$Profile.Name Value

System Administrator

PT1

System Administrator

Standard User

PT2

Standard User

Read Only

PT3

Read Only

Solution Manager

PT4

Solution Manager

Marketing User

PT5

Marketing User

Contract Manager

PT6

Contract Manager

Partner User

PT7

Partner User

Standard Platform User

PT8

Standard Platform User

Standard Platform One User

PT9

Standard Platform One User

Salesforce Administrator

PT10

Salesforce Administrator

Package License Manager

PT11

Package License Manager

Standard Partner

PT12

Standard Partner

Customer Portal User

PT13

Customer Portal User

Customer Portal Manager

PT14

Customer Portal Manager

 

To ensure your formulas continue to work after the Summer ’07 release, you should modify them to handle both the old and new values of $Profile.Name.

 

For example, this validation rule formula expression:

    $Profile.Name <> "PT1"

 

Should be replaced with this expression to be forward compatible:

AND(
    $Profile.Name <> "PT1",
    $Profile.Name <> "System Administrator"
)

 

Note: After Summer ’07 goes live, there is no need to retain the old internal names (PT1, etc.).

Alexandru IleanaAlexandru Ileana
Hello!

I have verified this and indeed $Profile.Name is fixed, but in some cases users will want the value of the profile to be fixed.
For example I have two fields defined for the Case object: Owner_Profile__c and Creator_Profile__c with a formula similar to: Owner:User.Profile.Name.

In this situation it does not work and displays the same values. What is worse is that Salesforce has implemented some sort of safeguard which prevents users from filtering reports by PT1 (System Administrator). We had to filter our reports by individual members of the administrator profile.

If Salesforce sees this. Please fix! Either make this change from the heart of the problem (The Profile.Name field) or just do not do it at all. Please...