Are you ready to elevate your Salesforce data modeling expertise? Dive into our latest blog post where we present a challenging practice question designed to put your skills to the test. Explore real-world scenarios, fine-tune your understanding of Salesforce data structures, and gain valuable insights into effective data modeling practices. Whether you’re a seasoned Salesforce professional or just starting, this practice question is your key to honing your skills and enhancing your ability to design robust, scalable data models. Uncover best practices, overcome common challenges, and level up your Salesforce game with our engaging and practical data modeling exercise. Get ready to transform your approach to data modeling and take your Salesforce proficiency to new heights!”
- Create a custom object named “Project” with the necessary fields to track project details.
- Add a lookup relationship to link the Project object to the Account object.
- Create a record type for the Case object that is specific to handling customer feedback.
- Develop a validation rule for the Lead object that requires a phone number to be entered if the Lead Status is set to “Contacted.”
- Create a validation rule for an Expense object to ensure that an Expense date field is not more than 30 days in the past.
- Develop a validation rule for an Account object to ensure that an Account Name field contains at least three words.
- Create a validation rule for the Opportunity object that prevents the close date from being more than 90 days in the past.
- Create a record type for the Task object to distinguish between different types of tasks (e.g., follow-up, meeting, etc.) and customize page layouts accordingly.
- Create a custom object named “Feature Request” to track customer feature requests, including relevant fields such as “Feature Name,” “Requester Name,” and “Status.”
- School System Management:
- Create an Application Called School Management. And add all objects in this application.
- Create Three Objects
- School
- School Name
- Address
- Phone number
- District (Picklist) Use field dependency district————-State
- State (Picklist)
- URL
- Total number of students (roll up summary (count) )
- Highest marks taken student ( roll up summary ( max) ) -Marks field
- Student
- Student Name
- ID (Auto number)
- Phone number
- School Name (Relationship field use master-detail)
- Parents Name (Relationship field use Lookup)
- Class
- Results (Picklist Pass and Fail)
- Subjects (Take multi picklist max 6 subjects are taken for student)
- Marks (Number datatype {max 600 marks} (If the student fails it should be 250 below) )
- Parents
- Parents Name
- Address
- Phone number
- Income (Take picklist agriculture, govt job, business )
- Single parent (Check box field)
- School
- Car Rental Service Application:
- Create an Application Called Car Rental Service. And add all objects in this application.
- Object Name
- Contact
- Name (Text)
- Phone (Phone)
- Email (Email)
- Driving License (Text)
- Driving Experience (Number)
- Ratings given (Roll up Summary)
- Bookings made (Roll up Summary)
- Payment – To store the payment details
- Car Id (Lookup)
- Customer ID (Master Details)
- Booking Id (Lookup)
- Payment Date (Date)
- Amount (Number)
- Credit Card Number (Text Encrypted)
- Card Owner Name (Text)
- Card Expiry Date (Date)
- CVV Number (Number)
- Status (Picklist- Pending, Done)
- Payment ID (Auto Number)
- Car – To Store Car Details
- Car Types: (Picklist)
- Mini
- Electric
- Go
- Prime
- XL
- Rental
- Car Name (Text)
- Model Number (Text)
- License Number (Text)
- Car Model Year (Number)
- Fuel Type (Picklist- Petrol, Diesel, CNG Gas, Electric)
- Number of Cars Available (Number)
- Avg. ratings (Picklist – 1, 2, 3,4,5)
- Car ID (Auto Number)
- Charge Per Day (Number)
- No of Rating of the Car (Roll-up Summary)
- No of Bookings (Roll up Summary)
- Car Types: (Picklist)
- Booking – To store the Booked Car details
- Contact Name (Master-Detail)
- Car Name (Master-Detail)
- Hire Date (Date)
- Return Date (Date)
- Status (Picklist – Booked, Not Booked )
- Payment Id (Lookup)
- Approval Status (Approved, Pending, Rejected)
- Car Returned (Checkbox)
- Penalty per day (Formula Field) Calculate penalty based on car type
- Penalty for late return (Formula Field) Calculate the penalty for the number of days after the date of return
- Tax (Formula) Calculate tax based on car type
- Fare (Formula) Calculate the total fare for the late return bookings
- Booking ID (Auto Number)
- Review – Store the customer review regarding the cars and the Booking
- Customer Name (Master-Detail)
- Booking Id (Lookup)
- Car Id (Master-Detail)
- Rating (Picklist – 1, 2, 3,4,5)
- Date (Date)
- Review (Long Text Area)
- Contact
- Validation Rules
Booking object:
- A car cannot be booked if it is not available
- A car cannot be booked if the customer does not have a driver’s license
- The car cannot be booked for more than 7 days
- The date of return should not be less than the date of hire
- If the car name is Benz, then the system admin only creates the record
- The payment amount and fare amount should be equal
Payment Object:
- Check the no of available cars and when a booking is made for the car
- Send an Email to the customer before 12 hours of the date of return
- Send an email to the customer after booking to make the payment with the booking ID and the fare amount
- When the car type is van submit for approval process
- Send confirm mail to the customer for the booking
- When payment status is processed, change booking status to confirmed
- Change the booking status to complete when the car is returned
One Response
Wow! Thank you! I continuously needed to write on my blog something like that. Can I include a fragment of your post to my site?