cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Query entity details with lookup field using Liquid

I have an entity with a lookup from another entity. I added this lookup using the relationship tab in the entity details. I have a department entity and programmer entity. The programmer entity has a field lookup to the department entity. I would like to get a list of programmers based on the department ID query string passed. 

 

My code looks like this: 

 

{% fetchxml programmers %}
      <fetch version="1.0" mapping="logical" output-format="xml-platform" distinct="true" returntotalrecordcount="true">
        <entity name="syst_programmer">
          <attribute name="syst_name" />
          <attribute name="syst_department" />
          <link-entity name="syst_department" from="syst_department" to="syst_departmentid" visible="true" link-type="outer" alias="ai">
            <attribute name="syst_departmentid" />
            <attribute name="syst_name" />
          </link-entity>
        </entity>
      </fetch>
      {% endfetchxml %}

{% if programers.results.total_record_count > 0 %}
{% assign id = request.params['id'] %}
      <div class="row">
        {% for p in programmers.results.entities %}
        <div class="col-md-4" style="text-align: center;">
          <a href="/departments/departmentinfo?id={{id}}">
            <H4>{{p.syst_department.syst_name}}</H4>
            {{p['ai.name']}} (this is alias value)
    
            </br>
          </a>
        </div>

        <!-- Note filtering of currency format -->
        {% endfor %}
      </div>
      {% endif %}

I am not sure how to use the link-entity, what's the correct format for it here? Any examples out there for the power apps portals? I'd like from the ID of the department, to display the name of the department, and then a list of all programmers that have that department as a lookup. 

Thanks for any guidance. 
1 ACCEPTED SOLUTION

Accepted Solutions

Hi

can you change this line:

      {% if programmers.results.total_record_count > 0 %}

 to this:

      {% if programmers.results.entities.size > 0 %}

also I noticed that now you are no longer using join/link-entity, which is fine 

but notice that as you made the search in Advanced Find it is now hard-coded the GUID of your department

that's not a problem as long as you have the same GUID in all environment

another option would be filtering (in advanced find) by the Related Entities, and then searching by name.. this would generate the join in your fetch




If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users find it.

Power Pages Super User | MVP


Oliver Rodrigues


 

View solution in original post

8 REPLIES 8
OliverRodrigues
Most Valuable Professional
Most Valuable Professional

Hi

 

What's the issue you are facing? are you getting any errors or not returning results..

did you create entity permissions for both entities?

 

just one thing in your code might be wrong:
p['ai.name']}}
you might be missing the attribute prefix
p['ai.syst_name']}}

------------

If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users find it.

 




If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users find it.

Power Pages Super User | MVP


Oliver Rodrigues


 

Hi @OliverRodrigues  Thanks for your response! 

 

Yes I have set entity permissions on both the department and programmer entities. I also changed the attribute reference to be ai.syst_name .

It's giving me this error: 

 

Liquid error: Exception has been thrown by the target of an invocation.

 

When I remove the linked entity code from fetch xml, the error is gone, that's why am not sure if this is the right syntax? 

This is the code that's when removed hides the error: 

 

    <link-entity name="syst_department" from="syst_department" to="syst_departmentid" visible="true" link-type="outer" alias="ai">
            <attribute name="syst_departmentid" />
            <attribute name="syst_name" />
          </link-entity>


I saw some posts on the internet without the "to" attribute, or makes it point to something like parented. But I don't understand how these work? I started with it simple without even filtering based on the current ID, but it's not working.. my end goal would be to have the link entity filtered by the current passed ID in the query string. 

 
 

you should keep both from and to as a good practice

from your code:

from="syst_department" 

to="syst_departmentid"

 

the from is usually the primary key from the linked entity.. so it should be syst_departmentid

the to should be the logical name for the lookup in your child entity, can you double check what is the name for that?

 

what you can always do is generate the fetchxml via Advanced Find, saves you a lot of time 




If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users find it.

Power Pages Super User | MVP


Oliver Rodrigues


 

@OliverRodrigues 
Thank you for the advanced find, I didn't know about that. 

I generated the fetchxml code, it returns a result in the advanced find, but when added to my liquid code, it's not returning anything (no error, but 0 result), here's my code: 

 
 
 {% fetchxml programmers %}
      <fetch version="1.0" output-format="xml-platform" mapping="logical" distinct="false">
        <entity name="syst_programmer">
          <attribute name="syst_programmerid" />
          <attribute name="syst_name" />
          <attribute name="createdon" />
          <attribute name="syst_department" />
          <attribute name="syst_about" />
          <order attribute="syst_name" descending="false" />
          <filter type="and">
            <condition attribute="syst_department" operator="eq" uiname="JavaScript" uitype="syst_department" value="{69CF501D-98C3-EA11-A812-000D3ABA3FFB}" />
          </filter>
        </entity>
      </fetch>
      {% endfetchxml %}
 
      <!-- Parse through results -->
      {% if programmers.results.total_record_count > 0 %}
     test
      <div class="row">
        {% for p in programmers.results.entities %}
      test in loop
        <H4>{{p.syst_name}}</H4>
        <div class="col-md-4" style="text-align: center;">
            <H4>{{p.syst_department}}</H4>
            </br>
        </div>
        <!-- Note filtering of currency format -->
        {% endfor %}
      </div>
      {% else %}
      no result
      {% endif %}


I always see the "no result"

Any idea?
The fetchxml code is what I downloaded from the advanced find.

Hi

can you change this line:

      {% if programmers.results.total_record_count > 0 %}

 to this:

      {% if programmers.results.entities.size > 0 %}

also I noticed that now you are no longer using join/link-entity, which is fine 

but notice that as you made the search in Advanced Find it is now hard-coded the GUID of your department

that's not a problem as long as you have the same GUID in all environment

another option would be filtering (in advanced find) by the Related Entities, and then searching by name.. this would generate the join in your fetch




If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users find it.

Power Pages Super User | MVP


Oliver Rodrigues


 

That worked! Thanks!

 

But what's the difference between doing the filter with how I did it now, and doing it based on a related entity? 

Brilliant.. can you mark as the solution so it can help other people as well?

 

if you are working on DEV environment, once you go to TEST / PROD you need to make sure the GUID of the records are the same.. if not your fetch won't work as it won't find a record with that GUID




If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users find it.

Power Pages Super User | MVP


Oliver Rodrigues


 

Thanks for the help! 

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results |Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 1: Community MembersSolutionsSuper UsersSolutionsPower Pages @Inogic  1   @ragavanrajan  2 @aofosu  1 @Jcook  1Open  @OliverRodrigues  1Open  @Lucas001  1Open Open    Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 2: Community MembersSolutionsSuper UsersSolutionsPower Pages @taraubianca25  2 @EmadBeshai  2 @ALP2  2@Fubar 2 @ekluth1  2@ragavanrajan 1 @mandela  1@OliverRodrigues 1 @Ajlan  1Open   @elishafxx  1    @TA_Jeremy  1    @helio1981  1       Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower PagesInogic2@EmadBeshai 6Ajlan1@ragavanrajan 4CraigWarnholtz1@Fubar 4  @Jcook 3  @OliverRodrigues2   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower PagesHenryed071Fubar3Inogic1OliverRodrigues2JacoMathew1EmadBeshai2faruk11  TA_Jeremy1   shubhambhangale1   doug-ppc1   hubjes1  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

  On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Top Kudoed Authors
Users online (2,223)