Forum Replies Created

Page 12 of 12
  • Nikita

    Member
    August 13, 2019 at 6:44 am in reply to: What are types of variables in Mule 4 in Salesforce?

    Hi Gursimran,

    Mule 3 has 3 different types of variables:

    1. Flow variable
    2. Session variable
    3. Record variable

    However, in Mule 4, the record variable is not there.

  • Hi Yogesh,

    Time-dependent actions are executed at a specific time, such as 10 days before a record’s close date. When that specific time passes, the workflow rule re-evaluates the record to make sure that it still meets the rule criteria. If the record does, the workflow rule executes those actions.

    For more detail, you can also refer https://help.salesforce.com/articleView?id=workflow_time_dependent.htm&type=5

  • Hi,

    Get (getter) method is used to pass value from controller to VF page while set (setter) is used to set the value back to the controller variable.

  • Nikita

    Member
    August 13, 2019 at 6:17 am in reply to: What is a wave analytic app/ application in Salesforce?

    Sales Wave Analytics, allows sales teams to manage forecasts, pipelines, team performance and more, in order to accelerate business growth. The app is also designed to promote greater productivity by making the Salesforce app even more tightly integrated with everyday sales tasks, such as using Salesforce 1 to manage customer contacts. The Wave app works natively in Salesforce 1, a customer relationship management CRM app in which salespeople are already working, so they don't have to click between multiple applications to analyze data and then take action.

  • Nikita

    Member
    August 13, 2019 at 6:13 am in reply to: What are the limitations of Viewstate in Salesforce?

    Hi Piyush,

    Salesforce allows Visualforce pages to have a maximum view state size of 170KB.

  • Nikita

    Member
    August 12, 2019 at 1:20 pm in reply to: What is the use of @IsTest(SeeAllData=true) Annotation in Salesforce?

    Hi Prachi,

    You can use the @isTest(SeeAllData=true) annotation to grant test classes and individual test methods access to all data in the organization. The access includes pre-existing data that the test didn’t create.

    If a test class is defined with the @isTest(SeeAllData=true) annotation, the annotation applies to all its test methods. The annotation applies if the test methods are defined with the @isTest annotation or with the (deprecated) testMethod keyword.

    The @isTest(SeeAllData=true) annotation is used to open up data access when applied at the class or method level. However, if the containing class has been annotated with @isTest(SeeAllData=true), annotating a method with @isTest(SeeAllData=false) is ignored for that method. In this case, that method still has access to all the data in the organization. Annotating a method with @isTest(SeeAllData=true) overrides, for that method, an @isTest(SeeAllData=false) annotation on the class.
    @isTest(SeeAllData=true) and @isTest(isParallel=true) annotations cannot be used together on the same Apex method.

  • Nikita

    Member
    August 12, 2019 at 12:57 pm in reply to: Which are the types of custom settings in Salesforce?

    Hi Prachi,

    Custom settings are similar to custom objects. Application developers can create custom sets of data and associate custom data for an organization, profile, or specific user. All custom settings data is exposed in the application cache, which enables efficient access without the cost of repeated queries to the database.

    There are two types of custom settings.

    List Custom Settings
    A type of custom setting that provides a reusable set of static data that can be accessed across your organization. If you use a particular set of data frequently within your application, putting that data in a list custom setting streamlines access to it. Data in list settings does not vary with profile or user but is available organization-wide. Examples of list data include two-letter state abbreviations, international dialing prefixes, and catalog numbers for products. Because the data is cached, access is low-cost and efficient: you don't have to use SOQL queries that count against your governor limits.

    Hierarchy Custom Settings
    A type of custom setting that uses a built-in hierarchical logic that lets you “personalize” settings for specific profiles or users. The hierarchy logic checks the organization, profile, and user settings for the current user and returns the most specific, or “lowest,” value. In the hierarchy, settings for an organization are overridden by profile settings, which, in turn, are overridden by user settings.

  • Nikita

    Member
    August 12, 2019 at 12:38 pm in reply to: How to style Visualforce pages in Salesforce?

    hi Hariom,

    In the visulforce page you can use html tags to resize the page such as:
    <font size="1" color="blue"> <b> Your text here </b> </font>

  • Nikita

    Member
    August 12, 2019 at 6:11 am in reply to: What is target attribute and fields in force:recordData represents?

    Hi Piyush,

    targetAttribute– attributes starting with target indicates values to be returned from Data Service. It can return record or error.
    targetFields – provides the simplified view of the record field and as well as it automatically updates when the changes are detected.

  • Nikita

    Member
    August 12, 2019 at 6:00 am in reply to: Can you report or otherwise build list by User License Type?

    Hi Yogesh,

    You can create a custom formula field on the object that has this as the formula:

    Profile.UserLicense.Name

     

  • Nikita

    Member
    August 9, 2019 at 11:25 am in reply to: What is the use of testSetup in Salesforce?

    Hi Saddam,

    Apex has introduced a new method in Test class known as “Test Setup”. It needs to be marked with @testSetup annotation in Test class. Methods defined with the @testSetup annotation are used for creating common test records that are available for all test methods in the class.
    One Test class can have only one @testSetup method. These test setup methods are implicitly invoked before each test methods.
    These methods can be used to create test records specific to Test class. It helps to keep Test classes isolated and independent of helper or utility classes. If an error occurs in the setup method then the entire test class fails. If the non-test method is called from the setup method then no code coverage is calculated for non-test method.

    • This reply was modified 5 years, 3 months ago by  Nikita.
  • Nikita

    Member
    August 9, 2019 at 5:27 am in reply to: Different tools used for deployment in salesforce platform.

    Hi Piyush,

    Following tools are mostly used for deployment in Salesforce

    1. ChangeSet (if you want to keep track of what has been deployed & when)

    2. Using Eclipse

    3. ANT

    Apart from the above three, there are multiple tools available in the market too. But the above three are used mostly.

    Thank,

    Nikita Gupta

  • Hi Divya,

    You can use the Process Builder to perform more actions than with workflow:

    Create a record
    Update any related record
    Use a quick action to create a record, update a record, or log a call
    Launch a flow
    Send an email
    Post to Chatter
    Submit for approval
    Call apex methods
    But the process builder doesn’t support outbound messages.

    Workflow does only 4 actions

    Create Task
    Update Fiel
    Email Alert
    Outbound Message

    Take a look here for more information

    Differences between Process Builder and other tools

    https://www.oreilly.com/library/view/learning-salesforce-visual/9781785289835/ch05s02.html

    Figure Out Which Tool To Use

    https://trailhead.salesforce.com/en/content/learn/modules/business_process_automation/process_whichtool

    Thanks,

    Nikita Gupta

  • Hi Prachi,

    Go through the following link to understand the difference between reports and dashboard.

    https://help.salesforce.com/articleView?id=lex_gaps_limitations_analytics.htm&type=5

    Wave Analytics

    Wave Analytics (formerly Salesforce Analytics Cloud) is a business intelligence tool, which has taken the complexities of data analysis and turned them into simple, mobile-friendly solutions that any Salesforce user can understand.

    Wave Analytics vs. Standard Salesforce Reporting

    One of the most noticeable differences between the two is the user interface. Wave Analytics has a clean, modern look that tends to encourage the end-user to explore data much more thoroughly. Pre-defined filters that you don’t have to recreate with each report, dynamic dashboards with customizable widgets, heat maps, forecasting, and strong data security are just a few differences between the two.

    Wave Analytics is also designed to analyze data from external sources, whereas standard Salesforce reporting would require you to import all data before analyzing. This means there is no need to litter your Salesforce instance with unnecessary customizations and complex development tasks. Open API access for Wave Analytics allows you to quickly import external data source into a single, data analysis platform.

    Another major differentiator between Wave Analytics and standard Salesforce Report is mobile capabilities. Wave Analytics was built “mobile-first” and is optimized for tablets, phones, and even smartwatches. Whereas data analysis and report building are limited on the Salesforce1 mobile platform. Wave Analytics allows your team to efficiently slice and dice reports from the comfort of their mobile device without losing crucial functionality.

    A few smaller, but notable differences include the security model, licensing, and the learning curve. Security in Wave Analytics is separate from standard Salesforce, so a new security model must be scoped and defined. It’s not required to license all your current Salesforce users on Wave Analytics, so you can select a handful of users to begin utilizing the platform, helping protect your wallet. There’s also a shallow learning curve for newly exposed users, meaning there’s not an extensive need for professional services after the initial configuration.

    Thank you,

    Nikita Gupta

  • Nikita

    Member
    August 8, 2019 at 6:42 am in reply to: Is there any governor limit on the number of objects in Salesforce?

    Hi Divya,

    Yes, there are governor limits on the number of custom objects in Salesforce. The Governor Limits are only on Custom Objects not on Standard Object because Standard objects are already present in every Org.

             Different Editions with  Maximum No of Custom objects per Org

    • Contact Manager                                                      5
    • Group Edition                                                          50
    • Enterprise Edition                                                   200
    • Unlimited and Performance Edition                       2000
    • Developer Edition                                                   400

    Thank,

    Nikita Gupta

    • This reply was modified 5 years, 3 months ago by  Nikita.
  • There are several different methods available for mass updating records in Salesforce, depend on the size of Records.

    • List views
    • Mass transfer tool
    • Data Import Wizard
    • API tools such as Data Loader

    If you are updating more than 50,000 records but less than 5 million records, use Data Loader.
    To update more than 5 million records, work with a Salesforce partner or visit the AppExchange for a suitable partner product.

    Methods for Mass Updating and Data Importing

    Use the ListView when

    • A single field with the same value for a small number of records
    • Consider an existing or create a Custom ListView in Salesforce Classic to select multiple records and mass edit field values via inline editing from within the list view.

    Use Mass transfer tool

    • Only for record owners

    Use the Data Import Wizard when

    • You need to load less than 50,000 records.
    • The objects you need to update are supported by the wizard.

    Use Data Loader when

    • You need to update 50,000 to ~100,000 records.
    • You need to update into an object that is not supported by the Data Import Wizard.

    So, according to your requirement, you can choose any of these methods for updating the records.

    • This reply was modified 5 years, 3 months ago by  Nikita.
Page 12 of 12