5

While "Login As" feature did not work to reproduce the issue, actually login as that user with its credentials did. After that, I came to this conclusion: Normally, LWC engine will parse and transform any latest syntax, lets say ES20 features, and convert it into something readable by the client browser if it is not supported already, however, ...


4

You just need to add CSS to wrap the text. overflow-wrap: break-word; define a class in CSS file .wrapped-content{ overflow-wrap: break-word; } And add this class to the div. <template> <div class="slds-grid slds-grid_align-center"> <lightning-card class="slds-size_1-of-3"> <div class=&...


3

You already have a getter (title) that checks this properly (via getFieldValue), so you can just reuse it! get isNullTitleValue(){ return !this.title; }


3

Because the getter runs before the data comes back from the @wire method, you will get this error as the contact object will be empty/undefined. To prevent this, you need to perform some null checks in the getter: get isNullTitleValue(){ if(this.contact && this.contact.data && this.contact.data.fields.Title.value === ...


2

You need to use this keyword. For eg : this.editValue should work. The only time you can skip this keyword is when you have variables declared inside local scope.


2

Unfortunately, this is not supported. The lightning-datatable is designed after SLDS, which does not have an allowance for multiple header rows or cells that span more than one column. You'd have to roll your own table instead.


2

My guess is that the table doesn't know to update because you have specified a key field of id but you have not provided on in the object array that you are feeding to the table. The table likely drives it's refresh algorithm off the key field, so even though you refreshed the array, with all the ids being the same, it won't rerender. And when you do it in ...


1

You can use a Lightning App. Like a VFP, they are addressable via a URL: https://mydomain.lightning.force.com/my_ns/appName.app Which you write as: <aura:application extends="force:slds"> <c:myLwc /> </aura:application> You can also just add the lightning__AppPage target and and make a full page app if you prefer, though it ...


1

According to Spring '19 ... Bring modern, blazing-fast Lightning web components (LWC) into the utility bar by adding the lightning__UtilityBar target to your LWC‘s meta configuration. LWC utilities don’t yet support APIs or being used as background utility items. However... You might be able to go for a hybrid solution where you use an Aura Component in ...


1

On the assumption that this button is just a small part of a larger component where all profiles see the other parts you have not shown, you need to make the button rendering conditional: <template if:true={canDeactivate}> <lightning-button slot="actions" label="Deactivate" onclick={DeactivateProcess}> </lightning-...


1

When you change the record, the record-form component is not reloaded, just the context is changed. But here you need to reload the component completely so you can get the default behavior same as first time load. Also instead of manipulating the classList you need to use the if:true attribute. If you use this approach, the framework will automatically mount/...


1

It seems like you are already assigning the value of lightning-input in keyword variable on change event. searchKeyword(event) { this.keyword = event.target.value; } So no need to again fetch the value of lightning-input on button click just pass your keyword variable to your Apex controller method. handleSearchKeyword(event){ ...


1

Try wrapping the spinner and your component markup in a element or div having class slds-is-relative.


1

You're not building your options correctly in your wire method getPicklistValuesByRecordType for a combobox. You need a value and label. You're just pushing labels which is why you see the options in the dropdown, but then have nulls (as there's no value you're pushing). this.record = data; this.error = undefined; let temp_option = []...


1

This is a timing issue, depending on when you are calling loadData() in your LWC and the Apex time to return the data, the iFrame may or may have not registered the listener yet. An easy solution would be to just load the data after the iFrame finished loading: <template> <div> <iframe src={viewerUrl} style={viewerStyling} onload={...


1

In Aura, we have lightning:unsavedChanges. Unfortunately, we do not yet have a parallel to this in LWC. You cannot cancel or prevent this event, as it is called after the component has already moved away from the component (i.e. after is removed from the DOM). If you need this functionality, use Aura instead of LWC; you could write an Aura "wrapper"...


1

Because you are using an accumulator, you need to make sure that you are returning a number from all possible outcomes inside your callback function. Here you are possibly returning back a value inside the if statement (but I'd probably wrap the assignment in brackets - the result of that assignment could actually be returning true not a value. if (...


1

(I'm providing a separate answer as this is a completely different solution approach). When the provided components don't work, the alternative is building a new LWC - in this case, to replace lightning-input-field. This comes with complications: you can't simply let the component integrate with the lightning-record-edit-form; you need to handle getting the ...


1

Although it isn't documented, you can set an html id attribute on lightning-input-field. It will likely be changed (amended) by the system when it is rendered, however, a corresponding label for="id" will also be updated and will match the modified id value. For example, I just tested the following in an lwc template: <label for="example&...


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