The post Implementing Feature Flags for Power Apps deployment appeared first on Aric Levin's Digital Transformation Blog.

The issue that we had was that we could retrieve each list of cases individually, but the result could be duplicate where a case could be associated with both a Case Contact and an Account Contact.

We were struggling on whether to retrieve the first fetch, and then the second fetch and check the values that were part of the second fetch didn’t appear in the list of first fetches, or the alternative was to have a single fetch Xml that contained both conditions with an Or Condition in-between. The issue here is that advanced find does not allow created an Or condition with related entities.

Thanks to a post by Alex Shlega, we were able to do this easily. This can be done using XRMToolbox Fetch Xml Builder or just writing the Fetch Directly in a Text editing tool. The end result that we had was the following:

<fetch version="1.0" output-format="xml-platform" mapping="logical" distinct="true" >
  <entity name="incident" >
    <attribute name="incidentid" />
    <attribute name="title" />
    <attribute name="customerid" />
    <attribute name="xrm_businessname" />
    <attribute name="statecode" />
    <attribute name="statuscode" />
    <filter type="or" >
      <condition entityname="ad" attribute="xrm_contactid" operator="eq" value="{{user.id}}" />
      <condition entityname="ab" attribute="xrm_contactid" operator="eq" value="{{user.id}}" />
    </filter>
    <link-entity name="account" from="accountid" to="customerid" link-type="outer" alias="ac" >
      <link-entity name="xrm_accountcontact" from="xrm_accountid" to="accountid" link-type="outer" alias="ad" >
      </link-entity>
    </link-entity>
    <link-entity name="xrm_casecontact" from="xrm_caseid" to="incidentid" link-type="outer" alias="ab" />
  </entity>
</fetch>

By adding the entity names to the Or Filter, we are able to specify conditions for the linked entities, and by doing this filter multiple linked entities with an Or Condition.

This resolves the issue of having to deal with duplicates in the results or having multiple result sets from separate Xml statements.

The post Multiple Fetch Xml Statements with Or Filter in Portal Web Template appeared first on Aric Levin's Digital Transformation Blog.

The default out of the box relationship for Account of the Contact having a Scope of Contact, or even a Scope of account did not work, so we needed to set a Global Scope, basically exposing this to the Portal, but limiting what will be available using our own logic.

The image below shows the Entity Permission that we set, so that it would become global:

The next step that was needed was to design the fetchXml to retrieve all the accounts that are associated the portal logged in user. We needed to use the user.id liquid object. We created a Web Template that contained the following Xml. This would retrieve a list of all accounts that are associated with the Account Contact many to many manual entity, and display it on the Web page.

The first part of the web template, which includes the fetchXml is shown below. Notice the link-entity which contains the relationship between account and contact and the condition attribute set to the logged in user id.

The next part is retrieving all the accounts (if available). We loop through the list of accounts and display the account name, and other fields.

Finally, we can create a new web page based on a web/page template to view the results is our web portal.

The post Fetch Xml Portal page with Entity Permissions appeared first on Aric Levin's Digital Transformation Blog.