error in previously working flow

[JeroenM13]

Hi all

I had a flow that was working fine until last week. Since then I  get the BadRequest error on a create documentset step.

I see no issues in the inputs but the outputs gives this: 

{

  "status": 400,

  "message": "The passed-in field \"DynamicProperties\" could not be found\r\nclientRequestId: be4f4710-a462-4697-b283-95a24a131ef4\r\nserviceRequestId: be4f4710-a462-4697-b283-95a24a131ef4"

}

any experience with this?

thank you

[Roberta]

Hello, I'm glad that you posted, I'm having the same issue!

Here some details and what I noticed on my side.

Since a week this flow continuosly fails because "The passed-in field "DynamicProperties" could not be found".

My flow uses the "Create a new document set" action. I noticed that the action can't manage to retrieve my column choices/lookup values.

I noticed that when I select the Content Type from the dropdown, my Lookup-column values can't be retrieved, whereas my Choice-column values can.

The error states "Could not retrieve values. The dynamic invocation request failed with error: { "status": 404, "message": "Could not find field." }."

 

However, when I select the Content Type by directly typing its ID, my Choice-column vaues can't be retrieved, whereas my Lookup-column values can.

 

So in any case the action can't work because some of the column's values aren't retrieved.

Have any of you experiencing the same issue?

Addditional note: if I look the inputs values after running my flow, I see that the Content Type Id when I select my document set from the dropdown is 0x0120D52000CA2045EF4278A047B07BE2F0C7EFA8060054A207F70E69634E9165A39881E5F7D4, whereas when I type it in it remains shorter (0x0120D52000CA2045EF4278A047B07BE2F0C7EFA806).

[JeroenM13]

Hi Roberta

based on your input I tried going by entering the content type id. It did load the correct columns, but could not be saved for some reason:

[Quesadillas-18]

Hi @JeroenM13 , have you found a solution?

I am getting the same error. "The passed-in field "DynamicProperties" could not be found" with the DocSet creation connector.

I had this flow working in sandbox last week. Replicated to prod, it was working fine until today. Went back to sandbox to check if there was any difference, I ran a test in sandbox without any changes, now sandbox doesn't work anymore.

There is a new way to add content types in SharePoint, I guess it has to do with that last update?

Btw, I am not using lookup columns, just single line of text, number, and choice. I've tried specifying content type Id and making column changes without luck.

[goldenbrown]

Yeah, I am having the exact same issue with the status "400". None of the meta data can be passed through the "create new document set" action. If I only fill out the site, library, path, and content type ID, the action runs and the document set is created (without metadata).

[JeroenM13]

Hi Goldenbrown

thanks for the suggestion I created a new document set action without metadata and used "update file properties" action right after to enter the metadata. this solved the issue for me.

[Roberta]

Hello @goldenbrown and @JeroenM13 ,

Thank you for the suggestion. In my case removing all the metadata still results in the flow failing.

Do you by any chance have some column which value is "requested" for your document set?

[JeroenM13]

Hi Roberta

I have no columns which are required, no.

[Quesadillas-18]

Thanks @goldenbrown , this is working for me. Using the "Update element" right after to add the metadata.

@Roberta Try setting to blank even default metadata like "yes/no" or default values in choice columns.

[Roberta]

@Quesadillas-18 I did ensure that each field has a blank value. Still not working for me.

However, my document set has 3 required columns, two of wich are Lookup columns, which values cannot be retrieved and therefore display the error "Could not retrieve values. The dynamic invocation request failed with error: { "status": 404, "message": "Could not find field." }.".

[JeroenM13]

Hi Roberta

would you not be able to define the lookup values and requirement of the columns via your flow, instead of making the requirements within the column itself? (like setting up conditions). This might resolve the issue for you

[Roberta]

I thought that Microsoft has maybe made an update by trying to fix this previous existing issue with this type of action: https://powerusers.microsoft.com/t5/General-Power-Automate/Report-Bug-Error-Create-new-document-set-...

Maybe it'll disappear on its own after a further update?
@JeroenM13 Could you please mark the topic as "not solved"? I think the solution of creating the document set without inputting metadata is just a temporary fix, but the action is still broken.

[JeroenM13]

Hi Roberta

done as per your suggestion.

[ElHombreOscuro]

I have the same issue in a flow that creates a document set. We immediately contacted Microsoft support and had a Teams meeting where I showed the person who to repro the error. So far haven't heard anything. 

[Roberta]

Hello everybody, I didn't change anything on my side, but the flow seems to work again for me.

Did any of you tried to restore the original non-working flow?

[ElHombreOscuro · Accepted solution]

I had a Teams meeting with someone from the SharePoint team. The problem was resolved that same day and all Flow started working without us changing anything. Apparently there was something wrong with the Create Document Set action.

[Astrapsato]

FYI to anyone still trying to solve this issue.

What worked for me was to re-add the "Create Document Set" step in PowerAutomate after disabling the column/field from requiring information.

It seems like when you add the "Create Document Set" step, it saves all the parameters and doesn't update when you remove the column, or make it not required.

[Roberta]

Hi @Astrapsato, in my case the flow just started working again spontaneously. My issue has been solved by just waiting, and everything in the last month has been working just fine.

I don't know if perhaps Microsoft fixed the issue.