PowerApps Exchange

Please login or click SIGN UP FOR FREE to create your PowerAppsUG account to join this user group.
Expand all | Collapse all

Strange behaviour in Flow from PowerApps

  • 1.  Strange behaviour in Flow from PowerApps

    Silver Contributor
    Posted Jan 11, 2019 01:18 AM

    Something strange has happened in my PowerApps/Flow environment which will cause me considerable issues if not resolved.

    I was experimenting with the Flow control of returning values from SharePoint to PowerApps and ever since I did this, no new Flows created, modified or re-saved will request more than a single value from PowerApps, even though multiple are set to "Request in PowerApps" in Flow.

    I have done a lot of testing and the following occurs: -

    • All existing Flows written prior to this time work fine and can have other trigger objects in PowerApps done (the syntax shows all requested items)
    • If I make a copy of the Flow (in Flow), it also works fine.
    • If I in any way modify the Flow (or even re-save it as below), I get the single parameter requested (generally the last item requested).
    • If I make a new Flow identical to one that works, the same.

     I have tried logging out and in again (and re-booting the PC), but to no avail.

     I would be grateful if someone can please shed some light on this.



    ------------------------------
    Warren Belz
    Database Developer
    Ventia Utility Services Pty Ltd
    Rockhampton Qld Australia
    +61 409 315 509
    ------------------------------
    Power Summit (PApps) - Post


  • 2.  RE: Strange behaviour in Flow from PowerApps

    Bronze Contributor
    Posted Jan 14, 2019 09:26 AM
    Warren,

    I generally find best practice when requesting parameters from PowerApps (i.e. "Request in PowerApps") that I need to remove the Flow from the app and re-add it every time I add or remove a parameter.

    To remove a flow, click View (tab), then Data sources.   Your Flow(s) should be listed along with any other data sources.  Click the ellipses and select Remove.
    Next find the control where you want to use the Flow and re-add it.

    Tip: All code associated with that control's property  (i.e. OnSelect) will be lost when you re-add the Flow, so I usually copy it and save it in a scratch text file just in case.

    Not sure if this will solve your problem.  The other suggestion I have is to post your issue to the PowerApps Community forum.

    Good luck,
    Jamie

    ------------------------------
    Jamie Willis-Rose
    Supervisor Technical Operations
    Discovery
    Sterling VA
    ------------------------------

    Power Summit (PApps) - Post


  • 3.  RE: Strange behaviour in Flow from PowerApps

    Silver Contributor
    Posted Jan 14, 2019 05:32 PM
    Thanks Jamie,

    You may not have seen Harold's response about the PowerApps regression bug, however your post is good advice and something I always do.

    I find any changes parameters are not picked up until this is done. As you suggest, the code after "<flowname>Run("  needs to be copied to Notepad or similar and then put back adding/changing/removing parameter alterations.

    I think this post may be useful in the future when strange unexplained things happen. In my testing, I had also eliminated the PC and created new Flows and blank PowerApps with only a button to run the flow and it was still happening. I then had another user log in and it all worked fine.

    All is well now Microsoft has addressed it - thanks for your response.

    ------------------------------
    Warren Belz
    Database Developer
    Ventia Utility Services Pty Ltd
    Rockhampton Qld Australia
    +61 409 315 509
    ------------------------------

    Power Summit (PApps) - Post