Microsoft Flow: Submission will not trigger if a date fields are blank.

  • Profile Image
    dmkim
    Asked on February 02, 2018 at 05:25 PM

    Dear Tech team,

     

    After a crazy amount of trial and error, I would just like to report a bug that may or may not be helpful to you.  

    I use the JotForm trigger integration in Microsoft Flow. I noticed that some of my form submissions were not registering to begin with. Not that they were failing, but just not even being recognized as a submission in the first place.  It will not even show up in the run history as a success or failure, its just nothing at all.

    I tried to control for the reason it wasn't working and found out that if any date fields are left blank on the form, the submission wont even be registered in Microsoft Flow. Other, non-date, fields left blank don't seem to have any effect either way. If all date fields are filled in with a date entry, the Flow triggers as normal and will register as a success or failure. 

    If you can test this yourself and let me know if this is true or if I am wrong, I would greatly appreciate it. 

    Kind regards,

    Davey

  • Profile Image
    Jed_C
    Answered on February 02, 2018 at 06:37 PM

    I'm asking a help from my colleague to create a microsoft flow account for us to test this issue. Will report back with our findings. Thank you for your patience.

  • Profile Image
    Jed_C
    Answered on February 02, 2018 at 09:38 PM

    I did test it with one drive and dropbox integration, that doesn't seem to work. However, integrating it with excel by following this video works https://player.vimeo.com/video/224162123?title=0&byline=0&portrait=0.

    1517625282microsoft flow.png

    May I know what action did you select? Looking forward for your response.

  • Profile Image
    ryan
    Answered on February 04, 2018 at 03:00 AM

    Thank you for reporting the issue.

    I was able to reproduce the issue and the bug was indeed caused by a blank date field.

    We have already patched the code and the issue should now be fixed.

    Thanks!