Activity
Mon
Wed
Fri
Sun
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
What is this?
Less
More
Pathway To Salesforce (PTS)

978 members • Free

42 contributions to Pathway To Salesforce (PTS)
A Bit Clearer!
In the course of my learning how to execute projects, I’ve always been hindered by what order to follow in carrying out a particular project. But I’ve discovered that there’s actually no single mandatory build order that applies to any Salesforce project. However, there’s a logical dependency-based order that must be followed. One discovers this order by analyzing the project given, to understand the requirements of the said project. Those requirements determine what comes first. So, before ever you go to Setup to start any projects, ask yourself, WHAT ARE THE REQUIREMENTS! Let the coaches correct me please, if my discovery were to be wrong to any extent. @Godwin Mbah @Divine Lantum @Josephine Nti @Efetobore Igoni .
🧠 WHO CAN FIX IT? STAKEHOLDER MANAGEMENT EDITION
You are the Salesforce Administrator on a major CRM project for a national retail company. The project is almost ready for UAT when three senior stakeholders disagree on an important requirement. The Sales Director says: Every new Lead must have a phone number before Sales can progress it. The Marketing Director says: Making the phone number mandatory will reduce online Lead conversion because many prospects currently submit forms without one. The Customer Service Director says: Their team should be allowed to progress Leads without a phone number because some customers contact them through email and live chat. The Executive Sponsor then tells you: “Sales owns the Lead process. Just implement what the Sales Director requested so we can stay on schedule.” However, changing the requirement could affect Marketing conversion, Customer Service operations, reporting, and the overall customer journey. You have 48 hours before UAT. ❓ WHO CAN FIX IT? 🔥 Only ONE answer represents the strongest stakeholder management approach. Do not just comment A, B, C or D. Tell me WHY you chose your answer. Let us see who is thinking like a real Consultant. 👀
Poll
5 members have voted
🧠 WHO CAN FIX IT? STAKEHOLDER MANAGEMENT EDITION
1 like • 2d
The strongest stakeholder-management approach is C. First of all we must acknowledge that this is not primarily a Salesforce configuration problem. It is an unresolved business requirement conflict involving three different objectives: For Sales: lead qualification/progression requires a phone number. For Marketing: making it mandatory may reduce lead conversion. For Customer Service: an exception for leads originating through email/chat is needed. Whereas the Executive sponsor: wants speed, but that does not eliminate the cross-functional impacts. The option C is therefore the best because a focused alignment session brings the stakeholders together to resolve the business decision before it is encoded into Salesforce. As the administrator, your role is to make the agreed business process work—not independently decide which department's objective wins. Hence, the session should establish the actual business requirement. For example, is a phone number truly required for all leads, or only before a particular sales stage? So, the administrator should not “fix” the disagreement by choosing a side; they should create the conditions for the business owners to make an explicit and informed decision quickly. That’s why the option C demonstrates the consultant mindset. Note: Im still a beginner. I just tried to understand this task and with the help of Ai, I made the above submissions.
Team Gamma!
We are live on Team Gamma, Guys!
1
0
Salesforce Data Import- A Common CSV Import Problem (and the Fix)
⚠️ Salesforce Data Import Wizard – A Common CSV Import Problem (and the Fix). This is for all who re in the process of internalizing Data Import and getting it done accurately. It’s the result of my days of searching for what went wrong during my data import process and how I was able to fix it. Our Coaches @Godwin Mbah @Divine Lantum @Josephine Nti , kindly correct me where I might have been wrong, if any please. If your CSV imports as one unmapped field or Salesforce doesn't recognize your columns, don't panic. The problem is often caused by German Excel saving CSV files with semicolons (;) instead of commas (,), ( for those that live in Germany). Quick Fix: Open the CSV file in Notepad (Editor). Check whether the fields are separated by semicolons (;). Replace all semicolons with commas (,) and save the file. Upload the corrected CSV again. Also remember: Contact Last Name is a required field when importing Contacts. Make sure every CSV column is mapped to the correct Salesforce field before starting the import. Lesson learned: Before importing into Salesforce, always open your CSV in a text editor to confirm that the columns are comma-separated and that all required fields are present. This simple check can save hours if not days of troubleshooting.
4
0
Don’t Rush Data Import !
Data Import requires patience and being extremely careful and attentive from the onset, so as to avoid very minor mistakes that might take one, hours if not days to solve. It’s a lesson learnt. Thanks Coach @Divine Lantum for your good mentorship.
1-10 of 42
Emmanuel Njoku
4
46 points to level up
@emmanuel-njoku-8239
Very Committed to Break into the World of Tech

Active 17h ago
Joined Jun 16, 2026
Powered by