Forum Post: RE: Account form subgrid and related contact activity records

Hi Josh,

Thanks for replying! :)

I think I figured it out (part of it at least).  Since we were using the "contact_customer_accounts" relationship we didn't need the <link-entity name="account" ...> part at all.  However, now I have two subgrids - one with Account - level activities and one with Contact-level activities.  I was hoping there would be a way to combine them.  Or maybe that was why the <link-entity name="account" ..> part was there and I just had it positioned incorrectly?

Here is what I ended up using:

<fetchxml>

             <fetch version="1.0" output-format="xml-platform" mapping="logical" distinct="false">

               <entity name="activitypointer">

                 <attribute name="activitytypecode" />

                 <attribute name="scheduledstart" />

                 <attribute name="prioritycode" />

                 <attribute name="ownerid" />

                 <attribute name="scheduledend" />

                 <attribute name="createdon" />

                 <attribute name="statecode" />

                 <attribute name="subject" />

                 <attribute name="regardingobjectid" />

                 <order attribute="subject" descending="false" />

                 <filter type="and">

                   <condition attribute="isregularactivity" operator="eq" value="1" />

                 </filter>

<link-entity name="activityparty" from="activityid" to="activityid">

<link-entity name="contact" from="contactid" to="partyid">

</link-entity>

</link-entity>

                 <attribute name="activityid" />

               </entity>

             </fetch>

Thanks,

Debbie