Kdtyjb

Check if a string is entirely made of the same substring

How to not starve gigantic beasts

Air bladders in bat-like skin wings for better lift?

What to do with someone that cheated their way through university and a PhD program?

Which big number is bigger?

How to keep bees out of canned beverages?

Negative Resistance

How to find the stem of any word?

Crossed out red box fitting tightly around image

Why didn't the Space Shuttle bounce back into space as many times as possible so as to lose a lot of kinetic energy up there?

Co-worker works way more than he should

Multiple options vs single option UI

Why must Chinese maps be obfuscated?

How important is it that $TERM is correct?

Why do games have consumables?

Will I lose my paid in full property

Is Diceware more secure than a long passphrase?

Can a level 2 Warlock take one level in rogue, then continue advancing as a warlock?

"My boss was furious with me and I have been fired" vs. "My boss was furious with me and I was fired"

Is there any pythonic way to find average of specific tuple elements in array?

The weakest link

std::unique_ptr of base class holding reference of derived class does not show warning in gcc compiler while naked pointer shows it. Why?

Double-nominative constructions and “von”

How exactly does Hawking radiation decrease the mass of black holes?

Conditionally enable edit in lightning:datatable

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

1

I'm trying to do a dynamic editable field, this is what I've got:

Component

<lightning:datatable columns="{!v.columns}"

            data="{! v.data }"

            keyField="{! v.keyField }"

            onsave="{! c.handleSaveEdition }"

            />

data

[

    {field1: 't1c1', field2: 't1c2', field3: 't1c3', field3Editable: true},

    {field1: 't2c1', field2: 't2c2', field3: 't3c3', field3Editable: true},

    {field1: 't2c1', field2: 't2c2', field3: 't3c3', field3Editable: false},

];

column

[

    {label: 'Col 1', fieldName: 'field1', type: 'text', sortable: false},

    {label: 'Col 2', fieldName: 'field2', type: 'text', sortable: false},

    {label: 'Col 3', fieldName: 'field3', type: 'text', sortable: false, editable: {fieldName: 'field3Editable'}},

];

but even with the last "field3Editable" from data seted as false the field appears as editable.

lightning-aura-components lightning lightning-datatable

share|improve this question

edited 1 hour ago

Jayant Das

19.4k21331

asked 2 hours ago

M. MassulaM. Massula

262

add a comment | 

1

I'm trying to do a dynamic editable field, this is what I've got:

Component

<lightning:datatable columns="{!v.columns}"

            data="{! v.data }"

            keyField="{! v.keyField }"

            onsave="{! c.handleSaveEdition }"

            />

data

[

    {field1: 't1c1', field2: 't1c2', field3: 't1c3', field3Editable: true},

    {field1: 't2c1', field2: 't2c2', field3: 't3c3', field3Editable: true},

    {field1: 't2c1', field2: 't2c2', field3: 't3c3', field3Editable: false},

];

column

[

    {label: 'Col 1', fieldName: 'field1', type: 'text', sortable: false},

    {label: 'Col 2', fieldName: 'field2', type: 'text', sortable: false},

    {label: 'Col 3', fieldName: 'field3', type: 'text', sortable: false, editable: {fieldName: 'field3Editable'}},

];

but even with the last "field3Editable" from data seted as false the field appears as editable.

lightning-aura-components lightning lightning-datatable

share|improve this question

edited 1 hour ago

Jayant Das

19.4k21331

asked 2 hours ago

M. MassulaM. Massula

262

add a comment | 

I'm trying to do a dynamic editable field, this is what I've got:

Component

<lightning:datatable columns="{!v.columns}"

            data="{! v.data }"

            keyField="{! v.keyField }"

            onsave="{! c.handleSaveEdition }"

            />

data

[

    {field1: 't1c1', field2: 't1c2', field3: 't1c3', field3Editable: true},

    {field1: 't2c1', field2: 't2c2', field3: 't3c3', field3Editable: true},

    {field1: 't2c1', field2: 't2c2', field3: 't3c3', field3Editable: false},

];

column

[

    {label: 'Col 1', fieldName: 'field1', type: 'text', sortable: false},

    {label: 'Col 2', fieldName: 'field2', type: 'text', sortable: false},

    {label: 'Col 3', fieldName: 'field3', type: 'text', sortable: false, editable: {fieldName: 'field3Editable'}},

];

but even with the last "field3Editable" from data seted as false the field appears as editable.

lightning-aura-components lightning lightning-datatable

share|improve this question

edited 1 hour ago

Jayant Das

19.4k21331

asked 2 hours ago

M. MassulaM. Massula

262

<lightning:datatable columns="{!v.columns}"

            data="{! v.data }"

            keyField="{! v.keyField }"

            onsave="{! c.handleSaveEdition }"

            />

[

    {field1: 't1c1', field2: 't1c2', field3: 't1c3', field3Editable: true},

    {field1: 't2c1', field2: 't2c2', field3: 't3c3', field3Editable: true},

    {field1: 't2c1', field2: 't2c2', field3: 't3c3', field3Editable: false},

];

[

    {label: 'Col 1', fieldName: 'field1', type: 'text', sortable: false},

    {label: 'Col 2', fieldName: 'field2', type: 'text', sortable: false},

    {label: 'Col 3', fieldName: 'field3', type: 'text', sortable: false, editable: {fieldName: 'field3Editable'}},

];

share|improve this question

edited 1 hour ago

Jayant Das

19.4k21331

asked 2 hours ago

M. MassulaM. Massula

262

share|improve this question

edited 1 hour ago

Jayant Das

19.4k21331

asked 2 hours ago

M. MassulaM. Massula

262

edited 1 hour ago

Jayant Das

19.4k21331

edited 1 hour ago

Jayant Das

19.4k21331

asked 2 hours ago

M. MassulaM. Massula

262

asked 2 hours ago

M. MassulaM. Massula

262

1 Answer
1

active

oldest

votes

3

Per documentation, the editable attribute for lightning:datatable is applicable directly at the column level, and it does not mention anything at cell level, excerpt below:

Specifies whether a column supports inline editing. The default is false.

With a quick test, I could confirm that you won't be able to disable a particular cell in a lightning:datatable with the syntax you have currently. With what you have currently editable: {fieldName: 'field3Editable'} is not the right syntax based on the documentation. The attribute itself should be set to editable: true or editable: false.

The syntax that you have currently seems to be always evaluated as editable: true by the platform, most likely it simply ignores any error and sets it to true. Even if you say have something as editable: {nonExistentFieldName: 'nonExistentFieldValue'} you will be still able to see that the cells are editable.

If you want to disable any particular cell, you may have to look at alternative solutions here as you may not be able to achieve it using lightning:datatable.

share|improve this answer

answered 1 hour ago

Jayant DasJayant Das

19.4k21331

add a comment | 

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

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f260099%2fconditionally-enable-edit-in-lightningdatatable%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

3

Per documentation, the editable attribute for lightning:datatable is applicable directly at the column level, and it does not mention anything at cell level, excerpt below:

Specifies whether a column supports inline editing. The default is false.

With a quick test, I could confirm that you won't be able to disable a particular cell in a lightning:datatable with the syntax you have currently. With what you have currently editable: {fieldName: 'field3Editable'} is not the right syntax based on the documentation. The attribute itself should be set to editable: true or editable: false.

The syntax that you have currently seems to be always evaluated as editable: true by the platform, most likely it simply ignores any error and sets it to true. Even if you say have something as editable: {nonExistentFieldName: 'nonExistentFieldValue'} you will be still able to see that the cells are editable.

If you want to disable any particular cell, you may have to look at alternative solutions here as you may not be able to achieve it using lightning:datatable.

share|improve this answer

answered 1 hour ago

Jayant DasJayant Das

19.4k21331

add a comment | 

3

Per documentation, the editable attribute for lightning:datatable is applicable directly at the column level, and it does not mention anything at cell level, excerpt below:

Specifies whether a column supports inline editing. The default is false.

With a quick test, I could confirm that you won't be able to disable a particular cell in a lightning:datatable with the syntax you have currently. With what you have currently editable: {fieldName: 'field3Editable'} is not the right syntax based on the documentation. The attribute itself should be set to editable: true or editable: false.

The syntax that you have currently seems to be always evaluated as editable: true by the platform, most likely it simply ignores any error and sets it to true. Even if you say have something as editable: {nonExistentFieldName: 'nonExistentFieldValue'} you will be still able to see that the cells are editable.

If you want to disable any particular cell, you may have to look at alternative solutions here as you may not be able to achieve it using lightning:datatable.

share|improve this answer

answered 1 hour ago

Jayant DasJayant Das

19.4k21331

add a comment | 

Per documentation, the editable attribute for lightning:datatable is applicable directly at the column level, and it does not mention anything at cell level, excerpt below:

Specifies whether a column supports inline editing. The default is false.

With a quick test, I could confirm that you won't be able to disable a particular cell in a lightning:datatable with the syntax you have currently. With what you have currently editable: {fieldName: 'field3Editable'} is not the right syntax based on the documentation. The attribute itself should be set to editable: true or editable: false.

The syntax that you have currently seems to be always evaluated as editable: true by the platform, most likely it simply ignores any error and sets it to true. Even if you say have something as editable: {nonExistentFieldName: 'nonExistentFieldValue'} you will be still able to see that the cells are editable.

If you want to disable any particular cell, you may have to look at alternative solutions here as you may not be able to achieve it using lightning:datatable.

share|improve this answer

answered 1 hour ago

Jayant DasJayant Das

19.4k21331

share|improve this answer

answered 1 hour ago

Jayant DasJayant Das

19.4k21331

answered 1 hour ago

Jayant DasJayant Das

19.4k21331

answered 1 hour ago

Jayant DasJayant Das

19.4k21331