Sorry, I haven’t seen that error before, but do you really need a custom functoid? They make the install process for your solution miserable. Seriously, I have seen very few custom functoids that were useful enough to justify the extra pain and suffering of installing them. You can solve many of the same problems using a scripting functoid and an external assembly. It is not as elegant of a solution, but is much easier to install.
Search this Site:
Recent Posts
- Logic App Consumption deployment: The secret of KeyVault parameter cannot be retrieved. Http status code: ‘Forbidden’. Error message: ‘Access denied to first party service
- BizTalk Server Visual Studio project: attempted re-targeting of the project has been canceled.
- BizTalk Oracle Adapter error: The assembly required for type mapping not found.
- PowerShell script to identify all SQL V1 actions and triggers inside Logic Apps Consumption
- Friday (funny) Fact: There is no size limit for the Logic App parameter name