2

I'm a product manager at Salesforce working on this area. I just updated our collection of Ideas. Scan the list for "header". https://sfdc.co/xandersroadmap Feel free to contribute there or get in touch with me. My email is listed there. Thanks, Xander


2

As manjit5190 pointed out in the comments, profiles don't control what records people see; they control what kinds of records they can see. For example, say a business has two profiles that can see opportunities -- Sales and Support. Sales needs access to opportunities so that they can generate new revenue, and support needs access to submit replacement ...


1

You can do this by adding another <supportedFormFactor type="Small" /> in <supportedFormFactors>:- <?xml version="1.0" encoding="UTF-8"?> <LightningComponentBundle xmlns="http://soap.sforce.com/2006/04/metadata"> <apiVersion>42.0</apiVersion> <isExposed>true</isExposed> <masterLabel>Best ...


1

In your application you need to extend force:slds to import slds stylesheet <aura:application extends="force:slds"> <c:campingListItem/> </aura:application>


1

You are not passing the recordId from your VF page currently. The empty braces {} in your following snippet represents which attributes you need to pass to your component and that currently you are not passing anything. $Lightning.createComponent("c:CPM_CreateAction",{}, .... You will need to change it to something as below for the component to receive ...


1

The administrator decides who gets what during installation (all users, admins only, or selected profiles). You don't get to decide who sees what. Instead, your permission set should include only the base tabs (not the admin-only ones), so that users assigned your permission set won't see everything. You can add a second permission set for admins if you need ...


Only top voted, non community-wiki answers of a minimum length are eligible