Conditionally enable edit in lightning:datatableCustom html label in lightning:buttonWinter 18...
What was Apollo 13's "Little Jolt" after MECO?
Work requires me to come in early to start computer but wont let me clock in to get paid for it
I preordered a game on my Xbox while on the home screen of my friend's account. Which of us owns the game?
Does the damage from the Absorb Elements spell apply to your next attack, or to your first attack on your next turn?
How to have a sharp product image?
`microtype`: Set Minimum Width of a Space
What to do with someone that cheated their way through university and a PhD program?
Retract an already submitted recommendation letter (written for an undergrad student)
A Note on N!
Does Mathematica have an implementation of the Poisson binomial distribution?
Negative Resistance
Why do distances seem to matter in the Foundation world?
Island of Knights, Knaves and Spies
Could moose/elk survive in the Amazon forest?
Unknown code in script
Complex numbers z=-3-4i polar form
Co-worker works way more than he should
Drawing a german abacus as in the books of Adam Ries
Suing a Police Officer Instead of the Police Department
Where was the County of Thurn und Taxis located?
Find a stone which is not the lightest one
What does "function" actually mean in music?
Is there any pythonic way to find average of specific tuple elements in array?
How much of a wave function must reside inside event horizon for it to be consumed by the black hole?
Conditionally enable edit in lightning:datatable
Custom html label in lightning:buttonWinter 18 <lightning:datatable> problemsSpring 18 <lightning:datatable> how to add a button columnlightning:datatable component - hiding Save and Cancel buttons after inline editHelp with working with lightning:dataTable?Reload after “e.force:editRecord”?Conditionally Render Button in lightning:datatablelightning:datatable set columns dynamicalyStatic values for `<lightning:datatable>`lightning:datatable won't show data in column with type of 'boolean'
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
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
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
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
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
lightning-aura-components lightning lightning-datatable
edited 4 hours ago
Jayant Das
19.4k21331
19.4k21331
asked 5 hours ago
M. MassulaM. Massula
312
312
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
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.
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
});
}
});
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
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
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
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.
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.
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.
answered 4 hours ago
Jayant DasJayant Das
19.4k21331
19.4k21331
add a comment |
add a comment |
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.
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
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
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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