Creating and Mapping Custom Fields (Classic)

This functionality allows you in creating the required custom fields in Salesforce and then mapping it with the custom fields in RFPIO.

Permission: Users must have the privilege System Administrator in Salesforce and Company Administrator in RFPIO.

Creating Custom Fields in Salesforce

You can follow the steps below to create custom fields in Salesforce:

1. Click Setup from the top navigation bar.
2. Click Customize from the left pane.

3. Select the object type for which custom field has to be created (example: Opportunity). The list of available custom field types will be displayed as shown below:

4. Select Fields.
5. The Opportunity Fields page will be displayed.
6. From the section Opportunity Custom Fields & Relationships, click New.

The New Custom Field page will be displayed with the list of available custom fields.

7. Select the required field to be added and click Next. A page as shown below will be displayed:

8. Enter the details of the custom field and click Next.

Note: Fields marked with red are mandatory fields.

9. In the next step, specify the field level security, and click Next. For example, let us select Phone.

 

10. The Add to page layouts page will be displayed. Select the layouts to which the custom field has to be added.

 

11. Click Save.

Note: To save this custom field and create a new custom field, click Save & New.

The newly added custom field will be displayed in the Opportunity Custom Fields & Relationships section as shown below:

In a similar way you can create custom fields for Leads and Accounts.

Mapping Custom Fields from RFPIO

Custom fields created in Salesforce should be mapped to project custom fields in RFPIO for them to appear while project creation and in reports.

To map the custom fields, you can follow the steps below:

1. Login to RFPIO.
2. Click Organization settings and select PROJECT. The Organization Settings – Custom Fields page will be displayed.

3. Click ADD FIELD. The Add Custom Field page will be displayed.

4. Select the category for which the custom field has to be created.
5. Specify the Merge Tag Name.
6. Enter a Display Name for the custom field.
7. Specify a Group Name.
8. Select the Project Type for which the custom field has to be created.
9. Select the Type of the field response.
10. To make the field mandatory, select the checkbox associated with Required.
11. To associate the field with Salesforce, select the checkbox associated with Associate with Salesforce (instance). A section as shown below will be displayed:

12. Select Phone Number from the Salesforce Fields drop-down options associated with Opportunity.

Note: Here you are selecting Phone Number associated with Opportunity as the custom field Phone Number for Opportunity was already created in Salesforce. You can select any of the custom field you have created in Salesforce to be associated here, and name them accordingly.

13. Click ADD to map the custom field with Salesforce custom field. The field will be added and will be displayed in the Organization Settings – Custom Fields

14. While creating projects from Opportunity in Salesforce, the mapped field will be displayed as shown below:

 

Note: While creating the custom field in Salesforce, the field was not marked as a mandatory field. While mapping it from RFPIO, it was marked as a required field. After successful mapping, the field Phone Number is displayed under Basic Details section as a mandatory field. While creating a new Salesforce associated project from RFPIO, the value for the custom field created for that object type will be auto-populated as shown below. The value from the opportunity will be auto-filled in the phone number custom field here.   In a similar way, we can create custom fields for the object types Account and Leads. Once it is created in Salesforce, you can create custom fields in RFPIO and map it to the custom fields in Salesforce. Values will be automatically pulled from Salesforce and populated while creating projects in RFPIO.

 

 

To refer other Salesforce (Classic) documentation, click here.