madhulika shah
IndividualForum Replies Created
-
Hi Prachi,
Beyond setting the organization-wide sharing defaults for each object, you can specify whether users have access to the data owned by or shared with their subordinates in the hierarchy. For example, the role hierarchy automatically grants record access to users above the record owner in the hierarchy. By default, the Grant Access Using Hierarchies option is enabled for all objects, and it can only be changed for custom objects.
To control sharing access using hierarchies for any custom object, from Setup, enter Sharing Settings in the Quick Find box, then select Sharing Settings. Next, click Edit in the Organization-Wide Defaults section. Deselect Grant Access Using Hierarchies if you want to prevent users from gaining automatic access to data owned by or shared with their subordinates in the hierarchies.
Hope this helps.
-
Hi Prachi,
Various Dashboard Components are:
1. Chart: Use a chart when you want to show data graphically.
2. Gauge: Use a gauge when you have a single value that you want to show within a range of custom values.
3. Metric: Use a metric when you have one key value to display.
- Enter metric labels directly on components by clicking the empty text field next to the grand total.
- Metric components placed directly above and below each other in a dashboard column are displayed together as a single component.
4. Table: Use a table to show a set of report data in column form.
5. Visualforce Page: Use a Visualforce page when you want to create a custom component or show information not available in another component type.
6. Custom S-Control: Custom S-Controls can contain any type of content that you can display or run in a browser, for example, a Java applet, an ActiveX control, an Excel file, or a custom HTML Web form
-
Hello Prachi,
A commit is described by a parent commit and a set of file modifications. This is enough to represent the version of the code at this commit. Indeed to find the code at this commit, you take the code from the parent commit and apply it the given set of modifications. This allows to keep a complete history of your code without having to store individually each version of each file. The file modifications are mainly add a line in a file, and delete a line. You can also rename a file, add a new file and delete a file.
A commit also contains informations about the author, the creation date and the message which was published with. A commit is identified by a hash, which is used in git commands to refer to this particular commit.
-
Hello Chanchal,
It takes 12 hours to delete an Active Process.
Thanks.
-
Hi Shradha,
Single emails are like regular individual emails that may go to one or more addresses (to/cc/bcc), but each of these emails has the same body whereas mass emails typically go to a large number of addresses (currently capped to 250 per email), with personalized message bodies.
-
Hi Avnish,
This is generic error message prompted by Salesforce many times, which is not well informative. To get informative message, we can try to delete same record in "Developer Console". In Developer Console Debug log, we will get exact error message.
Example : Lets say there is one record which is parent of more than 2000 records and grand parent of 5000 records. In such scenario from developer console it gives error something like "record cannot be deleted because it has many associated objects" However in User Interface, it will just display that "Object cannot be deleted". -
Hello Prachi,
Comparison between JSON and XML is given below:
- Simplicity: XML is simpler than SGML, but JSON is much simpler than XML. JSON has a much smaller grammar and maps more directly onto the data structures used in modern programming languages.
- Extensibility: JSON is not extensible because it does not need to be. JSON is not a document markup language, so it is not necessary to define new tags or attributes to represent data in it.
- Interoperability: JSON has the same interoperability potential as XML.
- Openness: JSON is at least as open as XML, perhaps more so because it is not in the center of corporate/political standardization struggles.
These are the reasons why one must use JSON over XML.
-
Hello Shradha,
Please refer to the link provided:
-
Hello Anjali,
Salesforce CPQ may be the only CPQ solution in the market with the concept of time built in. This is ideal for use cases such as subscriptions or other similar recurring sales models.
There's one more area where this concept of time is critical: renewal opportunities and quotes. Salesforce CPQ enables you to automate these as well. When renewals are in play, Salesforce CPQ automatically creates a renewal opportunity and quote so reps don't have to. On top of that, Salesforce sends the team a reminder when the renewal is coming up. All they have to do is jump into the new opportunity, ensure the data is correct (data is carried over from the original opportunity and quote), and then execute.
-
Hello Anjali,
One of the important aspects of REST (or at least HTTP) is the concept that some operations are idempotent. An idempotent method means that the result of a successful performed request is independent of the number of times it is executed.
-
Hello Shradha,
If we want to avoid the query we can use:
Id devRecordTypeId = Schema.SObjectType.Account.getRecordTypeInfosByName().get('Development').getRecordTypeId();
Here, 'Development' is the record type's name. You should use anything. Also, you will have to specify your SObject type, here I have mentioned Account.
-
Hi Shradha,
apex:PageMessages:
This component displays all messages that were generated for all components on the current page, presented using the salesforce styling. This will display both salesforce generated messages as well as custom messages added to the ApexPages class
apex:PageMessage:
apex:PageMessage is a component that adds a single message on the page. This is used to display a custom message using the salesforce formatting
apex:Message:
apex:Message is used to display an error on only a specific field. It is used to allow developers to place field-specific errors in a specific location.
apex:Messages:
apex:Messages is similar to apex:Message but it displays all errors.
-
Hi Avnish,
End user must needs to have “Apex Author” permission and this is something should not be granted to end user. Also, while creating JavaScript button, user must be aware that its only supported in Salesforce classic and not in Salesforce Lightning.
-
Hi Anurag,
we need to authorize the endpoint Address in SOAP Callout because we need security at Salesforce. So, any time you make a callout to an external site salesforce want to make sure that it is authorized. We can’t have code calling out willy-nilly to any endpoint without prior approval. Before you start working with callouts, update the list of approved sites for your org on the Remote Site Settings page.
-
Hi Shradha,
You can import Salesforce data extensions into the Marketing Cloud through Interactions and Automation Studio. Create import activities with accessible Sales or Service Cloud reports. For example, if you can’t access a report in Marketing Cloud, you can’t access it in the Marketing Cloud Admin folder of Sales or Service Cloud.
Manual and automated imports behave differently in scope-by-user accounts:
Manual import activities respect scoping, so the number of records that appear in the report are specific to the user who is running the import.
All automated import activities are executed as the Marketing Cloud API User. Therefore, the number of records reflect the Salesforce system user’s (tracking user) level of access to data.
-
Hi Avnish,
Permission sets only provide general permissions to objects. Creating a permission set is like extending a profile. If your org wide sharing rules for an object are set to private then creating a permission set with create/read/write on that object will only allow them to create and manage their own records and not records owned by other users. If you want them to be able to edit/update other users records then those records need to be shared with tem. You provide access to records, as you have already kind of figured out, using sharing rules.
-
Hi Avnish,
Currency field type allows user to enter INR or any other country currency values in the record whereas Number data type allows users to enter numbers.
-
Hi Chanchal,
Yes, we can deploy the object data and custom setting data with the help of change set.
-
Hi Anjali,
Salesforce have added a new lightning component called lightning:tree, using this we can display the hierarchy of Salesforce. To know how to implement it and how it works, kindly refer to the link provided:
https://cloudyabhi.blogspot.com/2017/09/lightningtree-to-display-account.html
-
Hi Prachi,
Expressions allow you to make calculations and access property values and other data within component markup. Use expressions for dynamic output or passing values into components by assigning them to attributes.
An expression is any set of literal values, variables, sub-expressions, or operators that can be resolved to a single value. Method calls are not allowed in expressions. -
Hi Shradha,
Referring to passing parameters in salesforce first I want to define what actually pass by reference and pass by value means.
“Pass by Value” means when a method is called, a second copy of the parameter variable is made in memory, and this copy is passed to the method as a parameter. This copy can be modified in the method, but the original variable in the caller is unchanged, and the changes to the copy are lost upon return.
“Pass by Reference” means when a method is called, that actual variable is passed to the method.
For passing parameters by value and by reference in apex you can refer to the following link:
-
Hi Shradha,
Single sign-on (SSO) is a session and user authentication service that permits a user to use one set of login credentials to access multiple applications. The service authenticates the end user for all the applications the user has been given rights to and eliminates further prompts when the user switches applications during the same session. On the back end, SSO is helpful for logging user activities as well as monitoring user accounts.
Benefits of using single sign-on include:
- User passwords are not stored or managed externally.
- Reduce password fatigue from different user name and password combinations.
- Reduce time spent re-entering passwords for the same identity.
- Reduce IT costs due to lower number of IT help desk calls about passwords.
-
Hi Avnish,
It is necessary for most sales teams to use both Leads and Contacts once you convert the lead, the lead record is no longer accessible via the UI. So to access any of the personal contact information that was captured on lead records, sales team use the contact record.
-
Hi Anjali,
We need to implement the following “force:appHostable” so that we can use the component as a Tab.
-
Hi Shradha,
The limitations of data import wizard in salesforce is that you can use the Data Import Wizard if you’re importing fewer than 50,000 records.