Friday Fact: Welcome Logic Apps Designer “v4” (Public Preview)
Dec 19, 2025
If you’ve been building Logic Apps for a while, you’ve probably felt the designer evolve in waves And recently, the Logic Apps team announced a major
Logic App Data Mapper Error: ‘xsl’ is an undeclared prefix
Oct 22, 2025
Recently, while preparing my Logic App Data Mapper demos for the Nordic Integration Summit (NIS) 2025, I encountered this error while trying to configure a
Logic App Data Mapper Error: Invalid or unrecognized expression ‘concat()’ extraneous...
Oct 21, 2025
Recently, while preparing my Logic App Data Mapper demos for the Nordic Integration Summit (NIS) 2025, I encountered this error while trying to test/execute a
Azure Logic Apps Naming Conventions whitepaper
Jul 10, 2025
In today’s rapidly evolving digital landscape, automation and integration are no longer optional Instead, they have become essential for successful
Join me at AVIATORS Community Event 2025 Hamburg | June 12, 2025 | A walk in the park with the br...
May 29, 2025
I’m thrilled to announce that I’ve been invited to participate in the second Aviators Germany Community event in Hamburg on June 12 Moreover, this marks
Friday Fact: There is a new-new Data Mapper for Logic App Standard
May 23, 2025
In November 2023, the Logic Apps team released the first Data Mapper for Logic Apps Standard in General Availability However, did you know that a brand‑new
Friday Fact: The name of When a HTTP request is received trigger affects the workflow URL
May 16, 2025
Yes, you are reading it right! Something so basic, so apparently harmless, can lead to unexpected behavior or integration issues: The name of the "When a HTTP
Friday Fact: Logic App Parameters naming size limits and restrictions
Apr 4, 2025
In the past, we had a similar Friday Fact: Friday (funny) Fact: There is no size limit for the Logic App parameter name But on that, we didn't go through all
Logic App Standard: Trigger History Error – InvalidClientTrackingId
Mar 18, 2025
Last week, while trying to customize the Custom tracking ID property of the workflow trigger, we noticed that there were no new workflow executions While



