Recently I had a project where I needed to use the Microsoft Office Excel BAM add-in. At Codit Belgium, where I work, we have an Office 365 subscription.
I followed the guide Enabling BAM Add-In for Excel 2016, by Sandro Perreira, but was unable to find the BAM Add-in within my Excel installation.
When virtualizing your APIs behind an Azure API Management (APIM) service, you always need to provide the subscription key in your calls. Typically, this is done via the header key Ocp-Apim-Subscription-Key. Your subscription key is always linked to an APIM product which you define in your publisher portal.
Sometimes, you might want to disable working with a subscription key altogether. Although this might not be the best idea, it is easier to use in development scenarios and might sometimes be preferred when working with certain legacy applications which cannot easily be changed.
Note: “TIL” posts are short on purpose. They are meant as a quick way to share something I learned or found. This might be something trivial to some people, but they are new to me. TIL stands for Today I Learned.
Today I was editing a Swagger file with Visual Studio Code. I was looking for an extension to be able to compare two files with each other. They were not in source control, so I was not able to use that…
I found that comparing files is actually built-in into Visual Studio Code!
With the latest CU’s for BizTalk Server, the Purge and Archive job can now be configured to clean up orphaned instances. The biggest advantage is that the cleanup is done without any downtime…. yes this means you no longer need to run the BizTalk Health Monitor to clean them up!
The change was marked in the following Microsoft Support article: Orphaned BizTalk DTA service instances are not removed by the “DTA Purge and Archive” job in BizTalk Server
Every now and then, when dealing with BizTalk orchestrations, you might encounter issues you can’t explain. Things like the following, infamous error, may occur without any valid reason:
#error: Errors exist for one or more children
Even after fixing every error, you rebuild the project and/or solution, and the error is still not fixed…
You may know the issue when opening a BizTalk orchestration and it opens like this:
Note: I blurred the code to protect the name of my client.
Not much you can do about it, except right-clicking the orchestration and clicking ‘Open With…’ and choosing the BizTalk Orchestration Designer.
However, if you close the BizTalk Orchestration Designer again, and double-click the odx file, it once again opens in the first, yet useless, view.
(This blog post was co-written by Pieter Vandenheede & Glenn Colpaert, both colleagues at Codit)
We finally admit it… we both were the brains behind the CrazyBizTalk account. There… it’s in the open. After Integrate 2017, day 3, we were no longer able to keep it a secret, so there is no use of denying it anymore…
It was a fun ride, which started in 2013 already. We’ve written this post to give you some insights on how it all got started, the fun we had through the years and what the next steps are.