Not sure what is going wrong here, as I’m getting UNPARSEABLE error when using the formula below. =IF([Risk Rating Calculation]@row This does not give any errors and works as expected All the syntax seems to be matching what is shown in the examples as well… Any suggestions?

IF formula Unparseable error when using strings

Mirest

Not sure what is going wrong here, as I’m getting UNPARSEABLE error when using the formula below.

=IF([Risk Rating Calculation]@row<5,”yes”,”no”)

If I were to use numbers instead of the strings “yes” and “no” I do not get any errors (example below).

=IF([Risk Rating Calculation]@row<5,12,10) -> This does not give any errors and works as expected

All the syntax seems to be matching what is shown in the examples as well… Any suggestions?

Find more posts tagged with

Accepted answers

GrahamWelsby

Hi, I've copied and pasted your formula into a sheet and had a few instances of UNPARSEABLE.

First was that your double quotes were a bit funny, replaced them and got it working, second was if the column name was a slightly different.

Check the double quotes first - although this could be a font thing here?

All comments

GrahamWelsby

Hi, I've copied and pasted your formula into a sheet and had a few instances of UNPARSEABLE.

First was that your double quotes were a bit funny, replaced them and got it working, second was if the column name was a slightly different.

Check the double quotes first - although this could be a font thing here?

Mirest

This seems to have worked! When I enter the formula on macOS I do get that error message and the double quotation marks do look different. When I ask my coworker to enter the exact replica of this formula on their windows machine, the quotation marks look different than macOS and the formula works.

It is really weird, as I’ve never had such a discrepancy between operating systems before, or related to fonts. You’d think that both these are interpreted as double quotation marks by Smartsheet regardless…

GrahamWelsby

@Mirest Glad it worked, very strange that it would do that, but at least you got it working.

Sign in to join the conversation!

Quick Links

Component react.discussion.discussions had an error.

ref must be one of: categoryID, siteSectionID, category, category/categoryID, category/name, category/description, category/url, category/allowedDiscussionTypes, locale, siteSection, siteSection/basePath, siteSection/contentLocale, siteSection/sectionGroup, siteSection/sectionID, siteSection/name, siteSection/description, siteSection/apps, siteSection/attributes, layoutViewType, discussionID, commentID, page, latest, sort, sortType, lookupSort, discussion, discussion/name, tags, breadcrumbs, discussionApiParams, serverDraftID, serverDraft.