Answered

Sporadic issue: The second argument to the 'Left' function is invalid

(1) Share

Report

Posted on by sthota

139

Hello Team,

We've been facing a peculiar issue with our app recently. We are getting a notification saying "the second argument to the 'Left' function is invalid error" when we are trying to patch a lookup column only with certain records sporadically. However, there is no impact on w.r.t functionality. I tried to debug using First(Errors('Table_Name')).Message for the table that we are trying to patch and we do not see any issues whatsoever.

FYI, I tried both syntaxes such as saving the lookup column record into a variable and then patching it as well as adding a LookUp() method directly into the patch without any luck. Did any syntax change recently?
If I stop patching a LookUp column then I am not seeing this issue there.

Also, we are getting this issue in a couple of other places such as ResetForm(Form_Name) and Navigate methods also. It's happening very recently. We never had any issues with the same piece of code before.

Thanks,
Srinivas

Categories:

Building Power Apps

I have the same question (0)

All responses (11)

Answers (1)

Verified answer

RandyHayes 76,299 Super User 2024 Season 1 on at

Like (1)

Report
Copy link

Link copied!

@sthota

You will need to identify the formula that is producing the error.

Use the Monitor Tool to try and identify where the error is happening. Then review the parameters of the Left function to determine the problem.

I hope this is helpful for you.

Was this reply helpful? Yes No
sthota 139 on at

Like (0)

Report
Copy link

Link copied!

@RandyHayes Thank you so much for your insights and prompt response. We could find the root cause of this issue in one place using the monitor tool already. We will try and fix it and see if that resolves the issue.

Thanks,
Srinivas

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

I am also seeing this issue today.
My left function was LEFT(string,LEN(string)-1)

And in my case, there were cases when the string was blank and my -1 was causing this sporadically. (Only when the string variable was blank for some items)

Was this reply helpful? Yes No
RandyHayes 76,299 Super User 2024 Season 1 on at

Like (0)

Report
Copy link

Link copied!

@Anonymous

As with the guidance in this post - you will need to run the monitor tool to tray and identify the formula that has that function in it.

Was this reply helpful? Yes No
sthota 139 on at

Like (1)

Report
Copy link

Link copied!
@Anonymous I was facing a similar issue and I replaced with the following code to avoid these issues.
If( Not(IsBlank(FieldName)), Trim( Last( FirstN( Split( FieldName, "," ), 1 ) ).Result ), "" )

Was this reply helpful? Yes No
zacblais 4 on at

Like (0)

Report
Copy link

Link copied!
Hi @RandyHayes -- I've run into a similar situation with an empty string causing issues where a non-empty string behaves as expected. Notably, the field reporting the error does not include Left at all:
ThisItem.'Asset type' & If( Not(ThisItem.'Asset type' = "Resource"), " - " & Switch( ThisItem.'Course type', "Web-Based Training", "WBT", "Instructor Led Training", "ILT", "On-the-Job Training", "OJT", "Other" ) )
When a filter would leave ThisItem.'Asset type' empty, the error appears. Otherwise no error appears, as expected. This probably isn't too helpful in diagnosing it, but it does at least seem to be more than just a syntax error.

Was this reply helpful? Yes No
fellow_chucker 4 on at

Like (0)

Report
Copy link

Link copied!

I am having the same issue. Judging from this thread, these errors only recently started popping up. This suggests to me that there was some change to the way that this now functions. I have been using the "LEFT(string,LEN(string)-1)" for ages without any issue, and now, all of a sudden it doesn't work... This is extremely frustrating.
The field that I use it on first separates Combo box selections:
UpdateContext({combined_variable: Concat(ComboBox.SelectedItems,Value & ",")});
and then removes the last character:
LEFT(string,LEN(string)-1)
It is only this LEFT function that is causing my errors, and only starting yesterday for me, but the App hasn't been used in a while, so it wouldn't have come up.
If anyone has any real solutions, I would appreciate it. For now, as much as it pains me to do, I will have to allow for the trailing comma to remain.

Was this reply helpful? Yes No
fellow_chucker 4 on at

Like (0)

Report
Copy link

Link copied!

I don't understand how this has been allowed as a solution... this simply identifies how to find the issue, not how to solve it. The Left function is still causing errors. Judging from this thread, these errors only recently started popping up. This suggests to me that there was some change to the way that this now functions. I have been using the "LEFT(string,LEN(string)-1)" for ages without any issue, and now, all of a sudden it doesn't work.
The field that I use it on first separates Combo box selections:
UpdateContext({combined_variable: Concat(ComboBox.SelectedItems,Value & ",")});
and then removes the last character:
LEFT(string,LEN(string)-1)
It is only this LEFT function that is causing my errors, and only starting yesterday for me, but the App hasn't been used in a while, so it wouldn't have come up.

Was this reply helpful? Yes No
T_A_M 332 on at

Like (5)

Report
Copy link

Link copied!

I was having the same issue suddenly, and I came up with a solution that has been working for me. The error with the Left function only seems to show up when the string in question is empty, so I wrapped my function with a If statement so that the Left function is only applied when the Combo Box is not empty:

If(!IsEmpty(ComboBox.SelectedItems), UpdateContext({combined_variable: Concat(ComboBox.SelectedItems,Value & ",")}),
LEFT(string,LEN(string)-1)), "")

Was this reply helpful? Yes No
CS-24071844-0 80 on at

Like (1)

Report
Copy link

Link copied!

This worked for me - Thank you!

Was this reply helpful? Yes No