Unanswered

SplitOn error preventing me from being able to run what is meant to be a child flow

(0) Share

Report

Posted on by Jamep2

Hello, hoping someone can help me out. I created a button trigger flow directly from within Power BI using a Power Automate visualization to export a table visual to an excel file. That works like a charm. Ultimately, what I am trying to do is call that flow from within another flow. The idea is the parent flow is set to run daily to test todays date against business day 15. When that condition is met, the flow will call the child flow to export the Power BI table to an excel file and save it with the specified name. Both flows work independently of each other except for the part of being able to create the parent child relationship.

I added both flows to a solution so that the run child flow option would be available however when I go to add the "Respond to Power App or Flow" component to the child flow and try to save, I get this error:

Flow save failed with code 'WorkflowUnsupportedSplitOnTriggerForResponseAction' and message 'The workflow with 'Response' action type should not have triggers with 'splitOn' property defined: 'manual'.'.

If I try to turn off the SplitOn setting, I still get the same error. Plus I think it needs to be on to export each line of data from the PBI table into excel. I am wondering if there is a way to edit the SplitOn trigger code that was generated by the PBI flow to allow this to work. Any help would be greatly appreciated.

Categories:

Building flows

I have the same question (0)

All responses (6)

Answers (0)

Sort by

Pstork1 69,397 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Not sure if this is related to your error, but the Respond to Power Apps or Flow needs to be the final action in a flow and there can only be one because it is used to exit the flow run and return results to another flow. I'm not sure what you are doing with it in this context.

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

Was this reply helpful? Yes No
Jamep2 27 on at

Like (0)

Report
Copy link

Link copied!

Thank you for the reply @Pstork1. I originally had the respond to flow in the last position but then decided to move it up after watching this video so the flow would not be hung up waiting on the export to happen as it take about 3 minutes for all of the data to be pulled into the excel file. https://www.youtube.com/watch?v=DLhwnZ5JRvE

I went back and moved it down just in case but I still get the same error. Its directly referencing the SplitOn but turning it off is still causing the same error. I am thinking its the way the trigger was coded through PBI but I honestly have no clue. Thanks for taking the time to respond, I appreciate it.

Was this reply helpful? Yes No
Pstork1 69,397 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Can you show a screenshot of the settings of the Trigger that is triggering based on Power Bi? That's where the SplitOn setting is. I'm assuming since its bringing in a data set from Power BI that it should be Off by default. If it is then you need to handle the details in a loop. Right now the code you have in the screenshot shows it passing an Object with an embedded array. So based on that schema I would expect the SplitOn to look something like

triggerBody()['Properties']?['Rows']

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

Was this reply helpful? Yes No
Jamep2 27 on at

Like (0)

Report
Copy link

Link copied!

Here is are screen shots and also the full code of the trigger below. @Pstork1

This is peek at the full code for the Power BI

{

    "kind": "ApiConnection",

    "splitOn": "@triggerBody()['rows']",

    "inputs": {

        "schema": {

            "type": "object",

            "properties": {

                "rows": {

                    "type": "array",

                    "items": {

                        "type": "object",

                        "properties": {

                            "entity": {

                                "type": "object",

                                "properties": {

                                    "Power BI values": {

                                        "title": "Power BI data",

                                        "type": "array",

                                        "items": {}

                                    }

                                },

                                "required": [

                                    "Power BI values"

                                ]

                            }

                        },

                        "required": [

                            "entity"

                        ]

                    }

                }

            },

            "required": [

                "rows"

            ]

        },

        "host": {

            "connection": {

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

            }

        },

        "operationId": "PowerBiButtonClicked",

        "parameters": {

            "inputsPowerBiData": "{}",

            "pbi_source": "powerAutomate"

        }

    },

    "metadata": {

        "operationMetadataId": "8519b0d5-c47b-4650-a25b-8860c0ca77cc"

    }

}

Was this reply helpful? Yes No
Pstork1 69,397 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

I don't do enough Power BI to be sure, but I suspect the issue is the way you are formatting the values in Power BI that are sent with the trigger when you press the button. When I add that trigger I get the following code.

As you can see the input schema is just an array of rows, while yours is an object with an array of rows. But both use the same SplitOn. For mine it would be right, but for yours it throws an error. I think you need to take another look at the data you are sending from Power BI when the button is pushed. I think it should be one level higher so you are sending an array of data rows instead of an object containing an array.

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

Was this reply helpful? Yes No
Jamep2 27 on at

Like (0)

Report
Copy link

Link copied!

Having a place to start is always a bonus @Pstork1. I will give that a try first thing Monday. I'll be sure to let you know if I get it working. Thanks so much!

Was this reply helpful? Yes No