We are trying to follow the steps documented in these two blog posts:
https://uds.systems/blog/how-to-run-custom-code-in-dynamics-365-portal
https://www.engineeredcode.com/blog/hacking-your-way-to-server-side-code-with-dynamics-365-portals-just-like-microsoft
We have the entity in place and we have a plugin that runs the logic we need.
The plugin is fired when we query from XRMToolbox with the View or Serialized/Explicit XML options selected. When we have "Raw fetch result" selected the plugin is not fired. This has been verified using the Plugin Trace Log set to "All" and nothing shows up with "Raw fetch result" is selected.
The real problem we are trying to solve is that the plugin is not fired from our Portal Liquid syntax.
Here is the Liquid syntax:
{% fetchxml create-order-query %}
<fetch distinct="false" no-lock="false" output-format="xml-platform" mapping="logical" >
<entity name="trit_portalaction" >
<attribute name="trit_response" />
<filter type="and" >
<condition attribute="trit_name" operator="eq" value="createorder" />
<condition attribute="trit_parameters" operator="eq" value="userid=E883375A-85A7-40A8-B32F-2F80DF83FF72cb1075-9087-ea11-a812-000d3a17769f;productid=6cf5e0d8-9479-ea11-a812-000d3a8a4127" />
<condition attribute="trit_response" operator="eq" value='{{"today" | date: "yyyy-MM-dd HH:mm:ss"}}' />
</filter>
</entity>
</fetch>
{% endfetchxml %}
