Advanced Search
Search Results
114 total results found
Channels & General Etiquette
#general can be used for anything including banter and support requests. Anything in the Automated category is automated. Posting in there can be done, but most have it muted. So you probably won't get an answer. #random is where memeing takes place #nsfw-ran...
Roles
You can have multiple roles. Normal Roles Normal roles cannot be tagged, but are displayed in the sidebar. Use this if you want to display what your current job description is. To get a Normal role, please use one of the following in the #r...
Job Postings & Requests
If you are submitting a #job-offers please use the following template for easier parsing: [Status] Open [Duration] X months [Location] Remote [Compensation] 1B€ [Description] Know Salesforce. Advise the VP on ...
Bots
You may use Dyno to listen to music. Simply join a voice channel and use #jukebox-requests to request a playlist. Useful commands: ?play <whatever> - searches for a song and plays it?nowplaying - displays Now Playing?skip - skips ...
Partner Servers
We don't have any partner servers for the moment. We did, but they became inactive, so we removed them.
Basic rules for Vendors
The basic rules for the server apply to everyone. If you have not done so, please read #basic-info.We are considering you to be familiar with these rules as you have read them enough to see how to become a vendor ;) In addition, there are two extra rules for ...
Vendor Perks
You get to read #vendors-basic-info You get a fancy role - we can change the role color to match your branding as long as you give us a hex code. Note that dark colors are nigh-unreadable on Discord though. You get access to #vendors - your privileged conta...
General Conventions
All Naming Conventions Are RFC 2119 and RFC 6919 compliant. All field API names MUST be written in English, even when the label is in another language. All field API names MUST be written in PascalCase. Fields SHOULD NOT contain an underscore in the fields ...
Grouping fields
If the organization is home to multiple services, the field API name SHOULD be prepended with the name of the service that required the field, followed by an underscore. This MUST NOT be the case if there is only one service using the object. If several...
Workflow Triggers
Workflow Rules (along with Process Builders) are now on a deprecation / End-of-Life plan. Existing Workflow Rules will continue to operate for the foreseeable future, but in the near future (Winter 23) Salesforce will begin to prevent creating new Workflow Rul...
Workflow Field Updates
Workflow Rules (along with Process Builders) are now on a deprecation / End-of-Life plan. Existing Workflow Rules will continue to operate for the foreseeable future, but in the near future (Winter 23) Salesforce will begin to prevent creating new Workflow Rul...
Workflow Email Alerts
Workflow Rules (along with Process Builders) are now on a deprecation / End-of-Life plan. Existing Workflow Rules will continue to operate for the foreseeable future, but in the near future (Winter 23) Salesforce will begin to prevent creating new Workflow Rul...
Workflow Tasks
Workflow Rules (along with Process Builders) are now on a deprecation / End-of-Life plan. Existing Workflow Rules will continue to operate for the foreseeable future, but in the near future (Winter 23) Salesforce will begin to prevent creating new Workflow Rul...
Workflow Outbound Messages
Workflow Rules (along with Process Builders) are now on a deprecation / End-of-Life plan. Existing Workflow Rules will continue to operate for the foreseeable future, but in the near future (Winter 23) Salesforce will begin to prevent creating new Workflow Rul...
Validation Rule Metadata Conventions
The Validation Rule Name MUST try to explain in a concise manner what the validation rule prevents. Note that conciseness trumps clarity for this field. All validation Rules API names MUST be written in PascalCase. Validation Rules SHOULD NOT contain an und...
Validation rules writing conventions
All Validation Rules MUST contain a Bypass Rule check. Wherever possible, a Consultant SHOULD use operators over functions. All possible instances of IF() SHOULD be replaced by CASE() Referencing other formula fields should be avoided at all cost...
Bypasses
We reference "bypasses" in a number of these conventions. Bypasses are administrator-defined checkboxes that allow you to massively deactivate automations and validation rules with a simple click. They avoid that awkward feeling when you realize that you need...
Salesforce Architecture resources
Official Salesforce Docs Undesrstanding the multinenant Architecture https://www.developerforce.com/media/ForcedotcomBookLibrary/Force.com_Multitenancy_WP_101508.pdf https://developer.salesforce.com/wiki/multi_tenant_architecture ...
1 - Data Migrations Checklist
The following is a semi-profanity-ridden attempt at explaining one way to do data migrations while following best practices. It is rather long and laced with colorful language. If you have read it already, or if you want to avoid the profanity, you can consult...
Trailheads we like
Basic Trailheads Consultant:https://trailhead.salesforce.com/en/content/learn/modules/consulting_partner_basics BA:https://trailhead.salesforce.com/en/content/learn/trails/force_com_admin_beginnerhttps://trailhead.salesforce.com/en/content/learn/trails/force...