General rantings about .NET, Linux, Biztalk and the odd hardware fun
I recently needed to access the tablebrowser in FO and found the nifty hint here:
You can access the table browser using the URL string you use to get to the Dynamics 365 Finance and Operations application. At the end of the URL after “dynamics.com/” you can add the following string and replace a few values with values you need.
“?mi=SysTableBrowser&TableName=CustTable&cmp=USMF&lng=en-us&limitednav=true”
As can be found several places, an Azure Function is not always deployed with all dependencies to Azure – apparantly because Microsoft has added a list of “standard” libraries/packages that should always be available on the Azure platform
This results in a nasty error
Could not load file or assembly ‘System.Configuration.ConfigurationManager, Version=5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’. The system cannot find the file specified.”:”System.Configuration.ConfigurationManager, Version=5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35″}
The solution is to use the undocumented property _FunctionsSkipCleanOutput like this in the .csproj file
.. removed ..
<PropertyGroup>
<TargetFramework>netcoreapp3.1</TargetFramework>
<AzureFunctionsVersion>v3</AzureFunctionsVersion>
<_FunctionsSkipCleanOutput>true</_FunctionsSkipCleanOutput>
</PropertyGroup>
.. removed ..
I my case, a used library System.Runtime.Caching was using the System.Configuration.ConfigurationManager library, and the latter was left out when deployed
This was on Microsoft.NET.Sdk.Functions (3.0.9)
In the LogicApp ARM template, you can specify an optional “state” value
…
“resources”: [
{
// Start logic app resource definition
“properties”: {
“state”: “”,
“definition”: {},
“parameters”: {}
},
…
Continue reading “Do not auto-enable a LogicApp when deployed”
During a recent migration between Azure tenants, I encountered the dreaded
Unhandled Exception: System.IO.DirectoryNotFoundException: The path `C:\REPOS\AzureFunctionsProject\obj\Release\net461\PubTmp\Out\bin` does not exist. Unable to generate Azure Functions extensions metadata file.
error when I tried to publish an Azure Function to the new tenant. And quite correctly, the ‘bin’ folder does not exist.
My “Microsoft.NET.Sdk.Functions” Version was “1.0.24” and it worked for me to follow the advise below to change that to use version 1.0.26 (by editing the .csproj file directly)
I probably ought to have tried with the newest version of the SDK, but time constraints in the project did not allow that.
Cant publish azure function unabe to generate azure function metadata
If you are using the “Logic Apps Management” solution in Azure Log Analytics to get an overview of the state of all your LogicApps, you may see that the solution-overview does not render. It simply seems to be trying to gather the data to show for eternity. This can also be seen, if you pin it to a dashboard
Continue reading “Azure “Logic Apps Management” does not render in “Incognito” browser”
When you only have access to one Azure directory, AzCLI and the Az Powershell module can figure out the Authentication itself, but if you have access to multiple directories on one user, you have to be more specific – especially if one of the directories uses MFA.
The typical “Get started” introductions does not cover this.
I have not tried it with multiple directories all requiring (different) MFA…
Continue reading “Authenticating to Azure with AzCli og the Az Powershell module”
Sometimes the simplest things become hard(er)
Normally it is not a problem terminating the Logic App run by using a Terminate action. But when you are iterating over some kind of list using a “ForEach” action, you are suddenly not allowed to use a “Terminate” action anymore. And Logic Apps does not provide any other way to stop a Logic App run.
Continue reading “Logic Apps: ForEach and Terminate actions”
While taking some Azure certifications, I have several times experienced this error during some Labs.
After creating a new webapi with
dotnet new webapi --output . --name SimpleApithe ensuing
dotnet runalways fails with this error on my Windows 10 development pc.
info: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[0]
User profile is available. Using ‘C:\Users\XXXX\AppData\Local\ASP.NET\DataProtection-Keys’ as key repository and Windows DPAPI to encrypt keys at rest.
crit: Microsoft.AspNetCore.Server.Kestrel[0]
Unable to start Kestrel.
System.InvalidOperationException: Unable to configure HTTPS endpoint. No server certificate was specified, and the default developer certificate could not be found or is out of date.
To generate a developer certificate run ‘dotnet dev-certs https’. To trust the certificate (Windows and macOS only) run ‘dotnet dev-certs https –trust’.
For more information on configuring HTTPS see https://go.microsoft.com/fwlink/?linkid=848054.The instructions on this page does not initially help much. As other people also experience, one dotnet dev-certs command says no valid certificates exist while another says that one already exists.
What have worked for me until now, is to first clear my pc of all existing dev certificates and then generate a new one. I seem to have to do this everytime i create a new project…
dotnet dev-certs https –clean
dotnet dev-certs https –trustI always comment out the app.UseHttpsRedirection(); in the autogenerated Startup.cs class, but it does not make any difference.
From time to time (or what seems like VERY often), you might not get the option for selecting your Azure subscription/resourcegroup in Visual Studio Logic Apps Designer, when you open a Logic Apps project. This happes even when you are logged into an Azure account.
Continue reading “Unable to select Azure subscription in Visual Studio Logic Apps deployment”
In some cases, you might want to use more than one trigger in a Logic App. This can for instance be when you hook up to a D365 CE environment and use the “Common Data Service” Connector in Logic Apps to subscribe to changes
Here, it might make sense to have two triggers (one for the event “When_a_record_is_created” and one for the event “When_a_record_is_updated”) since both can often be handled similarly – at least if you are inserting or updating them in a SQL-server.
This is easy to do, since you in the following actions always can refer to “@triggerbody()” no matter which trigger has fired.
But what can you do, if you also would like to include the “When_a_record_is_deleted” trigger in the same Logic App. It potentially could be handled by the same Stored Procedure (for instance), but where the data from CDS is similar whether it is a “created” or an “updated” event, CE only sends the CE record GUID when it triggers the “deleted” event. This would probably make it less obvious to use the same handling for all 3 triggers.
You can actually query the logic app, for which trigger was in fact triggered. You can use the “@trigger()?[‘name’]” in a condition to compare it with trigger-names and behave differently depending on the trigger.
It can very well be argued, if it is a good idea to pack both INSERT, UPDATE and DELETE handling into one single Logic App, but in our case we are having a LOT of Logic Apps already, and it clutters the view the more Logic Apps are added. Also, the CE tables in question are small, seldom-updated tables.