cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
ChrisRoxor
Level: Powered On

Using "Trim" expression with Dynamic Content

Hi

 

I'm having some issues using Flow and Microsoft Forms.

I have a form to collect feedback on an Application ID. This feedback is then passed to a Sharepoint list.

That triggers another flow that has a filter array between the Feedback list and the Master list, where i want to submit the feedback to as well.

The issue is, using Forms, people sometimes include a blank space at the end of the applicationID, which in turns, returns blank from the Filter Array.

I tried to add an expression upon the write from Forms to Sharepoint but it's giving me an error:

 

Right now it just fills it straight in:

@{body('Get_response_details')['rb4e2f716f3db4692aa8022940b704a99']}

 

This is my expression, within one of the fields in a "Create Item" Sharepoint action:

trim(@{body('Get_response_details')['rb4e2f716f3db4692aa8022940b704a99']})
but when i click "OK" it gives me an error saying "The expression is invalid".
 
What am I doing wrong here? Can i not trim whitespace from a dynamic content field?
 
Thanks in advance
1 ACCEPTED SOLUTION

Accepted Solutions
Super User
Super User

Re: Using "Trim" expression with Dynamic Content

hi @ChrisRoxor , thank you for posting this.

Try expression:

trim(body('Get_response_details')['rb4e2f716f3db4692aa8022940b704a99'])

I would expect this is correct format as @{} will not make valid WDL.

 

If you find my posts helpful, please mark with thumbs up

If this solves your issue, please click "Accept as Solution"

Any questions, just ask.

Thanks, Alan


Did I answer your question? Mark my post as a solution!

Proud to be a Flownaut!


View solution in original post

1 REPLY 1
Super User
Super User

Re: Using "Trim" expression with Dynamic Content

hi @ChrisRoxor , thank you for posting this.

Try expression:

trim(body('Get_response_details')['rb4e2f716f3db4692aa8022940b704a99'])

I would expect this is correct format as @{} will not make valid WDL.

 

If you find my posts helpful, please mark with thumbs up

If this solves your issue, please click "Accept as Solution"

Any questions, just ask.

Thanks, Alan


Did I answer your question? Mark my post as a solution!

Proud to be a Flownaut!


View solution in original post

Helpful resources

Announcements
firstImage

Better Together Contest Finalists Announced!

Congrats to the finalists of our ‘Better Together’-themed T-shirt design contest! Click for the top entries.

firstImage

Incoming: New and improved badges!

Look out for new contribution recognition badges coming SOON!

firstImage

New & Improved Power Automate Community Cookbook

We've updated and improved the layout and uploading format of the Power Automate Cookbook!

thirdimage

Power Automate Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

sixthImage

Community Summit North America

The top training and networking event across the globe for Microsoft Business Applications

Top Solution Authors
Top Kudoed Authors
Users online (3,806)