Feed

If you're looking for real-world job or internship opportunities (paid or unpaid) as a Junior Salesforce Administrator or Developer, here are a few reliable places to explore:

✅ 1. Salesforce Careers Portal

https://careers.salesforce.com/en/jobs/

This is the

✅ 2. LinkedIn

Use filters like “Entry Level,” “Internship,” and “Remote” when searching for Salesforce-related roles. Also, follow Salesforce partners and consulting firms who regularly hire juniors.

✅ 3. Indeed & Glassdoor

These platforms often list internships and junior Salesforce roles, especially for Admin and Developer tracks. You can set alerts for relevant opportunities.

💡 Bonus Tips:

• Join Salesforce Talent Alliance and Trailblazer Community Groups for networking and mentorship.
• Keep applying even if a role asks for 1–2 years of experience—many companies are open to enthusiastic, certified newcomers like you.

If this helped you, feel free to mark this as the best answer to help others in the community too!

Best of luck on your Salesforce journey — you’re clearly on the right track! 

Hello @Jeswin K Babu

To get a URL link to an image uploaded in Salesforce CMS, you can follow these steps:

1. Upload the image to CMS: First, ensure the image is uploaded to Salesforce CMS. You can do this via the "Content" tab in Salesforce CMS.
2. Create a Content Asset: In Salesforce CMS, once the image is uploaded, you can create a Content Asset to use it in different pages.
3. Access the Asset URL: After the image is uploaded as a Content Asset, Salesforce generates a public URL for the content asset. You can find this URL in the asset's properties.
4. Using the URL: This URL can be used to display the image on a record page or any other page that supports external image links.

Hello @Mariza Mejia

Handling ZIP+4 codes in Salesforce can be tricky since the standard address fields (like those on Accounts) typically support only the 5-digit ZIP code. However, there are several approaches you can consider to work around this limitation:

1. Custom Fields Approach

• Solution: Create a custom field for the ZIP+4 code in Salesforce and store the extended 4-digit code separately.
• Advantages:
  • Simple and easy to implement.
  • Flexible, allowing you to capture both the 5-digit ZIP and ZIP+4 codes.
• Disadvantages:
  • Requires user discipline to enter the ZIP+4 code consistently.
  • You’ll need custom validation and formatting rules to ensure the correct structure for ZIP+4 codes.

2. Validation Rules

• Solution: You could create a custom validation rule for the ZIP+4 field to ensure it contains the correct format (e.g., 12345-6789).
• Advantages:
  • Ensures data integrity.
  • Helps maintain consistency in the ZIP+4 format.
• Disadvantages:
  • This does not automate the process of populating ZIP+4 values; users must enter them manually or integrate them via other tools.

3. Third-Party Integrations

• Solution: Integrate a third-party address verification and enrichment tool (such as Loqate, SmartyStreets, or Melissa) to validate and automatically populate both the 5-digit ZIP and ZIP+4 codes based on the address.
• Advantages:
  • Automates the process, ensuring accuracy and reducing manual entry errors.
  • Some integrations can even automatically update ZIP+4 codes based on the full address entered.
• Disadvantages:
  • This could incur additional costs for the third-party tool.
  • May require additional setup and ongoing maintenance.

4. Custom Address Formatting

• Solution: Use a custom address field with a formula or trigger to combine the ZIP+4 extension with the standard ZIP code.
• Advantages:
  • Customizable for specific business needs.
  • You can display the full ZIP+4 code in a user-friendly format.
• Disadvantages:
  • May require development resources to implement.
  • Might add complexity to data maintenance.

5. Custom Address Component (LWC)

• Solution: If you're building a custom UI or app, consider developing a custom Lightning Web Component (LWC) that can capture both the 5-digit ZIP and the 4-digit ZIP+4 extension together. You can also handle validation and formatting directly in the component.
• Advantages:
  • Full control over the input experience and validation.
  • Can integrate with address APIs for auto-population.
• Disadvantages:
  • Requires development effort for the component.
  • Complex if you're dealing with large amounts of address data.

Each of these methods has its pros and cons, so it really depends on your specific requirements, budget, and technical capabilities. If you're looking for a quick solution, a custom field and validation rule might be the best option, while integrations can help automate the process if you’re looking for scalability.

Hello @Paul Stewart

You can't show the information icon only on one page layout if the Priority field is set as "Always on Layout."

Here are two solutions:

1. Dynamic Forms (if available): Use Dynamic Forms to control field visibility based on the Record Type. This way, you can show a custom field with the icon only on the desired layout.
2. Custom Field: Create a new custom field with the information icon, hide the original Priority field on the layout, and show the custom field instead.

These methods let you display the icon only where needed.