nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

All flows in power automate giving error: Cannot read properties of undefined (reading 'value')

RobBlash

All of my flows (and I have many) are producing this error: Cannot read properties of undefined (reading 'value') See screen shot attached.

I tried logging into my connector again but that didn't solve the issue. I assume the value it's trying to read is associated with the 'Url of ArcGIS Enterprise' parameter. Where do I find this param to fix it? And what is the expected URL? All of my flows are based on surveys published to ArcGIS Online.

All of the flows are still running correctly, but I can not make any edits to them due to this error.

PA_Error_20230125.jpg

Find more posts tagged with

Accepted answers

All comments

PADEP_GIS

Thanks to @MichaelTorbett I think I was able to solve my problem that was the same as everyone else. Sorry if this is too late for everyone else.

First, I saved my existing flow as a new flow, but I don't open it at all.

I exported my new flow to a "Package" which is a zip folder. You can do this from your flow list. Select the three dot ellipsis > Export > Package (.zip)

I extracted the zip folder, navigated into the folder structure to find a file called "definition.json". I edited with my IDE and inserted the ArcGIS online URL into the appropriate location

"queries": {

"portalUrl": "https://www.arcgis.com"

},

Once that was done, I zipped the files up again and went to Power Automate to Import and Upgrade my existing flow with the package. Hope this helps someone else.

MichaelTorbett

On Friday I opened up a support ticket with Microsoft to see if they could do something on their end. The conclusion was that the fix would have to be done by ESRI. We did a lot of testing looking for work arounds to avoid having to rebuild flows. No luck. However, we took a close look at the JSON generated by the Survey 123 connector. We compared a working flow and a non working flow and one thing that stood out was the "PortalUrl" parameter was blank in the non working flow's JSON. In the working flow's JSON it was "portalUrl": "https://www.arcgis.com". See both JSON's below (portalUrl colored in orange). @BarbaraWebster1 , would it be possible to expose the PortalUrl parameter where users can input the portal url? I wonder if that might solve the issue.

Thanks,

Michael

Working Survey 123 Connector:

{

    "inputs": {

        "host": {

            "connection": {

                "name": "@parameters('$connections')['shared_survey123_1']['connectionId']"

            }

        },

        "body": {

            "webhook": {

                "name": "MS-FLOW",

                "events": [

                    "addData"

                ],

                "url": "@{listCallbackUrl()}",

                "includePortalInfo": true,

                "includeUserInfo": true,

                "includeSurveyInfo": true,

                "includeServiceRequest": true,

                "includeServiceResponse": true

            }

        },

        "path": "/api/survey/@{encodeURIComponent('0dc764dbbe8145bd821a3751a8fc3c70')}/webhook/add",

        "queries": {

            "portalUrl": "https://www.arcgis.com"

        },

        "authentication": "@parameters('$authentication')"

    }

}

Survey 123 Connector with Error Message

"inputs": {

        "host": {

            "connection": {

                "name": "@parameters('$connections')['shared_survey123_2']['connectionId']"

            }

        },

        "body": {

            "webhook": {

                "name": "MS-FLOW",

                "events": [

                    "addData"

                ],

                "url": "@{listCallbackUrl()}",

                "includePortalInfo": true,

                "includeUserInfo": true,

                "includeSurveyInfo": true,

                "includeServiceRequest": true,

                "includeServiceResponse": true

            }

        },

        "path": "/api/survey/@{encodeURIComponent('0dc764dbbe8145bd821a3751a8fc3c70')}/webhook/add",

        "queries": {

            "portalUrl": ""

        },

        "authentication": "@parameters('$authentication')"

    },

    "metadata": {

        "flowSystemMetadata": {

            "swaggerOperationId": "AddData"

        },

        "operationMetadataId": "0b3a1791-5fe2-405d-b00f-96eed3a17dca"

    }

}

KimberlyMyers1

We ran into this issue too. Hoping there is a resolution other than rebuilding our flows.

AbiDhakal

I'm also dealing with this issue and would really appreciate a resolution.

Thank you,
Abi

MichaelTorbett

I have also been dealing with this issue and just escalated the bug through ESRI support. I have several complicated flows that need changes. Some will be a nightmare to rebuild. Is there any hope that this bug will be corrected without having to delete the Survey 123 connector?

Thank you,

Michael

KBeardsley

I have encountered this same problem, and really need to edit the email content as we have a new employee and she needs to receive the automated email. I put a lot of time and effort into creating the returned email message, with lots of dynamic content, and I'm not interested in recreating all this. Please let me know when there will be a solution that does not require users to re-enter all of their dynamic content. Thanks.

EgleAdmin

We are experiencing this issue for about half of our flows (about 10). The weird thing is the same Survey123 works in one Flow and we get this same error "Cannot read properties of undefined (reading 'value')" in another Flow. Unfortunately the Flow that we get the error in is a very complicated one and re-building is a huge ask. @BarbaraWebster1 is there an update when this will be resolved?

AlexUreAl

Thanks. In my case I had to rebuild the workflows again, after that they work fine, luckily we are in the initial stage of testing.

Regards.

BarbaraWebster1

Hi @AlexUreAl, please see the response above.

RobBlash

Barbara,

Rebuilding the flows and having every user re-download from the field app are individual deal breakers, and combined are a major interruption.

What's Esri's ETA on a non-disruptive fix? I have way too many surveys, flows, and users to go down the suggested path.

BarbaraWebster1

@RobBlash Adding a new trigger would mean you would need to select your survey again in the new trigger module and also re-enter any dynamic content based on the trigger survey downstream in the flow. You wouldn't need to republish the survey, but would need to update any surveys that were already downloaded in the field app. In our testing, re-adding the connector has resolved this issue. We are still looking into this issue to identify the specific cause.

Thanks,
-Barbara

RobBlash

Hi Barbara,

Will this disconnect the flow from the survey? I want to avoid having to re-publish the survey.

Also, it seems like this may break all of the downstream functions in the flow (since the survey trigger is typically the first step in the flow). Has anyone at Esri confirmed this will work?

Thanks,

Rob

AlexUreAl

Tengo el mismo problema. ¿Qué solución sugieres? Ya saqué el gatillo y lo puse de nuevo y el flujo no funciona.

BarbaraWebster1

Hi @RobBlash,

There was an update to the Survey123 connector this week we are looking into what may be causing this conflict. Like you mentioned, this error appears while editing a flow and does not prevent existing flows from running.

Can you try removing the 'When a survey response is submitted' trigger from the flow and re-adding it to resolve the error?

Thank you,
-Barbara

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.