I was setting up a blog, then, and even considering a new note-taking setup, and future-proofing became an even greater concern for me.
So, weeks later, when I stumbled upon Jeff Huang’s manifesto “Designed to Last”, it deeply resonated with me. I could remember many of those websites and pages, I could recall how and why they were important to me I just couldn’t see them. I’ve been keeping bookmarks for longer than that.Ī few months ago, I subscribed to Pinboard and imported all these 1000+ bookmarks, only to find that hundreds of them were dead links. I've been taking plain text notes on my computer for almost 20 years. You can then use those WFTextABC columns in Power BI reports, workflows, if/then statements, calculated columns and more where we couldn’t before with lookup values.Following the advice dang left in the comments, here’s the backstory for this workflow: That’s it! Publish your workflow, and your lookup columns’ values will always be converted to text. This just ensures your text fields are always being updated to the lookup values. Go to the workflow settings and, under “Start Options”, set this to run manually, when items are created and when items are modified.Click OK twice, and repeat steps 5-7 for each field you need to have converted.Find the lookup column for the second field, and set “return field as” to “Lookup Value (as Text)”.Then click the “function” button next to “to this value”. Click “Add” and find the new TEXT field that matches the lookup column field you’re setting.Name and describe your workflow, then select SharePoint 2010 Workflow as platform type.Create a SPD 2010 Workflow on the list which you’d like text values instead of lookup values.A new single line of text column for each lookup column you want to “convert” to text (i.e.And remember, you can start a 2010 workflow from within a 2013 workflow, so it shouldn’t interfere too much with your larger processes. You must use a SharePoint Designer 2010 workflow for this to work.
PLAIN TEXT WORKFLOW TRIAL
Feel free to comment with your scenario specifics – I’ve had a lot of experience with this error, and would be happy to help.įirst and foremost, note that much of my trial and error was with SharePoint Designer 2013 workflows and Microsoft Flow.