Error e.toLowerCase is not a function

[BlackMamba]

Hello guys,

I created a flow responsible for manually sending list items from Sharepoint to AzureDevops. I have a premium license and all connections seem to be correct. The flow works fine for me, but when my users are trying to use it using my connection, they get the following errors: 

Flow entity with name xxxxx does not exist in the store!

Do you have any idea what could be the potential cause of this issue?

[v-yetonggu-msft]

Hi @BlackMamba ,

‘toLowerCase’ function does not exist.

Please try toLower function:

toLower('<text>')

This link has a way to use the function correctly:

Reference guide for expression functions - Azure Logic Apps | Microsoft Learn

Best Regards,

Sunshine Gu

[BlackMamba]

But I am not using this function anywhere in my flow.

[JBlakist]

I am having the same issue! Re: Error: e.toLowerCase is not a function error w... - Power Platform Community (microsoft.com)

[LDJ_1125]

@BlackMamba  Have you solved the problem? I'm experiencing the same issue, and I have already exhausted the solutions posted in the forum (e.g., reviewing connections, replacing the Convert PDF to Word Business connection with a OneDrive connection), but none of them are fixing it.

[LDJ_1125]

@JBlakist Have you solved the problem? I'm experiencing the same issue, and I have already exhausted the solutions posted in the forum but none of them are working

[BlackMamba]

Unfortunately nothing worked for me...

[PatBic]

I am also facing this exact same issue, have tried everything I could find, nothing worked.

Same thing as the flow works from my licensed service account, but not from casual user account.

In my case the connection that is causing this ("Dokobit signature provider"), if I remove this step from the flow, then it can be run from both accounts fine.

Confusing thing is 5-6 weeks ago I had a flow that I copied and modified a bit, it also uses Dokobit connector and this flow is working for both accounts.

If I copy the same flow now, it just doesnt work and throws this "e.toLowerCase not a function". Of course have added permissions for run-only-users

I hope someone finally cracks this bug. 😑 

Have tried:

Giving permision to document library

Giving permisison for casual user (run only users) as individual added user-email

adding casual user account as owner

Reseting connections

Using different internet networks to make the flow
Fully reseting browser cookies

[JBlakist]

No I still have the same issue as well.

[cnelson0641]

I'm encountering the same issue, first happening Friday last week.  My first step of the flow is "When a flow step is executed" (Dataverse connector).  It happens to my actual users in prod, and my test user in dev and test (so in multiple environments).  But it does not happen to dev user with System Administrator security role.  I also notice that this was posted last Thursday, and we experienced issues with Power Automate shortly after on Friday morning.

[LDJ_1125]

I tried to remove the actions 'Populate a Microsoft Word template' and 'Convert Word Document to PDF', which are connected to the premium connector 'Word Online (Business)'. The flow can run fine without them.

I also attempted to redo the flow by recreating the deleted actions, but the error persists.

These deleted action steps were crucial in my flow. I am still waiting for someone to finally solve this 'e.toLowerCase' issue.

[cnelson0641]

Another thought:  the error text "e.toLowerCase is not a function" might be backend code, where e is the variable holding the actual error, and they are trying to print it to us so we can understand it.  So it's possible that the error is a red herring, and the code the actions we've listed needs to be updated to use the new format.

[JBlakist]

@LDJ_1125 and @BlackMamba - random question - can you let me know the name of your flows?  Mine is Create PDF for Bid Proposal w/attachments .  I was wondering if the / in the name was maybe causing a problem.  It's a long shot but I thought I would ask.  FWIW I have a support call with Microsoft support tomorrow AM for them to look at the issue.

[BlackMamba]

I tried it with different name of the flows - still the same problem

[PowerMar10]

I did not have the Error e.toLowerCase, but

"randomly" for some "run-only" users: 

I could resolve it by asking the user

1) to stay in the same browser and open a New tab

2) open URL: https://make.powerautomate.com/environments/[Your_ ENV] 

3) when logged in, go back to the tab with the button to start the workflow.

Now the user did not get the error anymore.

Kind regards,

Martine

[kthukral]

I am having a similar issue. The other user is also system administrator but still getting error. 

I am the creator and owner of the flow, so it is working perfectly fine for me. Should i give permission to other users for run-only? Why is the flow only running for me?

[Power_SVA]

Same issue here... for users trying to use my connection...

"e.toLowerCase is not a function"

... no toLowerCase in my code...

(Using Deepl connector in a Flow.)

[ksmiller99]

I have a premium corporate account and have been having the same issue for about 2 weeks. I suspect that there is some kind of versioning error in the various Microsoft tools, like with the script engine the flow designer IDE. I have similar problems with other MS tools that we know are versioning issues.

[briannagrant]

Experiencing the same issue. I am using a premium connection (Business Word) and the flow runs for me, however, the run-only users receive this error. Tried adding those users as co-owners and they are receiving the same error. Thoroughly tested my workflow and it was working for run-only users a couple of weeks ago. 

[Piotrek1]

Hello, 

After a few tests i noticed that the issue might come from the reference connection that has been automaticaly generated. Indeed when you add the action to your flow and your flow is in a solution, it automaticaly creates a new connection reference (if you never used this connection before in that particular flow). In my case i thought it might be linked to the name of my solution, because the connection reference is named after it. So i created a new solution and it worked

Regards