FetchXML improve for us to achieve more

I got a challenge from my colleague at CRMK:

I need to set owners on accounts with a team with the same name as the account.
Mia @ CRMK

Is that even possible??
Yes, it actually is.

Simplest query

I start with a very simple query to get all Accounts:

<fetch>
  <entity name='account'>
    <attribute name='name' />
    <attribute name='ownerid' />
  </entity>
</fetch>

New supported link-entity feature

I need to join with Teams, not by a relationship like OwnerId, but by their only Name.

<fetch>
  <entity name='account'>
    <attribute name='name' />
    <attribute name='ownerid' />
    <link-entity name='team' from='name' to='name'>
      <attribute name='name' />
      <attribute name='teamid' />
    </link-entity>
  </entity>
</fetch>

Are those from and to attributes on the link-entity node supported?? Well, oh yes! Do read! No relationships

Unexpected new filtering feature

Also, I don’t want to return accounts that already have the correct owner, so I add a filter by a really new cool feature…

<fetch>
  <entity name='account'>
    <attribute name='name' />
    <attribute name='ownerid' />
    <filter>
      <condition attribute='ownerid' operator='ne' valueof='T.teamid' />
    </filter>
    <link-entity name='team' from='name' to='name' alias='T'>
      <attribute name='name' />
      <attribute name='teamid' />
    </link-entity>
  </entity>
</fetch>

I thought I just found this unsupported feature when I was testing/trying a few months ago… But in the newly released documentation, it just is there! Read about this doc too: Cross table comparisons