[Parul]

Hi Anjali,

A joined report consists of up to five report blocks, which you add to the report to create multiple views of your data. For each block, you can add regular and summary fields, create standard and cross-block custom summary formulas, apply filters, and sort columns. You apply groupings across all blocks in the report, and can add up to three groupings to the blocks, the same as for the summary format. You can also add a chart to a joined report.

Each joined report has a principal report type. By default, the principal type is the first one added to the report, and is identified in the Fields pane with a small dot beside its name. For example, if you create the joined report by selecting the Opportunities report type, and then add the Cases type, the Opportunities type is the principal report type.

Thanks.

[Parul]

Hi Anurag,

You can use this as refrence:

<apex:page controller="FetchContactvsACC_usingButton">
<apex:form>
<apex:pageBlock>
<apex:pageBlockSection >

<apex:commandButton action="{!showSection1}" value='Yes' styleClass='btn' rerender='details'></apex:commandButton>
<apex:commandButton action="{!showSection2}" value='No' styleClass='btn'></apex:commandButton>
</apex:pageBlockSection>
<apex:outputPanel id='details'>
<apex:pageBlockSection id ='newData' title='Discount Rates' rendered='{!hideshow}'>
Enter Proposal range
</apex:pageBlockSection>

</apex:outputPanel>

</apex:pageBlock>
</apex:form>
</apex:page>

 

Apex class:

public class FetchContactvsACC_usingButton
{

Boolean testval = false;
public pagereference showSection1() {
setHideshow(true);
return null; }

public pagereference ShowSection2()
{
setHideshow(false);
return null;
}

public Boolean getHideshow()
{
return this.testval;
}
public void setHideshow(boolean s)
{
this.testval = s;
}
}

 

Hope this will help you.

Thanks.

[Parul]

Hi Anurag,

You can use this as refrence:

<apex:page controller="FetchContactvsACC_usingButton">
<apex:form>
<apex:pageBlock>
<apex:pageBlockSection >

<apex:commandButton action="{!showSection1}" value='Yes' styleClass='btn' rerender='details'></apex:commandButton>
<apex:commandButton action="{!showSection2}" value='No' styleClass='btn'></apex:commandButton>
</apex:pageBlockSection>
<apex:outputPanel id='details'>
<apex:pageBlockSection id ='newData' title='Discount Rates' rendered='{!hideshow}'>
Enter Proposal range
</apex:pageBlockSection>

</apex:outputPanel>

</apex:pageBlock>
</apex:form>
</apex:page>

Apex class:

public class FetchContactvsACC_usingButton
{

Boolean testval = false;
public pagereference showSection1() {
setHideshow(true);
return null; }

public pagereference ShowSection2()
{
setHideshow(false);
return null;
}

public Boolean getHideshow()
{
return this.testval;
}
public void setHideshow(boolean s)
{
this.testval = s;
}
}

 

Hope this will help you.

Thanks.

[Parul]

Hi Anjali,

Sales Analytics app brings the power of Analytics to Sales Cloud on any device that supports Analytics. With intuitive visualizations based on your Salesforce data, Sales Analytics lets you move from insight to action quickly and helps you turn data into smarter sales.

Sales cloud reports that help sales personnel continuously monitor and interpret their sales pipeline, team performance, forecasts, activities, customers, and more. User can find the analytics and reports throughout the applications. In addition, they can schedule reports and create briefing books with report data.

 

Thanks.

[Parul]

Hi Chanchal,

 

All you need to do is navigate to the custom object and change field type from Auto Number to Text. After the change, the old/existing records would still keep their Auto Number values so you needn’t worry about losing historical data.

The only thing that I would be worried about is any apps/workflow rules /processes working off the Auto Number field increments. If you don’t have those in your org, then go ahead and make the change.

 

Thanks.

• This reply was modified 6 years, 2 months ago by  Parul.

[Parul]

Hi Anurag,

All you need to do is navigate to the custom object and change field type from Auto Number to Text. After the change, the old/existing records would still keep their Auto Number values so you needn’t worry about losing historical data.

The only thing that I would be worried about is any apps/workflow rules /processes working off the Auto Number field increments. If you don’t have those in your org, then go ahead and make the change.

Thanks.

[Parul]

Hello Shradha,

Action poller acts as a timer in visualforce page. It sends an AJAX request to the server according to a time interval (time interval has to be specified or else it defaults to 60 seconds). Each request can result in a full or partial page update.
In this article I will demonstrate how to use actionpoller in visualforce page.

In the action attribute a controller method gets called. The method gets called with a frequency defined by the interval attribute which has to be greater than or equal to 5 seconds.
Time out can also be specified as an attribute in actionpoller. Once the time out point is reached it stops making AJAX callout to the server and controller method is no more called.

 

Thanks.

[Parul]

Hi Anurag,

Account hierarchies display accounts related via the Parent Account field. To maintain a complete account hierarchy, enter an account in the Parent Account field for every account except the one at the top of the hierarchy.
From Setup, in the Quick Find box, enter Account Settings and then click Account Settings.
Select Show View Hierarchy link on account pages in Salesforce Classic.Whenever an account is related to another account via the Parent Account field, the account detail page includes a View Hierarchy link.

 

Thanks.

[Parul]

Hi Madhulika,

WSDL : Salesforce provides a WSDL (Web Service Description Language) files. A WSDL is an XML-document which contains a standardized description on how to communicate using a web service (the Salesforce API is exposed as a web service).  The WSDL is used by developers to aid in the creation of Salesforce integration pieces. A typical process involves using the Development Environment (eg, Eclipse for Java, or Visual Studio for .Net) to consume the WSDL, and generate classes which are then referenced in the integration.

SOAP :The Force.com SOAP API (formerly known as the Force.com Web Services API) lets you integrate Force.com applications that can create, retrieve, update, or delete records managed by Salesforce, Force.com, and Database.com, records such as accounts, leads, and custom objects. With more than 20 different calls, SOAP API also lets you maintain passwords, perform searches, and much more. You can use the SOAP API with any programming language that supports Web services.

[Parul]

Hi Avnish,

Manual Sharing : Manual sharing lets record owners give read and edit permissions to users who might not have access to the record any other way.

Manual sharing is to share a record to a particular user manually.

Go to detail page of record and click on manual sharing button and assign that record to other user with Read or Read/Write access.

Manual Sharing button enable only when OWD is private to that object.

 

Thanks.

[Parul]

Apex:commandLink>:This tag creates a link that helps to execute an action defined in a controller.  Normally action can be executed using buttons but in situations where you need links to be placed on your page we can use this tag. Similar to the command button tag action method, this links also transfers control to a different and then either refreshes the current page, or navigates to a different page based on the PageReference variable that is returned by the action. An < apex:commandLink > component must always be a child of an < apex:form > component.

To add query string parameters to an < apex:commandLink >, specify them in the associated action method attribute.

Syntax:
<apex:commandLink action="{!save}" value="Save" id="theCommandLink"/>

Apex:outputLink – The <h:outputLink> renders a fullworthy HTML <a> element with the proper URL in the href attribute which fires a bookmarkable GET request. It cannot directly invoke a managed bean action method.

<apex:outputlink value=”https://www.google.co.in”> Google </apex:outputlink>

<apex:outputlink value=”/{!r.Id}”> {!r.Name} </apex:outputlink>

 

Thanks.

[Parul]

Hi Avnish,

Complexity. For small businesses, Salesforce’s greatest strength is also its weakness. Since it is such a robust solution, it is a good choice for many growing small businesses. However, the tool may be overwhelming for those with microbusinesses that do not really need such a complex software solution. This is especially the case for small companies that may not have a dedicated sales staff or already possess their special lead-generation and sales solutions that perfectly work for them.

Pricing. For some small businesses, pricing may also be an issue. Although the helpdesk solution offers affordable prices even for small businesses, the problem may happen when it comes customizing the software and if you prefer using third-party solutions.

In addition, if you or your agents lack the basic skills to customize or implement the helpdesk solution, there are add-on costs for your business so you can hire developers who will tinker the system for you. Small business owners claim information technology costs can reach up to hundreds of dollars, even tens of thousands of dollars, from those who are skilled enough to help them with the helpdesk software program.

Uncontrolled administration. Users also complain that Salesforce can turn your work environment into a nightmare because its administration features can be uncontrolled.

Problematic technical support. Businesses also complain that the helpdesk solution offers problematic technical support, especially the tool’s sales reps change from time to time easily.

Tricky reporting. When you use Salesforce, sometimes reporting even just basic information can be very tricky. Generating reports, compared with the rest of the helpdesk solution’s features, is not as user friendly.

[Parul]

Hello Avnish,

This is the solutions of problem :

<apex:includeScript value="//code.jquery.com/jquery-1.10.2.js"/>
<apex:includeScript value="//code.jquery.com/ui/1.11.2/jquery-ui.js"/>

hope this will help you to in future.

Thanks.

[Parul]

Hello Shradha,

There are 5 levels :

Debug, Fine, Finer, Finest, Internal.

but user don't see debug statements in levels "Info" or lower.

So, there are 3 levels: Info, Warn, Error

 

Thanks.

[Parul]

Hello Shradha,

By querying CustomObject__share we can manually shared with the current user in Apex.

 

Thanks.

[Parul]

Hello Avnish,

For overriding a related list button we have to use standard list controller. The syntex used in defining this standard list controller is same as standard controller. That is, we need not write it as standardlistcontroller in page tag, but we have to use "recordSetVar"  attribute. This variable indicates that the standard controller is a list controller. Also this variable can be used to access the selected record in related list.
To use standard list controller define the page attribute as below (example on contact)
<apex:page standardController="Contact" recordSetVar="LisRecs" extensions="relatedListoverideController">
In the following example a "list button" created on contact is overridden with following visualforce page that shows the selected contact records in related list (example contact related list on a account record).

Thanks.

[Parul]

Hi Avnish,

The first extension takes precedence over the second extension, so the first method  of first extension will be called first and then second one.

Thanks.

[Parul]

There are three steps to add Lightning components to a Visualforce page.

1.Add the Lightning Components for Visualforce JavaScript library to your Visualforce page using the <apex:includeLightning/> component.
2.Create and reference a Lightning app that declares your component dependencies.
3.Write a JavaScript function that creates the component on the page using $Lightning.createComponent().

 

Thanks.

[Parul]

Hello Prachi,

Approval process is an automated process and your organization can use to approve records in Salesforce, An approval process is combination of steps for a record to be approved and person has to approve it each step.A step can apply to all the records to that object or just record that meets the certain criteria. An approval process also specifies the actions to take when a record is approved, rejected, recalled, or first submitted for approval.

 

Thanks.

[Parul]

Hello Prachi,

Salesforce approval process is an automated process and your organization can use to approve records in Salesforce, An approval process is combination of steps for a record to be approved and person has to approve it each step.A step can apply to all the records to that object or just record that meets the certain criteria. An approval process also specifies the actions to take when a record is approved, rejected, recalled, or first submitted for approval.

 

Thanks.

[Parul]

Hello Avnish,

No, With Permission Sets, you can open up the permissions but not restrict.

Thanks

[Parul]

Hello Chanchal,

This error is caused by a line of code that is trying to use an object that has not been instantiated, or an object’s attribute that has not been initialized.

NOTE: If the field Site was left empty, it will generate the error message as well.

 

Thanks.

Parul

[Parul]

Hello Chanchal,

The exception is because of you are not getting any record in your SOQL query..

which meet the where criteria so it's give error.

Thanks.

Parul

• This reply was modified 6 years, 2 months ago by  Parul.

[Parul]

Hello Madhu,

Apex class always execute in system mode i.e. Apex code has access to all objects and fields irrespective of the logged in User. Example - lets consider you have VF page in which you are showing certain fields as columns. Lets see one column says "Sales Rep Performance" which displays a flag in red, green and yellow. Now ideally this field should not be visible whenever a Sales Rep accesses this page (consider this as business requirement). But it is always visible if the class has no keyword specified or if a class has without sharing specified.

Now once the class is "with sharing" the object permissions, field-level security, sharing rules are applied for the current user and fields which should not be visible/accessible and not visible or accessible.

Important -

If a method is defined in a class declared with 'with sharing' is called by a class declared with 'without sharing', the method will execute with sharing rules enforced.
The class doesn’t enforce sharing rules except if it acquires sharing rules from another class. Ex. Class A (with sharing) calls a method from Class B(Without sharing) then complete context is 'with sharing'
Inner classes do not inherit the sharing setting from their container class.

So,  ''without sharing" keywords to ensure that Apex scripts do not enforce the sharing rules of the running user.

Thanks

Parul Singh

[Parul]

Hello Anurag,

 

Bulkifying triggers means making sure the trigger can operate when multiple (hundreds) of records are passed in at once.

When a trigger fires, you get your "list" of objects in Trigger.new (and some other lists/maps).

Typically when you imagine a trigger firing, you do so thinking that a user has just affected one record, and so this list has one item in it. but in reality, Salesforce could send up to 200 records into the trigger in one list. If you are data loading, or mass updating (or many other things) - this can result in all the items being sent to the trigger in one go.

So, if you had a trigger, that took the Trigger.new list, and did a for() loop through the items and executed a SOQL query to load some data for each record, because there are govenor limits (https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_gov_limits.htm) in Salesforce - if the trigger.new list had more than 100 items in it, the trigger would completely fail - because you made too many SOQL querys, and your data update/insert would be rolled back.

Making sure these problems don't exist is bulkifying triggers - ie. making sure they can work with multiple (bulk loads) of data.

There is literally tonnes of blog posts and developer articles on this topic all over the internet:
https://www.google.co.uk/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=salesforce+bulkify+trigger (https://www.google.co.uk/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=salesforce+bulkify+trigger)

Including an official Salesforce post here:
https://developer.salesforce.com/page/Best_Practice%3A_Bulkify_Your_Code

 

Thanks

Parul