2

I recollect that this is a design quirk of AuraHandledException and that e.g. this is needed (constructor argument probably doesn't matter): AuraHandledException e = new AuraHandledException(System.Label.consulta_saldo_cliente_18); e.setMessage(System.Label.consulta_saldo_cliente_18); throw e; which is not convenient so best to wrap in a method: private ...


2

As Derek mentioned, MailingCountry is part of the MailingAddress compound field on the Contact object. So it should exist. Another possible explanation for your issue is that you don't have State and Country/Territory Picklists enabled in your org. Once you have that enabled, the first block of code in the blog entry you linked should work, although it's ...


2

The MailingAddress and ShippingAddress fields are special compound fields. They're read-only, and hide the fact that there are indeed separate fields backing them. So while you won't find MailingCountry explicitly listed as a field on the Account or Contact object, the field does in fact exist. This information is also corroborated by the SOAP API ...


2

Define the class level attribute to store the columns, columns. From the wired method add the dynamic columns to that. export default class MyComponent extends LightningElement { @track columns = [ { label: 'View', type: 'button-icon', initialWidth: 75, typeAttributes: { iconName: '...


1

no-cors prevents you from getting the response values in JavaScript (a so-called "Opaque" response). This is a security/privacy feature. See this Q&A on Stack Overflow. The server would have to be enabled to support CORS, which it appears is not the default. Presumably, they expect you to run your own. You should be able to spin up a server on ...


1

you need to specify correct values for small-device-size, medium-device-size and large-device-size. Phone in tablet mode is considered as a medium-device-size. Useful info from documentation Use the attributes of lightning-layout-item to configure the size of the layout item, and change how the layout is configured on different device sizes. The layout ...


1

You specified key={r.id}, but you didn't actually assign a unique id value, so it would cause errors. I've cleaned up your code and fixed the problem. The (a,b) => a + b syntax is an arrow function. We will pass this function in as a parameter to call the code dynamically. This eliminates much of the duplicated code. import { LightningElement,track } from ...


1

First, you cannot control the order of wire methods and how/when they are called. This is managed by the framework. Your property needs to be reactive: @wire(getInitialAccountRecords,{action:'$screenMode', recordId:'$recordId'}) Note that this will will be called multiple times. You will need to account for this in your code: @AuraEnabled public static ... ...


1

As per @SachinHooda's suggestion in comment, Replaced lwc combobox with with and that fixed the issue. <div class="slds-select_container" > <select name="peGroup" value={selectedId} class="slds-select" onchange={handleChange}> <template for:each={options} for:item="opt"> ...


1

lightning-record-form component will be based on standard page layout. Dynamic action will not impact it. I have done a quick check on this:- Even if you remove a field from dynamic form, if the field is available on standard page layout, it will appear on the record form component. My record Form component looks like this:- <template> <...


1

It doesn't look like lightning-datatable (actually lightning-formatted-url, which it uses) directly supports other protocols besides http or https. This is probably to prevent Cross-Site Scripting (XSS) vulnerabilities. Even the mailto protocol appears to be unsupported. You can specify a relative URL using /, ./, etc. See documentation for lightning-...


1

Note that 'undefined' is different than undefined. The former is a string with the word undefined in it, the latter is a type of null value that means "an undefined value." Note that in JavaScript, both of these values are considered "falsy", so you can use behavior to write the logic simply as: get displayFundStrategy() { return !!...


1

So it turns out Base_Station__c is a lookup, and you are trying to push a String value = csvRowData[0] which is just a string, thus it fails. You need to query the data first and fetch the ID for the field and populate the ID there.


1

event.detail.row isn't an Array, it's a single object. You may have meant: this.finalSObjectDataListChild = [dataRow]; Which would make it suitable for lightning-datatable.


1

Since your row data depends on the result of a wire, you need to ensure that the "initialization" is performed after that wire returns the required value. Note, also, that doInit is not an LWC construct, but rather is Aura's equivalent to the LWC connectedCallback. However, you cannot use LWC's connectedCallback because this would be called before ...


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