Uncaught TypeError: 'set' on proxy: trap returned falsish for property NameHow to convey LWC's complex...

I'm flying to France today and my passport expires in less than 2 months

RSA: Danger of using p to create q

Are astronomers waiting to see something in an image from a gravitational lens that they've already seen in an adjacent image?

High voltage LED indicator 40-1000 VDC without additional power supply

Why can't we play rap on piano?

Are the number of citations and number of published articles the most important criteria for a tenure promotion?

Replacing matching entries in one column of a file by another column from a different file

Paid for article while in US on F-1 visa?

What does the "remote control" for a QF-4 look like?

Could an aircraft fly or hover using only jets of compressed air?

Doing something right before you need it - expression for this?

Fully-Firstable Anagram Sets

Accidentally leaked the solution to an assignment, what to do now? (I'm the prof)

Why is consensus so controversial in Britain?

When a company launches a new product do they "come out" with a new product or do they "come up" with a new product?

How does one intimidate enemies without having the capacity for violence?

How can I make my BBEG immortal short of making them a Lich or Vampire?

Why is 150k or 200k jobs considered good when there's 300k+ births a month?

What are these boxed doors outside store fronts in New York?

How to determine what difficulty is right for the game?

Do I have a twin with permutated remainders?

Theorems that impeded progress

Why doesn't H₄O²⁺ exist?

How old can references or sources in a thesis be?



Uncaught TypeError: 'set' on proxy: trap returned falsish for property Name


How to convey LWC's complex Reactive property back to markup?How to set a public reactive property in the declared component during component constructionProperty “selectedContact” of [object:vm undefined > (51)] is set to a non-trackable objectHow to set default value for a select in lwc






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







4















Am not doing anything fancy, just trying to update a field on Contact in JS of LWC but getting this exception.



Uncaught TypeError: 'set' on proxy: trap returned falsish for property 'Name'
throws at mydomain/auraFW/javascript/mhontaYdOya4Y_lBu7v9yg/aura_prod.js:2:27687



HTML Code:



<template>

<template if:true={wiredContact}>

{wiredContact.Name}

<lightning-input value={wiredContact.Name} onchange={updateName}></lightning-input>
</template>

</template>


JS:



import { LightningElement ,wire,track,api } from 'lwc';
import myContact from "@salesforce/apex/ContactController.fetchContact";

export default class Myrefreshapextest extends LightningElement {


@track wiredContact;

@wire (myContact)
fetchedContact({error, data}){
if(data){
console.log(JSON.stringify(data));
this.wiredContact = data;
}else if (error){
console.log(error);
}
}

updateName (event){
console.log(JSON.stringify(event.detail.value));
console.log(JSON.stringify(this.wiredContact));
this.wiredContact.Name = event.detail.value;
}

}


Apex:



public class ContactController {

@AuraEnabled(cacheable=true)
public static Contact fetchContact(){
return [SELECT Id,Name FROM COntact LIMIT 1];
}
}


On top of my head, am not doing anything wrong, anyone has idea what's wrong with my code?



When I print console.log(JSON.stringify(this.wiredContact)); I get old values so am pretty sure it exists.



I tried with @track and @api, but same response. Can anyone shed some light?










share|improve this question























  • Do you get same issue when you use the individual field names viz., FirstName?

    – Jayant Das
    11 hours ago











  • Same error Uncaught TypeError: 'set' on proxy: trap returned falsish for property 'FirstName' throws at its same error doesnt matter if its normal contact or personAccountContact.

    – Pranay Jaiswal
    11 hours ago













  • I got the error (not exactly the same) but was able to replicate. Seems like you cannot set a value directly to the property instead recreate the JSON and then assign. E.g., this.wiredContact = ["Name:" + event.detail.value]; this worked. Still trying to figure out.

    – Jayant Das
    11 hours ago











  • @JayantDas It's a design feature. One that I'm pretty sure isn't documented.

    – sfdcfox
    11 hours ago











  • @sfdcfox I just saw the behavior you mentioned just by trying it out, and it worked, even though my format above is not JSON, but I was intending that.

    – Jayant Das
    10 hours ago


















4















Am not doing anything fancy, just trying to update a field on Contact in JS of LWC but getting this exception.



Uncaught TypeError: 'set' on proxy: trap returned falsish for property 'Name'
throws at mydomain/auraFW/javascript/mhontaYdOya4Y_lBu7v9yg/aura_prod.js:2:27687



HTML Code:



<template>

<template if:true={wiredContact}>

{wiredContact.Name}

<lightning-input value={wiredContact.Name} onchange={updateName}></lightning-input>
</template>

</template>


JS:



import { LightningElement ,wire,track,api } from 'lwc';
import myContact from "@salesforce/apex/ContactController.fetchContact";

export default class Myrefreshapextest extends LightningElement {


@track wiredContact;

@wire (myContact)
fetchedContact({error, data}){
if(data){
console.log(JSON.stringify(data));
this.wiredContact = data;
}else if (error){
console.log(error);
}
}

updateName (event){
console.log(JSON.stringify(event.detail.value));
console.log(JSON.stringify(this.wiredContact));
this.wiredContact.Name = event.detail.value;
}

}


Apex:



public class ContactController {

@AuraEnabled(cacheable=true)
public static Contact fetchContact(){
return [SELECT Id,Name FROM COntact LIMIT 1];
}
}


On top of my head, am not doing anything wrong, anyone has idea what's wrong with my code?



When I print console.log(JSON.stringify(this.wiredContact)); I get old values so am pretty sure it exists.



I tried with @track and @api, but same response. Can anyone shed some light?










share|improve this question























  • Do you get same issue when you use the individual field names viz., FirstName?

    – Jayant Das
    11 hours ago











  • Same error Uncaught TypeError: 'set' on proxy: trap returned falsish for property 'FirstName' throws at its same error doesnt matter if its normal contact or personAccountContact.

    – Pranay Jaiswal
    11 hours ago













  • I got the error (not exactly the same) but was able to replicate. Seems like you cannot set a value directly to the property instead recreate the JSON and then assign. E.g., this.wiredContact = ["Name:" + event.detail.value]; this worked. Still trying to figure out.

    – Jayant Das
    11 hours ago











  • @JayantDas It's a design feature. One that I'm pretty sure isn't documented.

    – sfdcfox
    11 hours ago











  • @sfdcfox I just saw the behavior you mentioned just by trying it out, and it worked, even though my format above is not JSON, but I was intending that.

    – Jayant Das
    10 hours ago














4












4








4








Am not doing anything fancy, just trying to update a field on Contact in JS of LWC but getting this exception.



Uncaught TypeError: 'set' on proxy: trap returned falsish for property 'Name'
throws at mydomain/auraFW/javascript/mhontaYdOya4Y_lBu7v9yg/aura_prod.js:2:27687



HTML Code:



<template>

<template if:true={wiredContact}>

{wiredContact.Name}

<lightning-input value={wiredContact.Name} onchange={updateName}></lightning-input>
</template>

</template>


JS:



import { LightningElement ,wire,track,api } from 'lwc';
import myContact from "@salesforce/apex/ContactController.fetchContact";

export default class Myrefreshapextest extends LightningElement {


@track wiredContact;

@wire (myContact)
fetchedContact({error, data}){
if(data){
console.log(JSON.stringify(data));
this.wiredContact = data;
}else if (error){
console.log(error);
}
}

updateName (event){
console.log(JSON.stringify(event.detail.value));
console.log(JSON.stringify(this.wiredContact));
this.wiredContact.Name = event.detail.value;
}

}


Apex:



public class ContactController {

@AuraEnabled(cacheable=true)
public static Contact fetchContact(){
return [SELECT Id,Name FROM COntact LIMIT 1];
}
}


On top of my head, am not doing anything wrong, anyone has idea what's wrong with my code?



When I print console.log(JSON.stringify(this.wiredContact)); I get old values so am pretty sure it exists.



I tried with @track and @api, but same response. Can anyone shed some light?










share|improve this question














Am not doing anything fancy, just trying to update a field on Contact in JS of LWC but getting this exception.



Uncaught TypeError: 'set' on proxy: trap returned falsish for property 'Name'
throws at mydomain/auraFW/javascript/mhontaYdOya4Y_lBu7v9yg/aura_prod.js:2:27687



HTML Code:



<template>

<template if:true={wiredContact}>

{wiredContact.Name}

<lightning-input value={wiredContact.Name} onchange={updateName}></lightning-input>
</template>

</template>


JS:



import { LightningElement ,wire,track,api } from 'lwc';
import myContact from "@salesforce/apex/ContactController.fetchContact";

export default class Myrefreshapextest extends LightningElement {


@track wiredContact;

@wire (myContact)
fetchedContact({error, data}){
if(data){
console.log(JSON.stringify(data));
this.wiredContact = data;
}else if (error){
console.log(error);
}
}

updateName (event){
console.log(JSON.stringify(event.detail.value));
console.log(JSON.stringify(this.wiredContact));
this.wiredContact.Name = event.detail.value;
}

}


Apex:



public class ContactController {

@AuraEnabled(cacheable=true)
public static Contact fetchContact(){
return [SELECT Id,Name FROM COntact LIMIT 1];
}
}


On top of my head, am not doing anything wrong, anyone has idea what's wrong with my code?



When I print console.log(JSON.stringify(this.wiredContact)); I get old values so am pretty sure it exists.



I tried with @track and @api, but same response. Can anyone shed some light?







lightning-web-components






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 11 hours ago









Pranay JaiswalPranay Jaiswal

18.6k53158




18.6k53158













  • Do you get same issue when you use the individual field names viz., FirstName?

    – Jayant Das
    11 hours ago











  • Same error Uncaught TypeError: 'set' on proxy: trap returned falsish for property 'FirstName' throws at its same error doesnt matter if its normal contact or personAccountContact.

    – Pranay Jaiswal
    11 hours ago













  • I got the error (not exactly the same) but was able to replicate. Seems like you cannot set a value directly to the property instead recreate the JSON and then assign. E.g., this.wiredContact = ["Name:" + event.detail.value]; this worked. Still trying to figure out.

    – Jayant Das
    11 hours ago











  • @JayantDas It's a design feature. One that I'm pretty sure isn't documented.

    – sfdcfox
    11 hours ago











  • @sfdcfox I just saw the behavior you mentioned just by trying it out, and it worked, even though my format above is not JSON, but I was intending that.

    – Jayant Das
    10 hours ago



















  • Do you get same issue when you use the individual field names viz., FirstName?

    – Jayant Das
    11 hours ago











  • Same error Uncaught TypeError: 'set' on proxy: trap returned falsish for property 'FirstName' throws at its same error doesnt matter if its normal contact or personAccountContact.

    – Pranay Jaiswal
    11 hours ago













  • I got the error (not exactly the same) but was able to replicate. Seems like you cannot set a value directly to the property instead recreate the JSON and then assign. E.g., this.wiredContact = ["Name:" + event.detail.value]; this worked. Still trying to figure out.

    – Jayant Das
    11 hours ago











  • @JayantDas It's a design feature. One that I'm pretty sure isn't documented.

    – sfdcfox
    11 hours ago











  • @sfdcfox I just saw the behavior you mentioned just by trying it out, and it worked, even though my format above is not JSON, but I was intending that.

    – Jayant Das
    10 hours ago

















Do you get same issue when you use the individual field names viz., FirstName?

– Jayant Das
11 hours ago





Do you get same issue when you use the individual field names viz., FirstName?

– Jayant Das
11 hours ago













Same error Uncaught TypeError: 'set' on proxy: trap returned falsish for property 'FirstName' throws at its same error doesnt matter if its normal contact or personAccountContact.

– Pranay Jaiswal
11 hours ago







Same error Uncaught TypeError: 'set' on proxy: trap returned falsish for property 'FirstName' throws at its same error doesnt matter if its normal contact or personAccountContact.

– Pranay Jaiswal
11 hours ago















I got the error (not exactly the same) but was able to replicate. Seems like you cannot set a value directly to the property instead recreate the JSON and then assign. E.g., this.wiredContact = ["Name:" + event.detail.value]; this worked. Still trying to figure out.

– Jayant Das
11 hours ago





I got the error (not exactly the same) but was able to replicate. Seems like you cannot set a value directly to the property instead recreate the JSON and then assign. E.g., this.wiredContact = ["Name:" + event.detail.value]; this worked. Still trying to figure out.

– Jayant Das
11 hours ago













@JayantDas It's a design feature. One that I'm pretty sure isn't documented.

– sfdcfox
11 hours ago





@JayantDas It's a design feature. One that I'm pretty sure isn't documented.

– sfdcfox
11 hours ago













@sfdcfox I just saw the behavior you mentioned just by trying it out, and it worked, even though my format above is not JSON, but I was intending that.

– Jayant Das
10 hours ago





@sfdcfox I just saw the behavior you mentioned just by trying it out, and it worked, even though my format above is not JSON, but I was intending that.

– Jayant Das
10 hours ago










2 Answers
2






active

oldest

votes


















3














Cached items are set as read-only (because otherwise you could corrupt the cache). If you want a modifiable object, you need to clone it.



this.wiredContact = Object.assign({}, data);





share|improve this answer
























  • +1 for Object.assign(). Didn't know something like this existed.

    – Jayant Das
    9 hours ago













  • Thanks sfdcfox. You are truly a Javascript wizard.

    – Pranay Jaiswal
    9 hours ago











  • @JayantDas In ES6, the syntactic sugar is: this.wiredContact = {...data};

    – tsalb
    4 hours ago













  • @tsalb Thanks for sharing. I now recollect coming it across on one of Pranay’s another question

    – Jayant Das
    4 hours ago



















1














This is what I could find from the documentation for wired service and that seems to be the case here (emphasis mine).




The wire service provisions an immutable stream of data to the component




So it most likely seems that when trying to set the values directly using this.wiredContact.Name, because of it's read only property, the values are not getting set.



However if you try to create a new data and then assign it to this.wiredContact, it works:



this.wiredContact = "{Name:" + event.detail.value + "}";





share|improve this answer
























  • This solution presumes only one field. If you have multiple fields, you must remember to encode all of them or lose data. The solution I presented avoids this problem by copying everything on initialization, leaving the variable free to be modified in all other function calls.

    – sfdcfox
    9 hours ago











  • Yeah, this was a more direct answer to the problem that Pranay had mentioned. I am not really good at JS, so didn't even know how to do so unless you mentioned.

    – Jayant Das
    9 hours ago











  • +1 thanks for linking documentation. This was freaking me out.

    – Pranay Jaiswal
    9 hours ago






  • 1





    I started looking only when @sfdcfox mentioned it was possibly not :) But at least it is mentioned. Easy to miss!

    – Jayant Das
    9 hours ago












Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "459"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f256761%2funcaught-typeerror-set-on-proxy-trap-returned-falsish-for-property-name%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









3














Cached items are set as read-only (because otherwise you could corrupt the cache). If you want a modifiable object, you need to clone it.



this.wiredContact = Object.assign({}, data);





share|improve this answer
























  • +1 for Object.assign(). Didn't know something like this existed.

    – Jayant Das
    9 hours ago













  • Thanks sfdcfox. You are truly a Javascript wizard.

    – Pranay Jaiswal
    9 hours ago











  • @JayantDas In ES6, the syntactic sugar is: this.wiredContact = {...data};

    – tsalb
    4 hours ago













  • @tsalb Thanks for sharing. I now recollect coming it across on one of Pranay’s another question

    – Jayant Das
    4 hours ago
















3














Cached items are set as read-only (because otherwise you could corrupt the cache). If you want a modifiable object, you need to clone it.



this.wiredContact = Object.assign({}, data);





share|improve this answer
























  • +1 for Object.assign(). Didn't know something like this existed.

    – Jayant Das
    9 hours ago













  • Thanks sfdcfox. You are truly a Javascript wizard.

    – Pranay Jaiswal
    9 hours ago











  • @JayantDas In ES6, the syntactic sugar is: this.wiredContact = {...data};

    – tsalb
    4 hours ago













  • @tsalb Thanks for sharing. I now recollect coming it across on one of Pranay’s another question

    – Jayant Das
    4 hours ago














3












3








3







Cached items are set as read-only (because otherwise you could corrupt the cache). If you want a modifiable object, you need to clone it.



this.wiredContact = Object.assign({}, data);





share|improve this answer













Cached items are set as read-only (because otherwise you could corrupt the cache). If you want a modifiable object, you need to clone it.



this.wiredContact = Object.assign({}, data);






share|improve this answer












share|improve this answer



share|improve this answer










answered 11 hours ago









sfdcfoxsfdcfox

263k12209456




263k12209456













  • +1 for Object.assign(). Didn't know something like this existed.

    – Jayant Das
    9 hours ago













  • Thanks sfdcfox. You are truly a Javascript wizard.

    – Pranay Jaiswal
    9 hours ago











  • @JayantDas In ES6, the syntactic sugar is: this.wiredContact = {...data};

    – tsalb
    4 hours ago













  • @tsalb Thanks for sharing. I now recollect coming it across on one of Pranay’s another question

    – Jayant Das
    4 hours ago



















  • +1 for Object.assign(). Didn't know something like this existed.

    – Jayant Das
    9 hours ago













  • Thanks sfdcfox. You are truly a Javascript wizard.

    – Pranay Jaiswal
    9 hours ago











  • @JayantDas In ES6, the syntactic sugar is: this.wiredContact = {...data};

    – tsalb
    4 hours ago













  • @tsalb Thanks for sharing. I now recollect coming it across on one of Pranay’s another question

    – Jayant Das
    4 hours ago

















+1 for Object.assign(). Didn't know something like this existed.

– Jayant Das
9 hours ago







+1 for Object.assign(). Didn't know something like this existed.

– Jayant Das
9 hours ago















Thanks sfdcfox. You are truly a Javascript wizard.

– Pranay Jaiswal
9 hours ago





Thanks sfdcfox. You are truly a Javascript wizard.

– Pranay Jaiswal
9 hours ago













@JayantDas In ES6, the syntactic sugar is: this.wiredContact = {...data};

– tsalb
4 hours ago







@JayantDas In ES6, the syntactic sugar is: this.wiredContact = {...data};

– tsalb
4 hours ago















@tsalb Thanks for sharing. I now recollect coming it across on one of Pranay’s another question

– Jayant Das
4 hours ago





@tsalb Thanks for sharing. I now recollect coming it across on one of Pranay’s another question

– Jayant Das
4 hours ago













1














This is what I could find from the documentation for wired service and that seems to be the case here (emphasis mine).




The wire service provisions an immutable stream of data to the component




So it most likely seems that when trying to set the values directly using this.wiredContact.Name, because of it's read only property, the values are not getting set.



However if you try to create a new data and then assign it to this.wiredContact, it works:



this.wiredContact = "{Name:" + event.detail.value + "}";





share|improve this answer
























  • This solution presumes only one field. If you have multiple fields, you must remember to encode all of them or lose data. The solution I presented avoids this problem by copying everything on initialization, leaving the variable free to be modified in all other function calls.

    – sfdcfox
    9 hours ago











  • Yeah, this was a more direct answer to the problem that Pranay had mentioned. I am not really good at JS, so didn't even know how to do so unless you mentioned.

    – Jayant Das
    9 hours ago











  • +1 thanks for linking documentation. This was freaking me out.

    – Pranay Jaiswal
    9 hours ago






  • 1





    I started looking only when @sfdcfox mentioned it was possibly not :) But at least it is mentioned. Easy to miss!

    – Jayant Das
    9 hours ago
















1














This is what I could find from the documentation for wired service and that seems to be the case here (emphasis mine).




The wire service provisions an immutable stream of data to the component




So it most likely seems that when trying to set the values directly using this.wiredContact.Name, because of it's read only property, the values are not getting set.



However if you try to create a new data and then assign it to this.wiredContact, it works:



this.wiredContact = "{Name:" + event.detail.value + "}";





share|improve this answer
























  • This solution presumes only one field. If you have multiple fields, you must remember to encode all of them or lose data. The solution I presented avoids this problem by copying everything on initialization, leaving the variable free to be modified in all other function calls.

    – sfdcfox
    9 hours ago











  • Yeah, this was a more direct answer to the problem that Pranay had mentioned. I am not really good at JS, so didn't even know how to do so unless you mentioned.

    – Jayant Das
    9 hours ago











  • +1 thanks for linking documentation. This was freaking me out.

    – Pranay Jaiswal
    9 hours ago






  • 1





    I started looking only when @sfdcfox mentioned it was possibly not :) But at least it is mentioned. Easy to miss!

    – Jayant Das
    9 hours ago














1












1








1







This is what I could find from the documentation for wired service and that seems to be the case here (emphasis mine).




The wire service provisions an immutable stream of data to the component




So it most likely seems that when trying to set the values directly using this.wiredContact.Name, because of it's read only property, the values are not getting set.



However if you try to create a new data and then assign it to this.wiredContact, it works:



this.wiredContact = "{Name:" + event.detail.value + "}";





share|improve this answer













This is what I could find from the documentation for wired service and that seems to be the case here (emphasis mine).




The wire service provisions an immutable stream of data to the component




So it most likely seems that when trying to set the values directly using this.wiredContact.Name, because of it's read only property, the values are not getting set.



However if you try to create a new data and then assign it to this.wiredContact, it works:



this.wiredContact = "{Name:" + event.detail.value + "}";






share|improve this answer












share|improve this answer



share|improve this answer










answered 10 hours ago









Jayant DasJayant Das

18k21330




18k21330













  • This solution presumes only one field. If you have multiple fields, you must remember to encode all of them or lose data. The solution I presented avoids this problem by copying everything on initialization, leaving the variable free to be modified in all other function calls.

    – sfdcfox
    9 hours ago











  • Yeah, this was a more direct answer to the problem that Pranay had mentioned. I am not really good at JS, so didn't even know how to do so unless you mentioned.

    – Jayant Das
    9 hours ago











  • +1 thanks for linking documentation. This was freaking me out.

    – Pranay Jaiswal
    9 hours ago






  • 1





    I started looking only when @sfdcfox mentioned it was possibly not :) But at least it is mentioned. Easy to miss!

    – Jayant Das
    9 hours ago



















  • This solution presumes only one field. If you have multiple fields, you must remember to encode all of them or lose data. The solution I presented avoids this problem by copying everything on initialization, leaving the variable free to be modified in all other function calls.

    – sfdcfox
    9 hours ago











  • Yeah, this was a more direct answer to the problem that Pranay had mentioned. I am not really good at JS, so didn't even know how to do so unless you mentioned.

    – Jayant Das
    9 hours ago











  • +1 thanks for linking documentation. This was freaking me out.

    – Pranay Jaiswal
    9 hours ago






  • 1





    I started looking only when @sfdcfox mentioned it was possibly not :) But at least it is mentioned. Easy to miss!

    – Jayant Das
    9 hours ago

















This solution presumes only one field. If you have multiple fields, you must remember to encode all of them or lose data. The solution I presented avoids this problem by copying everything on initialization, leaving the variable free to be modified in all other function calls.

– sfdcfox
9 hours ago





This solution presumes only one field. If you have multiple fields, you must remember to encode all of them or lose data. The solution I presented avoids this problem by copying everything on initialization, leaving the variable free to be modified in all other function calls.

– sfdcfox
9 hours ago













Yeah, this was a more direct answer to the problem that Pranay had mentioned. I am not really good at JS, so didn't even know how to do so unless you mentioned.

– Jayant Das
9 hours ago





Yeah, this was a more direct answer to the problem that Pranay had mentioned. I am not really good at JS, so didn't even know how to do so unless you mentioned.

– Jayant Das
9 hours ago













+1 thanks for linking documentation. This was freaking me out.

– Pranay Jaiswal
9 hours ago





+1 thanks for linking documentation. This was freaking me out.

– Pranay Jaiswal
9 hours ago




1




1





I started looking only when @sfdcfox mentioned it was possibly not :) But at least it is mentioned. Easy to miss!

– Jayant Das
9 hours ago





I started looking only when @sfdcfox mentioned it was possibly not :) But at least it is mentioned. Easy to miss!

– Jayant Das
9 hours ago


















draft saved

draft discarded




















































Thanks for contributing an answer to Salesforce Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f256761%2funcaught-typeerror-set-on-proxy-trap-returned-falsish-for-property-name%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

El tren de la libertad Índice Antecedentes "Porque yo decido" Desarrollo de la...

Puerta de Hutt Referencias Enlaces externos Menú de navegación15°58′00″S 5°42′00″O /...

Castillo d'Acher Características Menú de navegación