[Manpreet]

Hi Jyoti,

try something like this-

VISUALFORCE PAGE :

 

APEX CONTROLLER

Thanks.

[Manpreet]

Hi Sidhant,

I am providing you a link .You can just filter your requirements here and you will get the desired result as per you need.

Thanks.

[Manpreet]

Hi George,

I think it would be a great initiative for SFDC professionals and beginners. You can include tips for beginners in that Platform to boost up their career in salesforce. For professionals, you can provide them a career Hierarchy and about various certifications that can boost up their Salary.

Thanks

[Manpreet]

Hi George,

I have created a Blog that offers some Hands on Development Tips that developers can use in their day to day work.Here is the link .

Thanks.

[Manpreet]

Hi Naman,

1. Get the version Id from the error message
2. Login to Workbench
3. Go to Utilities > REST Explorer >> Perform a GET
4. Add the following to the URI field and change the Id with the FlowId you are investigating /services/data/v36.0/tooling/sobjects/flow/30124000000PcNDAA0

[NOTE: v36.0 refers to the API version and as new tooling API features are released, version may need changing]

5. Click Execute
6. Open the 'attributes' folder
7. Check the 'ProcessType', if the value is 'Flow' then this is a normal flow, if the value is 'Workflow', this is a Process. Here you can also see the MasterLabel, which should provide you with the name of the flow/process.

Thanks

 

 

[Manpreet]

Hi Jayant,

Integrating Salesforce and Alfresco is not as tedious a task as it might sound.

Whenever an enterprise tries to get a foot in the market it has two prime challenges amongst the rest: one is customer relationship management and the other is document management. To conquer both these issues, we have two imperative systems, the alpha dogs in their domain right now: Salesforce and Alfresco. One is the undisputed king of customer relationship management and the other has become the synonym of document management.

 

o there's no doubt about the magical outcome when these two excellent systems join hands, unleashing the power and strengths of both the systems. However, integrating Salesforce and Alfresco is not as tedious a task as it might sound. There are two ways in which this can be accomplished:

# Integrating Salesforce with Alfresco using an app.
# Integrating Salesforce with Alfresco using RESTful API.

Integration Using App
The idea of Salesforce and Alfresco integration is so apt and lucrative that Alfresco itself came out with the flourishing idea of a Salesforce native app. It is mostly a click-and-play structure and it requires minimum or almost no coding to accomplish this integration. You just need to go to Salesforce AppExchange, install the Alfresco app, and do the necessary configurations and mappings. You'll need to create an account for both Salesforce and Alfresco. (As per your need you may also have to buy the Alfresco subscription.)

 

This method seems to be a cakewalk, so you must be wondering what is the need of a custom solution, but as the complexity of the systems increases, we need to switch to custom API solutions.

Integration Using RESTful API
Most of the medium- to large-scale enterprises opt for Salesforce Alfresco integration using RESTful APIs from both Salesforce and Alfresco. Using RESTful API also has two methods:

First, that uses CMIS (Content Management Interoperability Services) and Rest API, and
Second that makes use of custom data exchange standards.
However using the first method (CMIS standards) is more advisable. CMIS is international standard to connect two or more content management systems. CMIS is preferable as it provides the flexibility to switch from one system to another without affecting the other systems integrated with them. If you want to switch to new CRM or ECM systems in future, you just need to change the CRM or CMS and add the new system to the previous CMIS connectors, and you will have the whole new integrated system running without needing to customize the connector to facilitate the new system.

Click here for Salesforce API
Click here for Alfresco API
When we integrate Salesforce and Alfresco we get the best of both worlds, we not only get a superb workflow manager but at the same time we have an absolute document manager and lucid viewer. Alfresco provides a lot of free storage space, so you get more space to store your documents at a much lower cost. An additional factor to support their integration—apart from ease of management—is that Salesforce limits the size of files or documents to 5 MB, but in the case of Alfresco they have liberty pertaining to the size.

However, creating custom APIs is a critical and tedious task. You have to ensure that your connector API is flexible enough to accommodate changes and at the same time, it is secure enough to handle sensitive data. Simultaneously, speed should not be compromised under pressure, so it calls for expert help.

For tutorial , you can check out this video .

You can further refer to this Link.

Thanks.

[Manpreet]

Hi Mohit,

You can check with the vendor himself. This seems to be working as expected, since the vendor would have made sure you have access to only those parts of the package that you are supposed to!

Since each vendor's license management is in the context of that vendor (and some integrated systems manage licenses in their own cloud not in Salesforce), an overall 'license usage' report is probably never going to happen. You can use Permission Sets that make it easy to "Group Users using this Package", but you need a well defined licensing policy that ensures a User is added to the PermSet when they are added to a package license.

Package vendors know who they licensed users are -- and different vendors handle reporting / tracking differently. Unfortunately for us Admins, most package vendors don't make it easy.

Is your extension package actually storing the data from the original package fields in another object or fields? If so, that could be your explanation. In our org, when users need a specific value for seeing reports, we use triggers, processes or workflow rules to put those values into our own custom fields to make the data visible.

You can further refer to this link.

Thanks.

[Manpreet]

Step 1: Create the Salesforce Picklist Custom Field on Opportunity Layout

1.) In Salesforce, go to Setup > Customize > Opportunities > Fields
2.) Under Custom Fields, click New
3.) Choose the type of Picklist, click Next
4.) Enter Picklist Field Label (i.e. My Picklist)
5.) Select 'Enter values, with each value separated by a new line'
6.) Enter desired picklist values
7.) Deselect 'Restrict picklist to the values defined in the value set.' *This is important to allow Connect to update values within the list

Finish any other desired customizations, then click Next
Select desired Field-Level Security. At the very least you need to make sure the Profile your system sender user is under has Visible enabled and Read-Only disabled. Click Next
Choose desired Page Layouts, then click Save

Step 2: Create the DocuSign Custom Radio Button Group

1.) In DocuSign, go to My Preferences > Custom Fields
2.) Click Add New Field
3.) Select the Type of Radio Button from the drop-down
4.) Enter the Radio Button Group Name in the Name field (i.e. My Radio Buttons)
5.) Enter the desired Radio Button Value in the Tooltip field (i.e. Radio One)
6.) Click Save
7.) Repeat steps 2 - 6 for each Radio Button in the group. *Make sure the Name is the same name of the Group for all (i.e. My Radio Buttons)

Step 3: Create a Custom DocuSign Connect Object

1.) In DocuSign Admin go to Connect and Select your Salesforce Connect Configuration
2.) Under Connect Objects, select New Object > Salesforce Object
3.) Select Activate Object
4.) Enter a Name for your Object in the Object Name field (i.e. My Radio Button to Picklist Test)
5.) Under Select Salesforce Object, pick the Object you are sending from (i.e. Opportunity)
6.) Under Select Where > Saleforce.com Field, select Opportunity ID (id)
7.)Under Select Where > DocuSign Field, select Envelope External Source ID

8.) Under Update Fields > Saleforce.com Field, select the Picklist you created in Salesforce (i.e. My Picklist)
9.) Under Update Fields > DocuSign Field, select Recipient Secure Field, then enter the name of your Radio Button Group (i.e. My Radio Buttons)

10.) Click Save
***Now, run a test by sending from your Opportunity Object using this radio button group and completing signing. Note that the Picklist value is updated with the Radio Button value chosen during signing.

[Manpreet]

Hi Sai,

To access Salesforce we need any ADO.NET driver for this. In our sample we use the well-known RSSBus Salesforce driver referred as System.Data.RSSBus.SalesForce in the configuration file (see below). The driver must be installed on the computer, that runs the Cloud Connector, usually somewhere in the corporate network, e.g. on Windows 7.

Alternatively you can use the DEvArt ADO.NET data provider for SalesForce found here:

http://www.devart.com/dotconnect/salesforce/

The Cloud Connector is configured as follows:

_______________________________________________________________________________________________________

<?xml version="1.0" encoding="utf-8" ?>
<connection xmlns="http://www.layer2.de/schemas/cloudConnections" interval="60" version="1.2" enabled="true">

<dataEntities>
<dataEntity name="Salesforce"
provider="System.Data.RSSBus.SalesForce"
connectionString="[email protected]; Password=myPassword;
Access Token=myAccessToken"
primaryKey="Id"
selectStatement="SELECT * FROM Account">
</dataEntity>

<dataEntity name="SharePointDestination"
provider="Layer2.SharePoint.Provider"
connectionString="Data Source=https://myDomain.sharepoint.com/sites/mySite/; Initial Catalog=myList;
Authentication=Office365; User [email protected]; Password=myPassword;"
selectStatement="">
</dataEntity>
</dataEntities>
<fieldMappings autoMapping="false" >
<fieldMapping>
<field entity="Salesforce" name="ID"/>
<field entity="SharePointDestination" name="Title" />
</fieldMapping>

<fieldMapping>
<field entity="Salesforce" name="Name"/>
<field entity="SharePointDestination" name="Company" />
</fieldMapping>

<fieldMapping>
<field entity="Salesforce" name="Phone"/>
<field entity="SharePointDestination" name="WorkPhone" />
</fieldMapping>

<fieldMapping>
<field entity="Salesforce" name="BillingCountry"/>
<field entity="SharePointDestination" name="WorkCountry" />
</fieldMapping>

</fieldMappings>

</connection>

_______________________________________________________________________________________________________

 

Refer to this Link also.This is an example of integrating SharePoint with Salesforce Chatter. The SharePoint instance could be local or in a datacenter as could the Salesforce instance -- in this case we're using a hosted SharePoint instance and a hosted Salesforce instance.

Thanks.

[Manpreet]

Hi Hazel,

Step 1. Select Incoming Data Source

Begin by selecting the input file that contains the Id's of the records to be deleted.

1.) Select the file by clicking Select File
Browse to find the file and click "Open"
2.) If an .xls, .xlsx, .mdb or .accdb file has been chosen the user must select the worksheet/table name to process by clicking on it (will highlight in blue)
Click Use on the right or double click to select (the fields from the spreadsheet/table will populate in the left column of the page)
The number of records loaded will be displayed in red
Read CSV as UTF8: Select this option to force files to open in UTF-8 encoding, even if they were saved in a different format
Ensures that special characters are imported correctly

Step 2. Select the Delete Records Operation

# Deletes records for one object per pass
A Salesforce cascading delete IS performed
# Check Use Bulk API if desired
Hard Delete available ONLY when Bulk API is selected
More information on Bulk API can be found here here
Note: Hard deleted records DO NOT go the recycle bin therefore CANNOT be undeleted.

Step 3. Field Mappings

Map the Id field from the input file to the Id field in the desired Salesforce object.

Step 4. Process the Delete
To perform the chosen operation click in the lower right
> By default ALL the input rows will be processed
> When using an xls, xlsx or csv file as the input source only specific rows can be selected for processing by changing the starting and ending rows using the Control option on the right

To process the first row from a data source change the End number to 1
Start: 1 refers to the "start of data" which is actually row 2 of the input file
> Changing the Start/End values allows for testing a small portion of the input file before processing the entire file

A Status pop-up will be displayed when the operation is complete noting if there were any errors and listing any results files created (e.g. Logfile, Success/Error Files, IdSave files, Restore files). Links are provided to access the results file DIRECTLY from the status pop-up.

 

Thanks.

 

[Manpreet]

Hi Audrey,

This is an existing feature, and I know of two options that you can use. My preference is Option 1, and I've been using it on my dashboards.

Option 1:
If you want to take users to another dashboard when they click on a dashboard component, in the "Dashboard Component Edit" page simply select "Other URL" in the "Drill Down to" field and type in the URL for the 2nd dashboard in the "Drill Down URL" field. Then in the 2nd dashboard, the users can click on those components and be taken to the underlying reports.

Option 2:
In the "Dashboard Component Edit" page, you can use the "Footer" field and enter text and the URL of the 2nd dashboard. Not as fancy of a feature as Option 1, since the user will have to copy & paste the URL in their browser. And when the user clicks on the dashboard component, they will be taken to the underlying report.

Thanks.

[Manpreet]

Hi Pranav,

global class Exporter implements System.Schedulable {
global void execute(SchedulableContext sc) {
ApexPages.PageReference report = new ApexPages.PageReference('/00O500000000000?csv=1');
Messaging.EmailFileAttachment attachment = new Messaging.EmailFileAttachment();
attachment.setFileName('report.csv');
attachment.setBody(report.getContent());
attachment.setContentType('text/csv');
Messaging.SingleEmailMessage message = new Messaging.SingleEmailMessage();
message.setFileAttachments(new Messaging.EmailFileAttachment[] { attachment } );
message.setSubject('Report');
message.setPlainTextBody('The report is attached.');
message.setToAddresses( new String[] { '[email protected]' } );
Messaging.sendEmail( new Messaging.SingleEmailMessage[] { message } );

}
}

Here's an example schedulable class that might be used to email a file. Note that the last five lines need to be ignored or stripped; I'll leave this as an exercise to the reader.

 

You could also build a SOQL query, execute it, then build the CSV yourself, but that means the system is hard-coded and less flexible. Of course, you could build an interactive configuration (perhaps by the use of a custom object or custom settings), which would help work around that particular limitation of flexibility, but that is by far more complex.

Thanks.

[Manpreet]

Hi Mohit,
I have tried the below java script code in all the input fields and Command Button to avoid Enter functionality while creating the opportunity in my own visual force page.It is working very well for me.

onkeydown="if(event.keyCode==13){this.blur();actionFunction();}"

 

Thanks

[Manpreet]

Hi Ashley,

Option "Define a new report type that includes accounts and the custom object" would be Best.

1.) From Setup, enter Report Types in the Quick Find box, then select Report Types.
2.) Click New Custom Report Type.
3.) Select the Primary Object for your custom report type.

You can choose from all objects—even those you don't have permission to view. This lets you build report types for a variety of users.
Once you save a report type, you can't change the primary object.
If the primary object on a report type is a custom or external object, and that object is deleted, the report type and reports created from it are deleted.
If you remove an object from a report type, all references to that object and its associated objects are removed from the reports and dashboards based on that type.
4.) Enter the Report Type Label and the Report Type Name.
The label can be up to 50 characters long. The name is used by the SOAP API.
5.) Enter a description for your custom report type, up to 255 characters long.
6.) Select the category in which you want to store the custom report type.

Thanks.

[Manpreet]

You've just setup your Desk to Salesforce integration and now would like to bring over all of your existing cases into the related list within Salesforce, you accomplish this task using two different kind of rules and a Custom Case Field.

So let's get started with the Custom Case Field.

1.) Go to the Admin Panel → Cases → Cases → Custom Fields
2.) Click on the big green button at the top of the page to add a field:

3.)Let's name it Push To SF, and make it a checkbox:

Now if you are using the system default Case Theme then the field will show up automatically but if you are using a Custom Case Theme then you will need to add this field to your theme.

Ok now that we have added the Custom Case Field we now need to create the Case Updated Rule

We are actually going to edit the Default Salesforce Rule that is in the Case Updated "bucket".
1.) Go to the Admin Panel → Cases → Rules → Cases Updated
2.) Find the "Update Case in Salesforce" Rule and click on the cog on the right hand side to edit the rule:

3.) We are going to add two new conditions to the rule:

The first one is "Case Interaction Count" "has changed", this will indicate that something has happened to the case.

Next "Case Push To SF" "is" "True", this condition will see that the checkbox has been checked.

 

Now click on "Update".

Now for our Time Rule

1.) Go to the Admin Panel → Cases → Rules → Time Rule
2.) Click on "Add Rule" as you did before, we'll name this "Push to SF".
3.) We are going to add a condition to the "All" conditions and then two "Rule Actions"

So in the All conditions add a condition that is defined as:

"Case Labels "does not contain" "push to sf"

Now create two Rule Actions, the first rule action is to "Set Case Push To SF" "True", and then "Append Case Labels" "push to sf"

Then click on "Update"

 

Once all of your existing cases are pushed over to SF you can turn off or delete the time rule and remove the values from the Case Updated rule.

Once all references to the custom field are removed from the rules you can then delete the custom case field.

Thanks.

[Manpreet]

This is user's personal setting. I dont find any appropriate way to deselect the default record type. You have to manually do it for every user.
However to default record types, you can do that on profile level instead of doin that in user settings.

[Manpreet]

Hi,

To improve Visualforce page load times:
Cache any data that is frequently accessed, such as icon graphics.
Avoid SOQL queries in your Apex controller getter methods.
Reduce the number of records displayed on a page by: ...
“Lazy load” Apex objects to reduce request times.

For more information check with below link:
https://developer.salesforce.com/docs/atlas.en-us.pages.meta/pages/pages_best_practices_performance.htm