Best Of
Re: TODAY() not updating till the file is opened
@Avinash Chandra This has been the case for as long as I can remember. The sheet must be activated for the TODAY function to update. Whether this is through actually opening the sheet, update requests, form submissions, automations, or other methods, the sheet needs to be activated.
The method I use is to insert a date type column and set a Record a Date automation to run everyday at 12:00am and record the date in my date type helper column. I have never had an issue with this since I implemented it.
Paul Newcome
Re: Welcome to the B2B Work Management Community!
Thanks for the solid advice @kowal, I appreciate it.
Isis Taylor
Re: NEW! Custom dashboard themes
This is yet again a feature that has been very needed! I have already begun using it! THANK YOU SMARTSHEET.
Paul.Woodward
Re: Table view initial release is now generally available for all customers!
Love that quick search feature at the top!
Dakota Haeffner
Re: Table view initial release is now generally available for all customers!
What! Sort and Filter at the same time! Well I'll be!
nbers
Re: Table view initial release is now generally available for all customers!
It's going to be a big year⦠lots of "finally" moments!
Matt Lynn ACT
Re: How to show a blank instead of 0 using countsif?
I'm guessing your goal here is to shut down the visual noise created in a sheet if there's zeroes everywhere. So you have two options:
=IF(COUNTIFS ({MY25 CTM Detail Report Range 1}, "(7)Other Matter Requiring Plan Review")=0,"",COUNTIFS ({MY25 CTM Detail Report Range 1}, "(7)Other Matter Requiring Plan Review"))
Basically, create the formula so COUNTIF is mentioned twice: once to evaluate if it's 0, and a second time to tell Smartsheet what to do if it's NOT 0. Your formula is looking at the entire range of what appears to include text, so it's not going to be 0.
Option 2 would keep the value in the cell - possibly helpful if you need to create dashboard visualizations, or if you ever want to do math on this column. (The "" is basically saying "THIS CELL IS TEXT" so you could be forcing an #UNPARSEABLE error.) Don't make it blank, but rather use conditional formatting - if the countif column = 0, color the font in that cell white on white (or to match whatever your default background is).
Whichever direction you decide to go, good luck!
Kerry St. Thomas
Re: Customize Widget Colors w/o Being Locked into the Theme
Barak,
You've interpreted my feedback correctly. I would like optionality to individually change widget colors.
Thank you,
ColinG001
Re: Bridge Add columns based on values within multi-picklist
I've thought of a way to bypass this error, and allow you to have one Parent workflow with all the Child Workflow Modules below it.
In each of your Child Workflows, add the "Get Sheet" and "Array Management: Extract Field from Array" modules to get all the Column Names in the sheet before looping through to add the new column if there's a multi-select match.
This way you can add in a CONTAINS Junction to see if the array of column names in this sheet contains the name of the new column already:
If there's a column already in the sheet with that person's name, the child workflow will have a successful result (result of nothing) which will prevent it from ending in an error.
I've added in two fail states just so they appear in my run log and I can keep track of how the workflow is going through each module.
Here are the pieces broken down:
Get Sheet
Copy the Data Reference to the Columns array.
Array Management: Extract Field from Array
Uses the Column Array reference to grab the title key.
Get the data reference to this new array of ONLY the column titles.
CONTAINS Junction
Look through the new Column Array as the Values to search, and use the runtime.entities.Name that was pulled from your Parent workflow to check if that name exists as a Content in the Array (or whatever you're using as the new column name).
The SUCCESS state (the column name already exists in the array) is just a plain state with a title for my run log. This will cause the workflow to end in SUCCESS but to take no action.
The FAIL state (no column exists) is the MATCH junction that we already had set up, where if there is no column and if the value (e.g. "AZ") exists in the multi-select array, it adds the column. Otherwise, even if the column does not exist, if there is no matching multi-select value it does nothing.
Let me know if this makes sense and will work for you.
Cheers,
Genevieve
Genevieve P.