Unanswered

Gettign BadRequest passed-in field "DynamicProperties" could not be found - not modifications have been made and was working fine

(2) Share

Report

Posted on by Grace-msk

Had a flow set up to create a new document set in a library once an item was created in a tracker, was all working fine for a week. Today it's been failing with the the error message:

The passed-in field "DynamicProperties" could not be found

Nothing has been modified in the flow, the tracker, or the library.

Any ideas?

Flow:

Inputs (all correct):

Categories:

General topics

I have the same question (0)

All responses (11)

Answers (0)

Jasonmumbulla 5 on at

Like (1)

Report

I am also getting this error on a flow that was previously working. I've created a minimal flow to test and this is also failing with the same error.

Was this reply helpful? Yes No
Dennis-DTI 4 on at

Like (0)

Report

Having the same issue. No changes to the flow, just all of a sudden failing on the Create New Document Set step. Pretty unreliable, Microsoft.

Was this reply helpful? Yes No
Grace-msk 6 on at

Like (0)

Report

Same, stripped it right back and it's still failing... very frustrating

Was this reply helpful? Yes No
jiwhite 498 on at

Like (0)

Report

I've reported a similar issue here, BUGS - No longer able to get ID or value of ShareP... - Power Platform Community (microsoft.com), where an existing flow is suddenly not working because the run time of the flow doesn't match design time.

Was this reply helpful? Yes No
pedropmb 4 on at

Like (0)

Report
Having exactly the same issue. Also trying to leverage inputs to create a document set fails with the same error:
The passed-in field "DynamicProperties" could not be found clientRequestId: 3ed9ca64-5a47-42a0-a521-ccef00013588 serviceRequestId: 3ed9ca64-5a47-42a0-a521-ccef00013588
Previous runs were successful but today fails with this error. No changes made since previous successful run...

Was this reply helpful? Yes No
APowerAppNewb 31 on at

Like (0)

Report

Were you able to determine what caused the error?

Was this reply helpful? Yes No
pedropmb 4 on at

Like (0)

Report

No. We've tried cutting down the "Create document set" to the minimum set of inputs required and it still fails on that action.
Currently opened an issue with Microsoft.
@APowerAppNewb are you expiriencing the same issue?

Was this reply helpful? Yes No
APowerAppNewb 31 on at

Like (1)

Report

@pedropmb Yeah. I wanted to see if I could re-run the flow, maybe that resolved the issue, but I am not seeing any luck. Same error: Dynamic Properties are not being found. I'm wondering if Microsoft changed that action in some way that has caused this break?

Was this reply helpful? Yes No
jiwhite 498 on at

Like (0)

Report

I can do what I need to do if I create a new flow with the same trigger, but I can't get the broken flow to work. Even if I delete the trigger and add it again, it still has the same problem. Something that Microsoft did has broken some existing flows.

These are the columns that the flow finds at run time.
These are the columns the list has.

It's like the flow can only get a very old version of the list, not the current one.

Was this reply helpful? Yes No
APowerAppNewb 31 on at

Like (0)

Report

Yeah. What I found solves the problem, at least for me, is to eliminate any of the fields within the Create New Document Set action. Only keep the core fields that are required to create the Document Set. Then use a HTTP trigger to add the necessary metadata for the Document Set. It's an extra step, but it does resolve the problem.

Was this reply helpful? Yes No