#Salesforce Developer429 人正在讨论

Hi @Shubham Baghel

, 

There are several secure ways to store files outside Salesforce while still reaching them from inside it, and the best one depends on how your files are used.

The easiest option, with the least effort, is

If you have a very large volume of files and want the cheapest storage,

A third route is a ready-made

Before any of these, do a

Settle a few security points upfront:

• Access model: should access follow Salesforce sharing or the external system's permissions? A mismatch between the two can expose data.
• External users: if Experience Cloud Guest or external users are involved, their file access needs a dedicated security review.
• Links and credentials: never use public buckets or long-lived public links, and keep credentials in Named Credentials rather than hardcoding them.
• Compliance: check retention, data residency, and audit-logging requirements.
• Migration: test in a sandbox first, with a rollback plan, because existing records need to be relinked to the moved files.

I hope you find the above information helpful. If it does, please mark it as Best Answer to help others too.

Hi @Tarun P Good question! I have seen many Salesforce freshers prepare well technically but make a few common mistakes during interviews.

Here are my suggestions:

1. Only learning definitions: Don't just explain what Flow, Trigger, OWD, or Sharing Rules are. Be ready to explain where and why we use them.
2. Lack of hands-on practice: Interviewers often ask scenario-based questions. Practice building solutions in your Developer Org.
3. Ignoring Salesforce security: Understand Profiles, Permission Sets, OWD, Role Hierarchy, and Sharing Rules with real examples.
4. Not understanding Flow vs Apex: Know when to use Flow and when custom Apex development is required.
5. Poor project explanation: Be ready to explain your project requirements, objects, automation, security, and challenges.
6. Giving memorized answers: Try to explain concepts in your own words rather than repeating textbook definitions.
7. Ignoring basic SOQL and Apex: For Developer roles, practice SOQL, Triggers, Bulkification, Collections, and Governor Limits.
8. Not saying "I don't know": If you don't know an answer, be honest and explain how you would approach the problem.
9. Poor communication: Practice explaining technical concepts in simple English with confidence.
10. Mentioning fake experience: Never add fake project or company experience. Genuine hands-on knowledge matters more.

My suggestion: Focus on strong fundamentals, build 2–3 practical projects, and attend mock interviews regularly.

Remember, interviewers don't expect freshers to know everything. They want to see your understanding, problem-solving skills, and willingness to learn.

All the best for your Salesforce journey! 

Hi Rani kumari, Since you already have Salesforce Admin certification, I suggest focusing on practical knowledge.

1. Hands-on Practice: Focus on Security, Flows, Reports, Dashboards and Data Management.
2. Real-Time Projects: Build 2–3 projects with real business scenarios.
3. Interview Preparation: Practice scenario-based questions regularly.
4. Resume & LinkedIn: Highlight your certification, projects and transferable skills.
5. Job Applications: Start applying for Junior Admin, Salesforce Support and entry-level roles.

Don't depend only on certification. Focus on hands-on experience and confidence in explaining business scenarios.

Your non-IT experience can also be an advantage, especially if you understand business processes.

Hi @ATU PANDU Salesforce Global Search doesn't support restricting searches to only Email and Phone fields for specific users.

A few options to consider:

1. FLS: Remove access to State and Address fields if agents don't need them.
2. Search Manager: Check whether unwanted fields can be excluded from search indexing.
3. Search Layouts: These control which fields appear in results, not which fields can be searched.
4. Custom LWC with Apex: Build a search component that allows agents to search Opportunities using only Email or Phone.

Since agents still need access to SA1 records, a custom LWC would be a good option.

Important: Custom search alone won't restrict standard Global Search. You'll also need to review field permissions and other available search paths.

Hope this helps!

Hi Chromer, This error usually happens when Salesforce doesn't allow changes to the current agent version. 

Try these steps:

1. Check if the agent is active. Deactivate it before making changes.
2. Refresh Agent Builder and try publishing again.
3. Check if any deployment or publishing process is still running.
4. If possible, try creating the agent again in a fresh Trailhead org.
5. If the issue continues, raise a Trailhead support case with the error and request ID.

It could also be a temporary Salesforce platform issue.

Hope this helps!