Power Automate

Help with Report Parameter Error in Power Automate

(1) Share

Report

Posted on by RP-11111036-0

Hi all,

I’m encountering an issue while running a report in Power Automate Desktop, and I need some guidance to resolve it.

I’ve set up a flow that exports data to a Power BI report, but I’m getting the following error message:

Here are the details of the error:

Report Name: Test_report
Status Code: 400
Error Code: Report_Processing_Error
Error Message: RootActivityId: The value provided for the report parameter GLDateFiscalYear is not valid for its type.
Correlation Id: 5e0d76b1-262e-4def-807b-ff9a0e709395
Report ID: 68d57b50-5bda-4b3d-8fcc-82fdb05b7c13

The parameter GLDateFiscalYear seems to be the source of the issue. I’ve checked that the value passed should be an integer (for example, 2024), but I’m not sure what’s causing the mismatch between the parameter and the expected data type.

What I’ve Tried:

Checked the parameter data type – I've confirmed the parameter is expecting an integer, and I am passing a number (2024).
Re-tested with a static value – I tried using a static value for the GLDateFiscalYear parameter but still received the same error.

Any suggestions on how I can ensure that the data type for this parameter matches the report's expected input, or steps I can take to troubleshoot this further?

Thank you in advance for your help!

Categories:

Power Automate Desktop

I have the same question (0)

All responses (5)

Answers (0)

makwanasamir 13 on at

Like (1)

Report

Please help answer questions below,

1. Could you please share the flow with more details? Like the details on 2 to 3 steps in the flow from the point before and after it gave you an error.

2. Was this a old work flow working fine and failed OR it has never worked?

3. Is there any recent changes to the flow or environment?

As you have already tried static value, there are chances that the step which is trying to consume that GLDateFiscalYear variable value having some issue.

Note related to Power Automate, but i recently faced similar datatype issue while passing variable from Copilot Studio to Power Automate cloud flow. Power Automate cloud flow was looking for Date Variable which i was passing from Copilot Studio, it kept failing with data type mismatch error. At last, i found out that Power Automate accept date value in text data type instead of date data type. I have created YouTube video explaining the same. https://www.youtube.com/watch?v=bJscQ1blfDA&t=1s

Was this reply helpful? Yes No
RP-11111036-0 8 on at

Like (0)

Report
Hi @makwanasamir ,

I'm relatively new to Power Automate, but I did get the flow working in the cloud platform. Initially, I tested it with %'2024'% as a static value for the GLDateFiscalYear parameter, and the test was successful. However, I'm still working on a dynamic solution for the year that could run automatically.

Here’s a bit more detail on the flow:

It starts by exporting a file from paginated reports.

Then, it creates a file and runs a PowerShell script to save it on a different drive.

In the cloud environment, everything ran smoothly. However, I moved it to Power Automate Desktop because I need to save the files to a specific location on a different drive, which I haven’t been able to achieve with the cloud solution.

This desktop environment is new, and I'm facing the same data type mismatch error across all flows. If I can get this resolved here, it should help fix the issue in my other flows as well. Thanks for any guidance you can offer!

Was this reply helpful? Yes No
Suggested answer

makwanasamir 13 on at

Like (0)

Report

There are two approach i would suggest, please ignore if you have already tried them,

1. More probing by following step below,

GLDateFiscalYear might be a text format. To identify that try checking length of the GLDateFiscalYear using %Variable.length% to see if it gives you the output as 4 (becuase there are 4 character in the year), then you try converting it to the date or number format by using "Convert Text to Number" or "Convert Text to DateTime" format and see if that works for you.

2. Change in solution approach,

As you mentioned that cloud flow working fine and only reason you are using desktop power automate as you want to store file in different folder. In that case, I would suggest to manage all the data extraction in the cloud flow and then store it on SharePoint or OneDrive for Business, which you can sync it to the computer. Once synced, you can use Power Automate Desktop to copy/move file from one folder to another.

if issue persist, having some screenshots of the work flow will be helpful to help you troubleshoot this issue further.

Was this reply helpful? Yes No
RP-11111036-0 8 on at

Like (0)

Report

@makwanasamir

Thanks for your suggestions! I was able to pass a single value for GLDateFiscalYear as text successfully using your help , but I haven’t been able to pass multiple values yet. Would you know if there’s a way to handle this? For example, if I need to pass 2022, 2023, and 2024, should I use an array, or is there another method you’d recommend?

Thanks again for your help!

Was this reply helpful? Yes No
makwanasamir 13 on at

Like (0)

Report

I am glad i was able to help with your first query.

For passing multiple values, I am not sure if you are planning to pass all in one or separate repetative actions, as they are text combined as sing text or list. Please review Join Text or Split Text actions, https://learn.microsoft.com/en-us/training/modules/pad-text-manipulation/2-text-actions#:~:text=value%2C%20use%20the-,Join%20text,-action%20and%20then. Moreover, if you want to process each of those value on repetative task then you might want to use different type of loops available on https://learn.microsoft.com/en-us/training/modules/pad-loops/

Was this reply helpful? Yes No