Thank you very much, Kent! while creating workspace, I don't get same options as yours. After workspace created, I have 3 .vscode folders, one under base folder with all launch,settings and tasks json files, one under Function folder with 4 json files including one extra as externsions.json files, one under LogicApp, but only extensions.json file. When I do dotnet build under Function folder, I don't get dll under bin folder of LogicApp. Also I cannot open workflow in design mode, some kind of error related root folder, etc.'
@kentWeare, tried locally and it is working. But problem is when deploying Logic App it is erroring out getting this error when running GetFunctionFailed The function 'logicapptest' does not exist in the function app.
Hey Kent, are you using a different A extension? We dont get the option to choose "Logic Apps with Custom Code" vs "workflow" option when creating a new workspace. We are not even given the option to select with or without code, it always creates the workspace with code. Also, everything works locally , but when we deploy Logic Apps directly from VS code, and when we try to run the Logic App in Azure Portal we get the following error in the Local Function action. Do we need to deploy the function separately? I see the DLL in the Assemblies folder!!! GetFunctionFailed The function 'customcodefun' does not exist in the function app.
Sounds like you have an older extension. In VS code you should be using the latest 2.72.2. As for runtime error, we do support App Insights logging so you can add some additional logging. Otherwise you may see some additional info in the exceptions table for that execution. Check out this video for more details: ua-cam.com/video/YK_RpacEOJ8/v-deo.htmlsi=2ShBgqp4JYja0PvB
Hi Kent, super interesting to be able to combine logic apps low code with custom code for specific logic that is not available as an action. My question is if it is possible to add the visual studio code workspace and projects to an already existing logic app that was created using the designer in the browser, and how to go about that ? I would like to add a function call to an existing logic app using the new features you demonstrated.
it will be easier to copy workflows from existing project into the new workspace structure than the other way around. I talk about it in this video: ua-cam.com/video/DjvZKtl7oeM/v-deo.html
@@KentWeare Very sorry to bother you Kent, but I'm stuck. I generated the weatherforecast app using VerifyHash as the function name. After deployment of the workflow, In the run history, I get an error on the function call action saying: GetFunctionFailed The function 'VerifyHash' does not exist in the function app. What could be causing this ? Is there a community for this type of questions ? Stephane
@@KentWeare I give up for today. After numerous tries to deploy and redeploy, I can't get the boilerplate logic app to run successfully. The logic app runs, but the call to the local function fails with message: "GetFunctionFailed. The function 'VerifyHash' does not exist in the function app.
Kent, can we have multiple Functions within a project and call these from Logic Apps? I could not find a way to create a new Function and it looks like the metadata created only has one entry point. Any examples out there on how to create multiple Functions to call from Logic Apps? Any help is appreciated.
Under the hood, we are provisioning a function so the programming model is largely the same. What is different is that you don't have to pay for another hosting plan to run your code. You also don't have another deployment to manage, secure and monitor. So the benefits, in my mind, are largely related to the operational overhead of managing another service when you have "integration code" that your workflow(s) are dependent upon.
Thank you very much, Kent! while creating workspace, I don't get same options as yours. After workspace created, I have 3 .vscode folders, one under base folder with all launch,settings and tasks json files, one under Function folder with 4 json files including one extra as externsions.json files, one under LogicApp, but only extensions.json file. When I do dotnet build under Function folder, I don't get dll under bin folder of LogicApp. Also I cannot open workflow in design mode, some kind of error related root folder, etc.'
Can you create a Logic App without custom code and load the designer? I would validat that first. It sounds like a pre-req issue.
@kentWeare, tried locally and it is working. But problem is when deploying Logic App it is erroring out getting this error when running GetFunctionFailed
The function 'logicapptest' does not exist in the function app.
resolved using the appsettings the App Type
Hey Kent, are you using a different A extension? We dont get the option to choose "Logic Apps with Custom Code" vs "workflow" option when creating a new workspace. We are not even given the option to select with or without code, it always creates the workspace with code.
Also, everything works locally , but when we deploy Logic Apps directly from VS code, and when we try to run the Logic App in Azure Portal we get the following error in the Local Function action. Do we need to deploy the function separately? I see the DLL in the Assemblies folder!!!
GetFunctionFailed
The function 'customcodefun' does not exist in the function app.
Sounds like you have an older extension. In VS code you should be using the latest 2.72.2. As for runtime error, we do support App Insights logging so you can add some additional logging. Otherwise you may see some additional info in the exceptions table for that execution. Check out this video for more details: ua-cam.com/video/YK_RpacEOJ8/v-deo.htmlsi=2ShBgqp4JYja0PvB
Hi Kent, super interesting to be able to combine logic apps low code with custom code for specific logic that is not available as an action. My question is if it is possible to add the visual studio code workspace and projects to an already existing logic app that was created using the designer in the browser, and how to go about that ? I would like to add a function call to an existing logic app using the new features you demonstrated.
it will be easier to copy workflows from existing project into the new workspace structure than the other way around. I talk about it in this video: ua-cam.com/video/DjvZKtl7oeM/v-deo.html
@@KentWeare Just a small follow-up question. How do I get the existing project into visual studio code ?
@@stephanebouillon2538 if you have an existing project in Azure Portal, you can export it.
@@KentWeare Very sorry to bother you Kent, but I'm stuck. I generated the weatherforecast app using VerifyHash as the function name. After deployment of the workflow, In the run history, I get an error on the function call action saying: GetFunctionFailed
The function 'VerifyHash' does not exist in the function app. What could be causing this ? Is there a community for this type of questions ? Stephane
@@KentWeare I give up for today. After numerous tries to deploy and redeploy, I can't get the boilerplate logic app to run successfully. The logic app runs, but the call to the local function fails with message: "GetFunctionFailed. The function 'VerifyHash' does not exist in the function app.
Kent, can we have multiple Functions within a project and call these from Logic Apps? I could not find a way to create a new Function and it looks like the metadata created only has one entry point. Any examples out there on how to create multiple Functions to call from Logic Apps? Any help is appreciated.
Yes, you can have multiple functions. I will email you
@@KentWeare Can you make a video on this please? Been trying to figure this out for quite a while. Cheers
@@andrewlahikainen4627 sure..can do that. Has come up a bit recently from other places. What would you prefer .NET 8 or .NET FX?
Nice walkthru, but what is really the different from using azure function instead? Its even easier? Or am I missing something here
Under the hood, we are provisioning a function so the programming model is largely the same. What is different is that you don't have to pay for another hosting plan to run your code. You also don't have another deployment to manage, secure and monitor. So the benefits, in my mind, are largely related to the operational overhead of managing another service when you have "integration code" that your workflow(s) are dependent upon.
@@KentWeare ok thx kent