Yes, by using the Design file, you can restrict access to just certain objects. This in the documentation:
<sfdc:object> and <sfdc:objects>
Use these tag sets to restrict your component to one or more objects.
<design:component label="Hello World">
<design:attribute name="subject" label="...
In the Summer 20 release, the componentInstances property for FlexiPage regions has been removed. These need to be replaced with itemInstances as outlined in the release notes. More details on the structure of an ItemInstance metadata type is in the guide.
For orgs that have been refreshed into the new version (like sandboxes and your production org at the ...
wire service getWorkingDays is dependent on record.id. So, this wire will invoke again only when record.id changes. But, although getRecord service is invoked every-time record is updated, its id never changes and so getWorkingDays is never getting invoked again.
You can use imperative apex call and use it inside getRecord function or you can try ...
This is because there are actually 2 instances of your div/component in the DOM tree after a new Account is created.
If you change your div to have class="te2" instead of an id and then in your click handler do:
var te2 = document.getElementsByClassName("te2");
You'll get back an array with both elements. The first element has clientHeight 0 because it ...
The sourceApiVersion on the sfdx-project.json is what controls what API certain CLI commands use. You can change this to 48.0 and deploy if you'd like (even to an Org on 49.0 that may have changed the underlying metadata).
I was able to deploy a FlexiPage with componentInstances references to an org with 49.0 by setting the sfdx-project.json file's ...
I have been in touch with Salesforce (as a DFC author) on a somewhat related topic for last few days and I know that no additional public documentation (at least officially) exists on FlexiPages as of now. Having said that, I also know that there is a plan to publish more blog posts & DFC articles on Salesforce1 in January and I believe it would cover ...
I would use cmp.find() instead of document.getElement(). This is because cmp.find() is the native Lightning API for finding the DOM
To make this work, you have to add an aura:id like this to the div
<div aura:id="te2" id="te2">...</div>
I tried to inspect the classes that go behind Salesforce's standard template that make the header stick, but couldn't get it to work as quickly as I preferred, so I got going with my own way. The following is not production ready, but should help you get started should you choose to go the custom route as well:
Looking at the screenshot and searching for the Lightning Tree component in appexchange led me to this github source for the component
It seems to be an open source reusable component that you can include in your apps via code (look at this sample). but the component is not implementing any of the interfaces by default to enable it to be used in the app ...
Yes, a flexipage is actually a Lightning component (flexipage:page) and a very powerful one. I've asked the product manager for Lightning Pages to comment here on roadmap plans for access="global"ing it. Somewhat ironically I was the first to ask for this awhile back - totally get the power of this capability.
It seems there is a significant bug in the Lightning Platform infrastructure. While it should be possible to include the LWC component hierarchy in the flexipage it appears there's a namespace handling issue that prevents it. The workaround is as per a different known issue:
Create an Aura-based "wrapper" component that includes the necessary design ...
You can use standard__navItemPage (Navigation Item Page Type) with lightning:navigation here. Refer to the documentation for pageReference Types those are utilized with the component for details. From documentation:
Navigation Item Page Type
A page that displays the content mapped to a CustomTab. Visualforce tabs, Web tabs, Lightning Pages, and Lightning ...
Let me offer you another approach.
Instead of trying to figure out where a component is dropped, think about exposing a design attribute on your component that will allow users to show or hide the header manually when they manipulate it in the App Builder.
<aura:component implements="flexipage:availableForAllPageTypes" access="global" ...
Given @salesforce-sas's answer (patiently built up iteratively with me) the following points should be noted:
My implementation's chaining of wired service calls was broken and here's why...
As a bit of background, when you set up a tracked property you have basically two choices:
Have tracked changes trigger processing if the property itself changes by ...
At this point, it is not possible to utilize Lightning Pages (Flexipages) as a programmatic building block for use in your own components.
Ultimately, it's something we'd like to do eventually since it would open up a wide range of options for customization of your apps.
Our current priority for Lightning Pages and App Builder is customization of ...
There is a limitation on the number of components that you can have in a flexipage, however it's 25 and not 2.
This is stated in the Salesforce1 developer guide on page 155:
I don't see anything wrong with your flexipage though...
This functionality is coming in Spring 17 release. You can edit the page using Lightning App Builder. You can click on the 'Related Lists' (not Related List) component and select the way they need to be displayed. You will see three options: Default, List and Card. Select List and all the related list will display in the familiar tabular format.
I have the same issue and spent quite a lot of time to find the solution. Unfortunately, there are nothing about ability to activate Lightning record page via API. So it turns out that we have only Lightning App Builder for now to do this.
Finally I left post at IdeaExchange. Hope Salesforce could offer any solution in the future.
Internal URL is the right choice. You define the URL when you create the page
Later if you want to see or edit the URL, pick the page from the Page-Picklist in the top and then make just sure, that under PAGE STRUCTURE the page-name itself is selected. You see the Name and URL (editable) in the property editor at the right sidebar. The URL is labeled Vanity ...
Not sure if this was possible at the time you wrote this post but it now is and can be achieved by using the following in an applications/AppName.app metadata file:
Account_Record_Page.flexipage-meta.xml fails with "Component [force:relatedListSingleContainer] attribute [relatedListApiName]: Could not find related list [AccountContactRelations] for entity [Ac count]", which is a known Salesforce issue.
This sObject requires the Contacts to Multiple Accounts feature, which is enabled in your scratch org ...
This is a change with the v49.0 summer 21 release. Meaning you won't be able to use v48.0 version of the metadata in the v49.0 org unless you push with v48.0 in sfdx-project.
Once all the orgs are updated to v49.0, make sure to retrieve using the v49.0 in the sfdx-project.json and deploy to update the metadata.
Flexipage assignment on org default level can be deployed with ActionOverride metadata. It is a nested metadata inside CustomObject metadata type.
From the documentation:
To set a Lightning page action override on the View standard button in
Lightning Experience, use:
'Order_Record_Page1' doesn't exist in the database until you press save. What you are seeing is technically a cloned version of the standard (system default) out of the box page, all in your browser. "Order_Record_Page1" is a default generated name which will be used if you press save.
I think you are confusing DeveloperName with Label. Most Salesforce setup objects have a DeveloperName which needs to be unique and can't contain spaces or special characters, whereas the Label can contain those things.
If you open developer console and run a query using the Tooling API, you can see both pretty easily.
select id, MasterLabel, DeveloperName ...
Firstly, what you are trying to get is label and not title. Title is something which comes as pop-up near mouse pointer when you place mouse on a field for more than like 2 sec (or 3sec appx.)
As a standard, you will get the object label in top of highlights panel - below which you can place 5 fields (for which labels are also displayed). But, you cannot ...