We have a bunch of Field Editors on a page, and we have buttons to move them in and out of Edit mode (using a Global Action Sequence, but this is irrelevant) that fires a bunch of “Run Component Actions”. I have two sequences that specifically move them between edit and read, because using Toggle 1) didn’t solve this problem and 2) seemed to introduce other problems!
So on each action we have a sequence of these on each field editor:
Now, these “work” - but they only work if the table’s original mode was “Read with Inline-Edit” - and when you run the action to put them back into “Read Mode” - it puts them back in to “Read with Inline-Edit”.
ie. If we make the field editor “Read Mode” on the page - the Component Action cannot switch it into Edit mode (it simply doesn’t change).
Has anyone else experienced this? Or think it’s a bit weird. I really don’t want inline edit mode on the editors, we want the user to make a conscious decision to switch to edit mode (as we do other stuff then too).
I want to go:
Read -> Edit - > Read (and so on)
not
Read with Inline Edit -> Edit -> Read with inline Edit
Is that just the way it works? So am I going to have to replace the actions sequences with a bunch of Javascript?! (again?!)
Ok, excellent, thank you! I will have a word with the technical lead and see if/when a Skuid update is scheduled (and I’ll also let you know if this doesn’t resolve it )
I am unable to toggle between Edit/Read with a component action if the field editor default mode is set to “Read”, nothing happens. The field editor default mode must be set to “Read with In-Line Edit” (Read with In-Line Edit –> Edit –> Read with In-Line Edit)
However, if my field editor default mode is set to “Edit” I can toggle between Edit/Read (Edit–>Read–>Edit).
I actually just ran into this and was talking to our Product Designer. This was an intentional decision when the toggle actions were built. But we are exploring changing it so a form or table could be put in Read Only mode - and then toggled into Edit mode - and back. Stay tuned.
No - the mode (read only -v- edit) is set at the component level. you can’t declare that all components in a tab should be read only.
Also - there is not a way to make a tab “inactive” so users cannot activate it. We do have 'conditional rendering" on the tab - so you could hide the tab entirely, or you could hide the tabs contents, but if the tab is present - a user will e able to click on it.