Flow save failed with code 'PropertyNotAllowed' and message 'The template action 'BuildQuery' at line '1' and column '18889' is not valid. The property 'actions' is not allowed on action type 'Select'.'.

(0) Share

Report

Posted on by bobesponja

258

Hello.

I have an Apply-to-each loop with a single Compose action in it. The Compose just writes an odata filter query to find a single item (ORDER_ID eq items('BuildQuery')?['ORDER_ID']), and the first action after the loop combines the Compose outputs using join(). It looks like this:

I want to condense that loop into a single Select action to save costs, enhance beauty, and reduce the chances of the flow tripping over itself (which is important since this flow must run every minute). Ideally, it would look like this:

I've already made this change for another flow that has the exact same structure, which references a different table. But now that I'm making the same change in this flow, with almost the exact same code, I get this error if I try to save: Flow save failed with code 'PropertyNotAllowed' and message 'The template action 'BuildQuery' at line '1' and column '18889' is not valid. The property 'actions' is not allowed on action type 'Select'.'.

I've already tried closing the flow editor and re-making the changes, sometimes with extra spaces in case it just doesn't like a specific spelling, but it refuses to budge on this despite allowing me to do it in another flow with the same structure. (the accepted Select statement is below)

What do I do from here?

Categories:

Building flows

I have the same question (0)

All responses (5)

Answers (2)

wskinnermctc 6,519 Moderator on at

Like (0)

Report

You have the exact same setup in another flow and it works? It is not working in this flow?

Your screenshot is showing the other flow that it is working?

Can you show the same screenshot for the flow that is not working? Trying to see if there is a difference in the expressions.

Was this reply helpful? Yes No
wskinnermctc 6,519 Moderator on at

Like (0)

Report

What is the body being used as a source for the Select?

Did you use copy to clipboard and paste steps into this flow? Like copy and pasted flow steps from the previous flow into this flow?

Was this reply helpful? Yes No
bobesponja 258 on at

Like (0)

Report
I've used the same basic structure across several flows. When I want to make a new one, I use "Save As" to make a copy, then edit that copy to match what's needed for the new table, which usually doesn't involve adding/removing any actions from the flow, just editing expression in the existing actions (I have a second structure that I use for other tables I'm working with, but that structure doesn't use BuildQuery).

The last picture shows the Select control for SCHEDULEDETAIL (the flow where it works), and the first two pictures are from the flow for DORDERS (the second picture being what I'm trying to save that part of the flow as). Both of these tables are SQL tables that we're regularly copying portions of into SharePoint tables. (My boss wants to avoid having apps directly interface with SQL so he can avoid dealing with premium licenses every time someone joins or leaves the company, which will not be easy to manage if our department downsizes as planned.)

The expression in SCHEDULEDETAIL's Select action is:
From: body('UpdatedEntries') Map: concat('(ORDER_ID eq ',item()?['ORDER_ID'],' and LOAD_NBR eq ',item()?['LOAD_NBR'],')')
And the Select action I want to make in DORDERS should be:
From: body('UpdatedEntries') Map: concat('ORDER_ID eq ',item()?['ORDER_ID'])
The flow for SCHEDULEDETAIL is working fine. I haven't tried to edit it since replacing the loop with a Select action, since I don't want to lose the change if this was a fluke. I've also tried making this change in other flows with the same structure, and they all reject the change with the same error given in the original post.

Was this reply helpful? Yes No
Verified answer

wskinnermctc 6,519 Moderator on at

Like (1)

Report

In the Select action for DORDERS can you test adding a final single ' quote? I'm wondering if that is throwing off the map of the Select?

Or even wrapping the whole thing in parentheses like the previous one.

I'd even go so far as literally using the one that works but just double by replacing LOAD_NBR with ORDER_ID and see what power automate does trying to evaluate the same thing twice.

Also if you are copying these flows and changing things, I would troubleshoot rebuilding the flow from scratch and not use copy and paste to clipboard. Sometime power automate has difficulty with being swapped around like that. It is like the ghosts of old steps or links conflict with the new flow.

Was this reply helpful? Yes No
Verified answer

bobesponja 258 on at

Like (1)

Report

I was really hoping the copy-and-replace-LOAD_NBR would work, but sadly it didn't take.

However, you gave me the idea to copy over the entire BuildQuery action from SCHEDULEDETAIL to DORDERS instead of just the caldculation, which ended up working! I then snipped off the rest of the formula and removed the parentheses and it decided that this was okay. Tried it on another flow and it worked there, too. Not sure what happened, but I won't complain. Thanks!

Was this reply helpful? Yes No