Miscellaneous Questions
Table of contents
Objects and Relationships
How many lookup relationship and MDR can you create on single object?
Lookup : 40
MDR : 2
What if you delete child record and after that you delete parent record of that child then can you undelete the child record
- If you delete a detail record and later separately delete its master record, you can’t undelete the detail record, as it no longer has a master record to relate to.
Consider there is a lookup relationship between two object and if I share the parent record using sharing rule then will all the child record be shared or not if there is lookup relationship
- If you share the parent record using a sharing rule, it does not automatically share the child records in the lookup relationship.
Can we convert master detail relationship to lookup relationship in salesforce.
Yes, in Salesforce, you can convert a Master-Detail relationship to a Lookup relationship, but only under certain conditions. The process involves the following steps and requirements:
No roll-up summary fields
No active workflow rules or processes that reference the relationship
Can we convert lookup relationship to master detail
Yes, you can convert a Lookup relationship to a Master-Detail relationship in Salesforce, but only under certain conditions.
Child records must have a parent: All existing child records must have a value in the lookup field. If any child records have a blank parent, they must be updated before the conversion.
No existing roll-up summary fields: If there are any roll-up summary fields on the parent object, you will need to remove them before conversion.
Process Automation
- Comparision between Workflow rules and Process Builder
| Feature/Capability | Workflow Rules | Process Builder | Flow |
Purpose | Automates simple record-based actions | Automates complex processes with multiple actions | Automates processes with flexible, multi-step logic |
Actions | Field updates, email alerts, outbound messages, tasks | Field updates, create records, update records, send emails, invoke flows, call Apex, post to Chatter, delete records | Create records, update records, delete records, send emails, call Apex, invoke other flows, complex logic |
Logic Complexity | Simple (single if-else conditions) | Moderate (supports branching logic) | Highly flexible (supports complex logic with loops, branching, etc.) |
Record Deletion | Not supported | Supported | Supported |
Criteria Evaluation | Simple evaluation (record meets condition) | Multiple criteria with branching options | Complex conditions, including loops and nested logic |
Trigger Types | Record changes (create or update) | Record changes, including related objects | Record-triggered, scheduled, or user-triggered |
User Interface | Simple and easy to use | More advanced, with a visual interface | Highly visual, drag-and-drop interface for creating complex flows |
Related Record Operations | Limited to the record that triggered the rule | Can operate on related records and other objects | Full flexibility, can operate on related records and more |
Limitations | Can only perform a limited set of actions | More actions available, but can be complex to manage | Best for very complex processes; can become hard to manage at scale |
Use Cases | Simple processes like sending alerts, updating fields, and creating tasks | Processes requiring multiple actions or branching logic, such as creating records based on multiple conditions | Complex workflows requiring advanced logic, user input, or interacting with multiple objects |