Forum Replies Created

Viewing 1 - 25 of 292 posts
  • Manpreet

    Member
    May 1, 2018 at 10:59 am

    Hi Aman,

    If your element is a product attribute, Magento is ready to handle with the Soap API. The catalogProductCreate method has additional_attributes parameter. You can use it to set one or more values to your attribute using single_data or multi_data.

    Example: Add a manufacturer info

    $newProduct->name = "product name";
    $newProduct->description = "description";
    $newProduct->short_description = "desc";
    $newProduct->status = "1";
    $newProduct->price = "99";
    $newProduct->tax_class_id = "2";

    $newProduct->additional_attributes = array(
    'single_data' => array(
    array(
    'key' => 'manufacturer',
    'value' => 'Company INC',
    ),
    )
    );
    /* you can add other additional attributes here like $manufacturer using multi_data parameters */

    Thanks.

  • Manpreet

    Member
    May 1, 2018 at 10:58 am

    Hi shubham,

    It represents a Lightning definition bundle, it contains a Lightning definition and all its related resources. It could define a component, application, event, interface, or a tokens collection.

    An AuraDefinitionBundle component is a collection of component definition files, each representing a different resource such as markup code, event documentations, applications and interfaces.

    Lightning bundles must be under a top-level folder that’s named aura. Each bundle must have its own subfolder under the aura folder.

    Thanks.

  • Manpreet

    Member
    May 1, 2018 at 10:57 am

    Hi shubham,

    aura:registerevent is the notifier component and it declares that it may fire a particular event, it includes ‘name’ attribute which is relevant only to component event and is not used for application event. Other attribute is the ‘type’ which lets the component know which event would be fired.

    Ex. <aura:registerEvent name=”Event” type=”c:EventName”/>

    Thanks.

  • Manpreet

    Member
    May 1, 2018 at 10:53 am

    Hi Aman,

    Additional instructions for Enterprise 2.0 accounts Continue to set roles and permissions:

    Click My Users from Email Studio Admin.
    Select the Marketing Cloud API User.
    Click Manage Roles.
    Click Edit Roles.
    Assign the following roles: Administrator Marketing Cloud Administrator
    Click Save.

    Thanks.

  • Manpreet

    Member
    May 1, 2018 at 10:52 am

    Hi Aman,

    Since the responses probably go to your email you can sync them with things like Salesforce for Outlook, Connect for Outlook. Or if you are not using Outlook you can use Email to Salesforce and forward the emails to the address it gives you, it will try to match it to the record based upon the from email in the original message.

    For HTML email tracking make sure its enabled in Activity Settings then that you are sending html emails of course, make sure to add the related list for HTML email status and then hope that the recipient is loading images in their emails, otherwise the tracking image will not be accessed and an opening will not register.

    Thanks.

  • Manpreet

    Member
    May 1, 2018 at 10:50 am

    Hi pranav,

    For this purpose we need to first make a lightning tab which points to the lightning component we created and then we have to include that tab in the salesforc1 Mobile Navigation select list and the newly created tab to it.

    Thanks.

  • Manpreet

    Member
    May 1, 2018 at 10:48 am

    Hi pranav,

    A Lightning component can be embed in any webpage using a very powerful and flexible feature, Lighting out. When used with Visualforce some complexity becomes simpler.
    Lightning component can be added to Visualforce page in three steps:

    1. We have to first Add the Lightning Components for Visualforce JavaScript library to your targetted Visualforce page using the tag.

    2. Next we have to create and refer a Lightning app which is used to the component dependencies.

    3. Lastly we need to write a JavaScript function which will finally create the the component on the page using $Lightning.createComponent()

    Thanks.

  • Manpreet

    Member
    May 1, 2018 at 10:47 am

    Hi pranav,

    We need to implement the following “force: lightningQuickAction” so that we can use the component as a Quick Action

    Thanks.

  • Manpreet

    Member
    May 1, 2018 at 10:45 am

    Hi pranav,

    a. Application Event – Scope of this event is throughout the lightning App and any component which has registered for this event would get a notification.
    b. Component Event– Scope of this event is within itself or the parent component of this event, all the components declared within the parent component would get notified of this event.
    c. System Event- these are the events fired by Salesforce’s system during the lifecycle of the lightning app.

    Thanks.

  • Manpreet

    Member
    April 27, 2018 at 11:30 am

    Hi saurabh,

    Validation rules can never be bypassed. If we have upload records and need to bypass validation, then deactivate validation rule and upload records. After upload, again activate validation rule.

    Thanks.

  • Manpreet

    Member
    April 27, 2018 at 11:29 am

    Hi saurabh,

    No. Validation rules fire in insert and update operation.

    Thanks.

  • Manpreet

    Member
    April 27, 2018 at 11:28 am

    Hi saurabh,

    Yes. Create a checkbox field as API upload and make this field hidden in page layout. Create a validation rule and in evaluation criteria first check if checkbox is false and then check other validation criteria.
    Whenever user upload record through data loader, specify value for this checkbox as true in .csv file and then upload it to salesforce. While upload, validation rule will fire and will find checkbox value as true so it will not check other criteria and system will allow to upload records.

    Thanks.

  • Manpreet

    Member
    April 27, 2018 at 11:26 am

    Hi saurabh,

    “Manage Force.com Flow” AND “View All Data” in profile.

    Thanks.

  • Manpreet

    Member
    April 27, 2018 at 11:25 am

    Hi saurabh,

    Use the error messages that appear in the Process Builder and the emails you receive when a process fails to help solve problems that arise when you’re working with processes. When all else fails, look at the Apex debug logs for your processes.
    Identifying Errors in the Process Builder
    The API names for criteria nodes and actions are created in the background. When you create or update processes, you might see error messages that reference those names to help you identify specifically where the problem occurred.
    Errors Received after a Process Starts Evaluating a Record
    When a user performs an action that triggers a process (such as creating a record) and that process fails, the user sees a page with this error: “Workflow Action Failed to Trigger Flow.” In addition, the administrator who created the process receives an email with more details.
    Using Debug Logs to Troubleshoot Processes
    Use debug logs to find detailed information about your running processes after they finish running. For example, if a process doesn’t seem to trigger when a record meets the process’s criteria, or if you want to understand the sequence of processes being executed.

    Thanks.

  • Manpreet

    Member
    April 27, 2018 at 11:25 am

    Hi saurabh,

    Below are 2 conditions:
    Only when record is created
    When record is created or edited and while define criteria select the checkbox for below setting
    Do you want to execute the actions only when specified changes are made to the record?
    3. Is it possible to edit the process once it is activated?
    No, You need to clone and while cloning you can create new process or create new version.

    Thanks.

  • Manpreet

    Member
    April 27, 2018 at 11:24 am

    Hi saurabh,

    If object-level permissions conflict with record-level permissions, Salesforce applies the most restrictive settings.
    If a user’s profile grants him update permission on an object, he will not be able to edit records of that type owned by other users unless read/write record-sharing has been granted.
    If read/write sharing has been granted, a user whose profile does not specify update permission will not be able to edit records of that type.

    Thanks.

  • Manpreet

    Member
    April 27, 2018 at 11:23 am

    Hi saurabh,

    When you grant “View All” or “Modify All” for an object on a profile or permission set, you grant any associated users access to all records of that object regardless of the sharing and security settings.
    In essence, the “View All” and “Modify All” permissions ignore the sharing model, role hierarchy, and sharing rules that the “Create,” “Read,” “Edit,” and “Delete” permissions respect. Furthermore, “Modify All” also gives a user the ability to mass transfer, mass update, and mass delete records of that specific object, and approve such records even if the user is not a designated approver.
    These tasks are typically reserved for administrators, but because “View All” and “Modify All” let us selectively override the system, responsibilities that are usually reserved for the administrator can be delegated to other users in a highly controlled fashion.

    Thanks,

  • Manpreet

    Member
    April 27, 2018 at 11:22 am

    Hi saurabh,

    Field-level security doesn’t prevent searching on the values in a field. When search terms match on field values protected by field-level security, the associated records are returned in the search results without the protected fields and their values.

    Thanks.

  • Manpreet

    Member
    April 27, 2018 at 11:21 am

    Hi saurabh,

    Query “userRecordAccess” to check whether has access to record or not.
    For example:
    SELECT RecordId, HasReadAccess, HasTransferAccess, MaxAccessLevel, HasAllAccess, HasDeleteAccess, HasEditAccess FROM UserRecordAccessWHERE UserId = “005xxxxxxxxx”AND RecordId = “001xxxxxxxx”
    HasAllAccess Indicates whether a user has all access–read, edit, delete, and transfer—to the record (true) or not (false).
    HasReadAccess, HasEditAccess , HasDeleteAccess ,HasTransferAccess return Boolean value.
    MaxAccessLevel return access level like None, read, Edit,Delete,Transfer and All.

    Thanks.

  • Manpreet

    Member
    April 27, 2018 at 11:16 am

    Hi pranav,

    No. We can define apex sharing reasons for custom object.
    Apex sharing reasons are defined object by object. - so, positions might have different reasons than candidates.

    Thanks.

  • Manpreet

    Member
    April 27, 2018 at 11:15 am

    Hi pranav,

    Share table contains four columns: ParentId, UserOrGroupId, RowCause, AccessLevel.
    Below is code to create position__share record:
    Position__share p = new Position__share();
    p.parentId = ‘Position Record Id which needs to be shared’;
    p.userOrGroupId= ‘User id or Group id with which we want to share record’;
    p.RowCause=’ apex sharing reason defined for custom object, here for position__c’;
    p.AccessLevel =’access level for record’; //can be Read or Edit
    insert p;
    Note: you cannot update share table record. System only allows insert or delete of records for share table. So if you have to change access for user, you have create new record and can delete already existing record if you want.

    Thanks.

  • Manpreet

    Member
    April 27, 2018 at 11:14 am

    Hi pranav,

    Apex managed sharing is a type of "Programatic Sharing" which allows you to define a custom sharing reason to associate with your programatic share. Standard Salesforce objects support "Programatic Sharing" while custom objects support Apex managed sharing. More specifically, object shares can be written to both standard and custom objects, however custom sharing reasons can only be defined for shares written to custom objects.
    apex manage sharing is used for custom objects as we can define apex sharing reason for custom objects. For standard object, apex sharing reason will be “Mannual”.
    Salesforce create share table for all objects for which OWD is either public read only or Private. For standard object, share table name is table name followed by share word. For example: AccountShare, ContactShare, CaseShare
    For custom object, it is followed by __share. For example : For Position__c, share table name is Position__share.

    Thanks.

  • Manpreet

    Member
    April 27, 2018 at 11:13 am

    Hi pranav,

    Yes, only if relationship is master detail. If it is look-up relationship, then it is not possible.

    Thanks.

  • Manpreet

    Member
    April 27, 2018 at 11:12 am

    Hi pranav,

    For that you will have to Define different steps in approval process.For further reference : https://trailhead.salesforce.com/en/projects/build-a-discount-approval-process/steps/create-an-approval-process.

    Thanks.

  • Manpreet

    Member
    April 27, 2018 at 11:10 am

    Hi pranav,

    Yes.
    In processes that have steps that are optional depending on criteria, use the skip step feature.
    To skip steps, use filter criteria or formula, then choose what should happen to records that do not meet the criteria. The options are:
    - Approve Record (approves the request and performs all final approval actions).
    - Go to Next Step (skips this step and goes to the next step).

    Thanks.

Viewing 1 - 25 of 292 posts