cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Super User
Super User

Select action corrupt on open

Corrupt.PNG 

My filter array 3 is an array of strings. My flow works but when I open my flow I get the enter a valid json errror and I can't save my flow. 

 

this feel like a bug in the opneing of a flow with a select that using the body function.

Community Support Team
Community Support Team

Re: Select action corrupt on open

Hi @Pieter_Veenstra,

 

I want to make a test on my side,

Could you please share the full details about the output of your Filter array 3 action?

Could you please share the expression you use in the Select 2 action?

Could you please share more details of the error message of your issue?

 

Please share more details so we would try to provide a proper workaround for you.

 

Best regards,

Alice

Super User
Super User

Re: Select action corrupt on open

Hi Alice,

 

 

It is a simple array of strings:

 

[
  "a href=\"/this-is-a-url/opportunities/1234\"",
  "This is a job",
  "This is a company name",
  "London",
  "Type 1",
  "Published: Friday 15 June 2018",
  "Deadline for asking questions: Friday 22 June 2018",
  "Closing: Friday 29 June 2018",
  "This is a long description of the job",
  "/p",
  "/div",
  "div class=\"search-result\""
]

Community Support Team
Community Support Team

Re: Select action corrupt on open

Hi @Pieter_Veenstra,

 

 

I have made a test on my side and don't have the issue that you mentioned.

 

The screenshot of the configuration of your flow as below:

Capture.PNG

 

The flow would run successfully as below:

Capture.PNG

 

Please take a try to delete the "Select" action and re-add it or recreate the flow to see if your problem still exists.

 

Best regards,

Alice

 

 

 

 

Best regards,

Alice

Highlighted
Super User
Super User

Re: Select action corrupt on open

Hi Alice, You are using a variable to hold the string array. I've got a select that gives me the array. Therefore I'm using the body(...) rather than variables(...) function. I think this is making the difference. Can you try it with two selects or one compose and select following each other?

>