The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
I have a Power BI report that utilizes slicers and uses the Power Automate button to invoke a flow which writes data to a SharePoint list which includes the 'user email' field that is inherent to the button. The flow writes the field but it appears to be garbage. This causes my subsequent flows to fail as the value is not viable.
I have the same logic working in a similar flow, but it wites the data with no issues to the SharePoint List. I have verified that the field in both SharePoint lists are set to "Single Line of Text". What am I missing here?
Solved! Go to Solution.
My Power BI fields for the Power Automate Visual is listed below:
That is an interesting point. I had noticed in th past that mine would list as yours and I woiuld have to hover over the field to see what it was actually doing, but I have ran some updates from our company on my laptop that must have changed the functionality a bit. Thank you again for the insight but I was able to work around the issue. It seemed that somewhere in the flow the value for the Power BI parameter was being altered prior to my use. The early assignment to a variable in the header has been a solid fix and does add clarity for future modifications by other analysts.
Kudos team and thank you.
Thank you for your response. I was attempting to slice data within Power BI and then by use of the Power Automate button, pass the data records out to a sharepoint list and then a seperate set of data including the "User email" Power BI supplied string parameter to a seperate SharePoint List that was a trigger for an external flow to generate a detailed report and then email it back to the requesting user. The problem was when I pitched the "User Email" parm from Power BI to the SharePoint List it was corrupted the contents.
I have a working resolution to the issue by moving the "User email" field/parm to a initialized string variable within the flow in the header and then pitching the variable to the SharePoint List instead. I have another flow where I did not need to do this, but for some reason, the newer flow is corrupting the value of the variable. The modification was one new entry and a single modification of the variable name to the SharePoint list prior to saving. The new entry for the string population is listed below, however, if you might know if this is the best approach, I'd be grateful. I'm guessing whenever I alter my first program it will most likely abend in the same way and require the same method of resolution if this is related to some patch or update to the code.
That doesn't look like it should. On my side it looks like
can you show the values well for your Power Automate visual?
This is how mine looks like
My Power BI fields for the Power Automate Visual is listed below:
That is an interesting point. I had noticed in th past that mine would list as yours and I woiuld have to hover over the field to see what it was actually doing, but I have ran some updates from our company on my laptop that must have changed the functionality a bit. Thank you again for the insight but I was able to work around the issue. It seemed that somewhere in the flow the value for the Power BI parameter was being altered prior to my use. The early assignment to a variable in the header has been a solid fix and does add clarity for future modifications by other analysts.
Kudos team and thank you.
Please provide a more detailed explanation of what you are aiming to achieve. What have you tried and where are you stuck? What is the field type of the email in Power BI? Did you assign a category to it? Is it part of the values list for the Power Automate visual? Can you post the Flow part where it loops through the transmitted records ("Apply to each") ?