An Overview of Force.com Development

The multinational enterprise software company Salesforce, widely known for its Customer Relationship Management (CRM) software, is now also providing platform-as-a-service. Salesforce is a pioneer in offering top-notch on-demand CRM software, which it refers to as “The Sales cloud.” They have expanded into on-demand customer care and support services as well (Salesforce refers to this as “The service cloud”). Cloud computing is the industry leader in today’s world. One method for migrating all of your applications to the cloud is Salesforce.com.

This page introduces the Force.com platform development:

  • Join the Developer Edition now.

Go to http://developer.force.com/join in your browser.

  • Complete the fields about you and your business.
  • Use a public email address that you can easily check from a web browser in the Email Address section.
  • Enter a distinct Username. It should be noted that this field also takes the form of an email address, but it is not required that it match your email address, and it is typically preferable if they don’t. You’re often better off selecting a username like firstname@force.com or firstname@lastname.com since it serves as both your login and your identification on developer.force.com.
  • The Master Subscription Agreement checkbox should be selected after reading. then select Registration Submission.
  • You’ll get an email with a login link shortly. Change your password by clicking the link.

Object:

  • Object in a relational database that is logically equivalent to database tables. The concept of a field in an object is comparable to a column in a relational database.
  • The object may be generic or unique. Salesforce has predefined standard objects such as Account, Contact, Lead, Case, Opportunity, etc.
  • Force.com Development Service build custom objects depending on an application’s specifications.
  • Customized items have the following qualities:
  1. Information that is particular to and significant to your organization is stored in custom objects.
  2. Custom items are reportable and searchable.
  3. Custom objects provide features for adjusting access control.
  • The un-delete feature is available on Force.com Development items. Deleted items are placed in a recycle bin with a 45-day expiration date. Objects in the recycling bin can be deleted by an administrator.
  • The Object name is used to programmatically access the object. The suffix __c is appended to the custom object names. The label name is displayed with the object.
  • Developers must enter the following fields into the object:
  1. Label
  2. Labeling in Multiples
  3. Object Description
  4. Description
  5. Record Title
  6. Type of Record
  • There are a maximum of 500 custom fields per Object.

When an object is created, a user interface for Create, Update, Read, and Delete operations is automatically built.

  • Metadata XML can be used to represent custom objects.
  • Deleted data and metadata are kept in the recycle bin.
  • Database tuning is managed by Salesforce. Salesforce controls how objects and fields are saved in the database.

Relationships between Objects:

  • Force.com Development Company India enables the creation of relationships between items. Objects’ “Custom Fields & Relationship” section is used to define object relationships.
  • Force.com Application Development offers two different types of object relationships:
  1. Relationship lookup
  2. The master-detail relationship
  • These relationships are utilized to put one-to-many relationships into action. They are added to the kid record as fields. In a Customer feedback object, for example, if one customer can have several customer feedback, we could construct a lookup (or master-detail) relationship referring to the application object.
  • If the parent record in a Master-Detail relationship is removed, all of its children’s records are also deleted.
  • There are no owners for child records in a master-detail relationship. They take over ownership of the parent record.
  • The parent field is necessary for the Master detail relationship. Also, once given, the parent field cannot be modified.
  • Standard Objects are not allowed to be on the detail side of a Master-Detail connection.
  • By default, just one field of the child item is presented in the related list section of parent objects. This is the field defined in the child object as Record Name. The search lookup layout must be changed to accommodate more fields.
  • In the master-detail relationship, rollup-summary fields are supported. The parent object can use the roll-up summary field type to conduct sum, maximum, minimum, and count operations on its children’s records. These are read-only fields that are used to calculate values from a collection of records.
  • Two master-detail objects are used to implement many-to-many relationships. One Junction object is used as the child of the objects that must form a many-to-many relationship.
  • A lookup relationship with oneself is a self-relationship. One example is an organizational chart in which an employee’s manager is also an employee.
  • Only the User object has a Hierarchy Relationship. Force.com Developer establish a manager field in the User object to relate to another object in this case.

Fields:

  • Picklist fields cannot be made compulsory.
  • When the item must be displayed, the field for the record name is displayed by default (for example in search results). Text or auto-number records can be created. Auto-number can accept values such as A-0001, A-0002, and so on.
  • The normal fields are automatically added. Standard fields include Created By, Owner, and so on.
  • Fields can be designated as unique, mandatory, or external IDs. On the edit page, a mandatory field is always visible. A record id from another system is a field of type external id. Reports and SOQL function better when fields are defined as external ids. External ids can be assigned to number, text, and email fields. Each object can have a maximum of three external identifiers.
  • Users cannot see a field that has been marked as encrypted. The encrypted field is commonly used for passwords. The encrypted fields can only be viewed by people who have the “View Encrypted Data” permission. Encrypted fields can be edited. Because this is a provided feature, you must contact Salesforce to activate it.
  • Standard picklists can be both controlling and dependent picklists. The controlling field can have a maximum of 300 values. A custom multi-select picklist cannot be the picklist’s controlling field
  • Merge fields display values determined by formula calculations
  • Force.com Development Service Providers In India allows you to track changes in field values over time. This option is available for up to 20 fields in an object.

Leave a Reply

Your email address will not be published.

Back To Top