We are working on a migration of a BizTalk implementation. There are lot's of XSLT files to be transformed.
Most of them use an external assembly to perform some basic tasks. They usually run without issues.
But sometimes (we haven't found a pattern yet) the Transform XML action complains that it can't find the assembly.
Even for mappings that ran without issues before and the assembly is registered in the integration account.
The current way we fix the issue is delete the map(s) and assembly from the integration account and redeploy it.
As you can understand, this is very annoying. When moving into PRD this can cause some major issues.
To upload the XSLT files we use the Set-AzResource and New-AzResource commands.
Plan Type
Consumption
Steps to Reproduce the Bug or Issue
Reproducing is difficult since it seems to be triggered at random.
It can occur at any time you create/update the mapping in the integration account through a Devops Pipeline
Describe the Bug
We are working on a migration of a BizTalk implementation. There are lot's of XSLT files to be transformed. Most of them use an external assembly to perform some basic tasks. They usually run without issues. But sometimes (we haven't found a pattern yet) the Transform XML action complains that it can't find the assembly. Even for mappings that ran without issues before and the assembly is registered in the integration account.
The current way we fix the issue is delete the map(s) and assembly from the integration account and redeploy it. As you can understand, this is very annoying. When moving into PRD this can cause some major issues.
To upload the XSLT files we use the Set-AzResource and New-AzResource commands.
Plan Type
Consumption
Steps to Reproduce the Bug or Issue
Reproducing is difficult since it seems to be triggered at random. It can occur at any time you create/update the mapping in the integration account through a Devops Pipeline
Workflow JSON
Screenshots or Videos
No response
Additional context
No response