Laveesh Bansal (Azure Logic Apps team)

My feedback

  1. 5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Logic Apps » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Laveesh Bansal (Azure Logic Apps team) commented  · 

    Hey RJ. Thanks for your comment. You are right that this is not the right behavior. I just tried with a new logic app and I cannot reproduce it; the first execution of my logic app happened at the specified start time, rather than at deployment time.
    Could you send the details of your logic app where you observed this behavior to me at laveeshb AT microsoft DOT com? We can take a look.

    Thanks
    Laveesh Bansal

  2. 310 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Logic Apps » Workflow runtime  ·  Flag idea as inappropriate…  ·  Admin →
    Laveesh Bansal (Azure Logic Apps team) commented  · 

    You could use ARM's expression to construct the resource Id of the function app in the template. Here is an example

    "actions": {
    "myfirstfunction": {
    "inputs": {
    "function": {
    "id": "[concat('/subscriptions/', subscription().SubscriptionId, '/resourcegroups/', resourceGroup().Name, '/providers/Microsoft.Web/sites/myfunctionapp/functions/myfirstfunction')]"
    }
    },
    "runAfter": {

    },
    "type": "Function"
    }
    },

Feedback and Knowledge Base