ToLower() fails with null but the input isn't null

(0) Share

Report

Posted on by ShawnKeeneTF

106

I am building a flow that alerts me if an email arrives that has certain words in the subject or is urgent.

The flow fires when an email arrives, and then checks if any of those conditions are true.

It worked somewhat okay, but in testing I discovered that it is case-sensitive, so I need to convert it to lowercase before I check the strings.

And this is where I need help. I thought it would simply be toLower(triggerOutputs()?['body/subject']) but when I tried that I meet a failure.

The toLower() function I used was written by me first, but when I tried the "suggest function by examples" the system also suggested the same formula. The error says it found a null input but none of my inputs are null in this case (of course it does need to handle an empty subject or importance anyway).

Setup:

Failure: Input is null. The email subject and importance were not null.

What am I missing?

PS another user with basically the question: Building an autoreply flow

Categories:

Building flows

I have the same question (0)

All responses (6)

Answers (1)

abm abm 32,865 Most Valuable Professional on at

Like (0)

Report

Hi @ShawnKeeneTF

Add an AND condition first to evaluate its not null AND add all the other conditions with OR.

Thanks

Was this reply helpful? Yes No
ShawnKeeneTF 106 on at

Like (0)

Report

I'm sorry I'm not clearly understanding where to add that... but in my example case none of these were null so that really shouldn't have been the true problem, right? My subject and importance fields were non-null in my test case.

Was this reply helpful? Yes No
abm abm 32,865 Most Valuable Professional on at

Like (0)

Report

Hi @ShawnKeeneTF

According to the error it is null. Did you checked the run history? Open the run history and inspect the trigger step. Check the values?

Was this reply helpful? Yes No
Verified answer

wskinnermctc 6,519 Moderator on at

Like (1)

Report

I just tested this multiple times even with a blank subject and the expression still worked. I double checked your expression and it appears correct to me.

Can you try deleting your condition step and reapplying the expressions?

Sometimes those boxes have previous expressions hidden in them that are hard to see. Like the expression might be applied twice or something in the same box but you can't see it.

I can't tell why your flow is not working.

Was this reply helpful? Yes No
ShawnKeeneTF 106 on at

Like (2)

Report

Crazy that must have been it. I just created a new condition step that is absolutely identical and now it works totally fine. Crazy. Well I appreciate your help and time no less at all, thanks for the quick discussion.

Was this reply helpful? Yes No
abm abm 32,865 Most Valuable Professional on at

Like (1)

Report

Hi @ShawnKeeneTF @wskinnermctc

Think there is a bug in the flow designer that if you edit expression sometimes it won't update it for the first time. So always when you update an existing expression place your cursor over the expression and check via tooltip whether it is updated or not. If not edit the expression and update again. In my experience second time it always works. Something to remember next time.

Glad to hear that all sorted.

Thanks

Was this reply helpful? Yes No