Hello everyone,
I am using the FetchXML Builder and the query shows exactly what I want.
{% fetchxml testXML %}
<fetch>
<entity name="test_table">
<attribute name="attr1" />
<attribute name="LookUpField" />
<attribute name="attr3" />
<attribute name="attr4" />
<link-entity name="linked_Table" from="xyz_id" to="name" alias="nameXYZ" visible="true">
<attribute name="nameXYZ" />
</link-entity>
</entity>
</fetch>
{% endfetchxml %}
I want to retrieve a LookupField. But whysoever there's nothing displaying inside the LookUpField when I display it in a JSON.
I tried different combinations as below:
[
{% for item in testXML.results.entities %}
{
"Test1" : "{{ item.LookUpField }}",
"Test2" : "{{ item.nameXYZ }}",
"Test3" : "{{ item.LookUpField.nameXYZ }}"
}{% unless forloop.last %}, {% endunless %}
{% endfor %}
]
Inside the FetchXML Builder it's working fine, but the fetchXML inside my pagetemplate seems to have an issue.
Do I need to give the FetchXML additional access or something as it is not even displaying the GUID neither the Name which is referenced inse the LookUp.
Has somebody come across something like that or know how I can display the linked name attribute of the lookup column?
Solved! Go to Solution.
I finally found a solution.
[
{% for item in testXML.results.entities %}
{
"Test1" : "{{ item.['yourAliasFieldName.yourNameofTheFieldInsideTheRelatedTable']}}"
}{% unless forloop.last %}, {% endunless %}
{% endfor %}
]
It is difficult to find something like that when there's nowhere a documentation.
@ragavanrajanmaybe you could submit that to the product team and ask them to include it into the documentation.
Hi @Lucas001
For the lookup column table, hope you have set enough table permissions and assigned web roles properly. Please check all your table permissions
Hope it helps.
------------
If you like this post, give it a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users to find it.
Hi @ragavanrajan,
what I don't get. I can display the needed data in a view in a form or anything else. As I created the FetchXML witht he builder and it is working fine inside its UI as well. Copying that code and just trying to display it inside a JSON doesn't work.
Is there anything else one has to give permission when using FetchXML with a LookUp Column?
I finally found a solution.
[
{% for item in testXML.results.entities %}
{
"Test1" : "{{ item.['yourAliasFieldName.yourNameofTheFieldInsideTheRelatedTable']}}"
}{% unless forloop.last %}, {% endunless %}
{% endfor %}
]
It is difficult to find something like that when there's nowhere a documentation.
@ragavanrajanmaybe you could submit that to the product team and ask them to include it into the documentation.
sure @Lucas001
Thanks for the answer. I will pass the info and you can see some updates in the docs soon.
Thanks again.
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!
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
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.
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