I have a flow that works until I add a condition where if the answer Yes to a "Return Request" it requires additional fields like Return POC, Return Location, Return Date... This seems to work as intended. However, I need to build into the flow for "change request" which will call up the data from a SharePoint list (by the submitter entering the original request ID). So....I added a condition BEFORE the "Return Request = YES" condition which says If all the "Return data fields are "empty" then Yes = Create a SharePoint List without capturing the Return Fields Data. If NO = Create a SharePoint List CAPTURING the Return Data.
This Condition works if the Return = Yes and the return data fields are populated (as intended). However, when I test with Return = No and these data fields are empty.
With this error:
The 'inputs.parameters' of workflow operation 'Return_Required_-_YES' of type 'OpenApiConnection' is not valid. Error details: Input parameter 'item/ReturnDate' is required to be of type 'String/date'. The runtime value '""' to be converted doesn't have the expected format 'String/date'.
The problem I am seeing is that the condition ALWAYS gives the False expression even though I know I answered the test flow correctly with Return = NO
The Return Date seems to be the data field that is causing issues which I am sure has to do something with the date format (but I am guessing). I also added a compose ABOVE "Get Response Details" to if(empty(triggerOutputs()?['body/Return Date']), 'NA', formatDateTime(triggerOutputs()?['body/Return Date'], 'yyyy-MM-ddTHH:mm:ssZ'))
However, I am not sure that is necessary as the whole issue currently is that condition is giving the FALSE expression regardless.
What am I missing?
My next issue is once I get this condition working properly I have to add another condition that will retrieve data from the form when someone does a "change request" option to it will pull the data fields back in for them to update where needed and resubmit - and for that resubmit to update the data that changed on the task that is created (so we don't get multiple tasks for the same submission)...
