Check a SharePoint list field to see if contains N/A or is empty and replace with Not Required

[PaulK]

Hi,

I was wondering if there is a better solution to the issue I am facing.

Background:

MS Form for training requests with approx. 12+ job types and up to 10 courses (Displayed via Likert) that they may need so you can imagine the output data from the form (multiple of each course) so that filters into the correct fields within the list

I would like to take the data from those course fields within the sharepoint list and check if they contain:

N/A

Nothing at all (Empty)

I thought about adding all of the items to an array then querying each to check and update each array item when the required conditions are met. I seem to have been going around in circles for what seems hours to get that working and couldn't

Below is what I have come up with and it does seem to do the job but is there a more efficent way to be doing it?

It repeats for each course in the Sharepoint list.

Thanks for taking the time to read this.

Paul

[NickMerrick]

Set the Inpatients variable to be an If Expression, if blank, then set it to a string "Not Required", else Inpatients value. then there is no need for a condition or array as the variable will just have the correct value from the create item action.

[PaulK]

Thanks for your reply, I can't really use the value given in create item as there are multiple form feed results that could be in a field in the list but only ever one will be filled in for each, see an example below:

This is for only 2 job groups for both new and current users and the courses they may need each form result for the request could contain:

Full

Refresher

N/A

Blank

This is why ideally I would like to do this check on the output of get items as it will have already been filter from the form at this point. I might be able to get them to change N/A to Not Required on the form so that would fix that part.

[NickMerrick]

if there are different departments and different question types used in the same form, why not have a choice field near the beginning, then change what question is asked next based on that initial selection? Then in the beginning of the flow you could have a condition which checks what department the form response is for, letting you create records using only those input fields. For example I have a task for for two departments, my first form question is what type of task this is, then based on their selection it takes them to fill out that departments specific questions. No need to have multiple fields for each one.

Basically have a choice at the start of the form that goes to the dept specific questions, then have all those answers go to the generic questions. Then in the flow have a different process for each dept.