Unanswered

Error e.toLowerCase is not a function

(1) Share

Report

Posted on by 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?

Categories:

Using flows

I have the same question (0)

All responses (25)

Answers (1)

v-yetonggu-msft on at

Like (0)

Report
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

Was this reply helpful? Yes No
BlackMamba 35 on at

Like (1)

Report

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

Was this reply helpful? Yes No
JBlakist 18 on at

Like (2)

Report

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

Was this reply helpful? Yes No
LDJ_1125 27 on at

Like (0)

Report

@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.

Was this reply helpful? Yes No
LDJ_1125 27 on at

Like (0)

Report

@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

Was this reply helpful? Yes No
BlackMamba 35 on at

Like (0)

Report

Unfortunately nothing worked for me...

Was this reply helpful? Yes No
PatBic 2 on at

Like (0)

Report

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

Was this reply helpful? Yes No
JBlakist 18 on at

Like (0)

Report

No I still have the same issue as well.

Was this reply helpful? Yes No
cnelson0641 10 on at

Like (0)

Report

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.

Was this reply helpful? Yes No
LDJ_1125 27 on at

Like (3)

Report

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.

Was this reply helpful? Yes No