Hot answers tagged

8

As of Summer '15 this component still has server-side dependencies that prevent it from updating as desired. You will need create the component in JavaScript to achieve the desired result. Here's a small app that demonstrates this: <aura:application access="GLOBAL"> <aura:attribute name="id" type="String" access="GLOBAL" default="...


6

LWC was introduced in latest release - Spring '19 and it's API number is 45.0 so if you describe your metadata using 44.0 MDAPI won't be able to see those components. You need to change "-a" parameter to "45.0" sfdx force:mdapi:describemetadata -a 45.0 -u username


5

The last value in the case is the "default value", in other words, for any value not already in the case statement. Therefore, it should look like this: CASE(Lead_Source__c, "Self Generated", IF(Markup__c >= 0.35 && Markup__c <0.40, 5, IF(Markup__c <0.50, 8, IF(Markup__c <0.60, 11, IF(Markup__c <0....


3

Ya, this is most likely from the CLI upgrade, and installing the plugin again probably won't help. It might be because your alias contains .'s in it which I didn't think worked in v6 either. Can you try to update your alias and see if that resolves it? sfdx force:alias:set newAliasWithoutDots=<yourscratchorg> sfdx force:config:set defaultusername=...


3

It may wont work properly because of lightning out behavior Excerpt from bookshelf. While the core Lightning Out functionality is stable and complete, there are a few interactions with other Salesforce features that we’re still working on. Chief among these is the standard components built into the Lightning Component framework. At this time, a number of ...


3

Community Users are derived from your contacts and Community license has access to only to certain objects and will not have access to the Opportunity , Leads and Campaigns Similarly partner license has access to only certain CRM Objects (Opportunity,Leads) . The answer really depends on from which objects your charts are getting data from . The ...


2

The platform in and of itself is not customer-averse. However, you probably don't want to buy all your customers a license, nor do you want to give them too much data access. Take a look at Community Cloud, which is in fact designed to be customer facing. Another option is to use Site pages, which can be easily integrated with a branded website.


2

If you're already using a trigger on the object for other purposes, consider using a trigger to do the heavy lifting. Otherwise, go for either a Process Builder or Workflow Field Update. The reason for this is that field updates will cause your triggers to run twice, potentially doubling execution time. If you have no triggers, however, using workflow rules ...


2

You can use this formula to be evaluated as rule criteria: EventDate__c = TODAY() It will work.


2

force:createRecord opens a page to create a record for the specified entityApiName, for example, "Account", or "myNamespace__MyObject__c". To display the record create page for an object, set the object name on the entityApiName attribute and fire the event. recordTypeId is optional and, if provided, specifies the record type for the created object. ...


2

Idea has been created regrading the Callback method for force:createRecord event to redirect or refresh after save:- https://success.salesforce.com/ideaView?id=0873A0000003V4hQAE You have to go for Custom Lightning Component with same functionality without using e.force:createRecord and you will be able to Callback after the record was created like:- // ...


1

Issue was due to case sensitive nature of lightning only.It got resolved when I used recordTypeId instead of RecordTypeId


1

Current Salesforce User license information can be found by the following links: User Licenses Standard User Licenses


1

In order to show the currency I believe you have to use and output field <apex:outPutField value="{!Purchase_Order__c.Total__c}"/>


1

Assuming all values are correct then it is possible the profile has Login IP Ranges defined: Login to production via the UI. Goto the profile associated with your user Look at the "Login IP Ranges" related list. If it is populated your security token cannot be used (you will also notice the reset security token option is not available to your user) so ...


1

As far as I was able to see, the only way of refreshing the component is to recreate dynamically with $A.createComponent() I'm still looking for better alternatives.


1

You have to create Workflow rule with time-dependant action to trigger it when EVENT DATE equals Today (this could be a Field update that will trigger your Workflow rule). You have to check 'Re-evaluate Workflow Rules after Field Change' flag for this to happen.


1

I think it's brandability driven. Salesforce and Salesforce1 (mobile app) aren't super-brandable, so it's easier for a company to ask its employees to use Salesforce than to ask your customers to. And if you're going to write massive amounts of code for brand reasons, you're giving up some of the plarform's advantages. Another is user scale. There are ...


1

Too much to put into a comment, but here are some notes: If you are writing a formula for the Commission_Percentage__c field, it should not contain any references to the field's own API Name (Commission_Percentage__c). If you are writing an IF clause, the syntax is IF(logical_test, value_if_true, value_if_false). You don't do any assignment, so no need to ...


1

I'm in agreement with Anurag A, use out of the box whenever you can. In addition, you may want to look into using CASE instead of the nested if's. It makes the formula much easier to read and debug and you can use it with picklists :)


1

Use rendered attribute in your outputText to show and hide your field. <apex:outputText value="{!Product_Brief__c.Name}" rendered="{!IF(Product_Brief__c != NULL && Product_Brief__c.Name != NULL,true,false)}"> </apex:outputText> Provide a id to outputText and rerender this id in your commandbutton <apex:commandButton value="Save" ...


1

You can use apex:repeat with a list to generate as many Page Blocks as you like. The code below will display a button called "Add Section". One new page block will be added every time you click on the button. Hope this helps. <apex:page controller="TestController"> <apex:form> <apex:commandButton value="Add Section" reRender="...


1

Hope this example helps you <apex:page controller="TestMyPage" > <apex:form > <apex:pageBlock id="block"> <apex:pageBlockSection title="Section 1" rendered="{!showSection1}"/> <apex:pageBlockSection title="Section 2" rendered="{!showSection2}"/>...


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