Forum Discussion
Send a Mail When a Field in a SharePoint List has a value of Yes
Rob Ellis Thanks Rob, and thanks especially for the quick response. I actually had this method reserved as a 'Plan B'. Glad to report it worked though, exactly as you suggested (I finished testing it literally seconds after you replied!). Took a while to setup (list has over 100 columns, so a lot of monotony deleting values out of the 'Update list item' part of the flow), so I was reluctant to jump straight to that method.
Still just have that niggly feeling that there must be a simpler way.
Ah well. If it ain't broke...
kevinmckeown8 Thanks Kevin (and thanks for providing the answers on this post in the first place). Now that I have these additional columns, purely used for the Flow to work, then my next task is figuring out how to hide them from view (...but that's another story for another day, another pertinent forum post I need to find).
Dave Palmer If you go into the List Settings, you can go down to Views, select the view to modify, then select which columns are shown in that view.
Additionally, if you want to keep columns from showing in New/Edit Forms, then you need to:
- Go to List Settings
- Go to Advanced Settings
- Set "Allow management of content types?" to Yes. Click OK.
- On the List Settings page you should now see a "Content Types" section. Click the "Item" content type.
- Click one of the columns you want to hide from forms.
- Change the column setting to "Hidden (will not appear in forms)". Click OK.
- Do this for all columns that you want hidden from forms.
- Once done, go back to Advanced Settings and set the "Allow management of content types?" back to No.
- If you leave content type management on, then your forms will always show a "Content Type" dropdown at the top of the form.
kevinmckeown8 Thanks Kevin. I knew how to hide columns from a view, but didn't have a clue how to hide them from new forms (so that's REALLY helpful).
I was concerned about going 'off topic' here (don't like upsetting the forum Gods), but to be honest - you've made me think of a pertinent question/point.
Not sure what I was doing wrong, but it seems the only way I've eventually got these Flows working is by using the 'Limit Columns by View' setting, early on in the Flow (i.e. in the Trigger). Could just be that I was fumbling at first, but all of my Flows have this in place. It 'felt like' I simply had so many columns in my list (over 100) that I HAD to use this.
So I wasn't going to rush and hide these extra columns I've needed to add (just to get this one working) from the view. Presumably, if I'm limiting columns by view (call it 'View A')... then if I remove columns which I'm using in the Flow from View A, then it's not going to work.
I know, I know... I need to test it.
Just thought that if you could shed any light on the 'Limit Columns by View' setting, it could help others finding this thread in future (and help me understand more too). Feel free to point me to another post if there is one (I probably should have checked first).
