I have 3 dataverse tables that we are using to track project related details. I need to be able to search by ID or Name in each of the tables and filter a gallery based on the records. The code below pulls in all the data that is related, so as long as the Story has a Feature and the Feature has a Project the below works. When the Feature does not have a Story and when the Project does not have a Feature or Story, the search does not work as the collection is only pulling the related rows. How can I create a collection that joins all of the matching data but also includes the non-matching records as well?
Dataverse Tables
ClearCollect(colSearch,
AddColumns(
STORY_TABLES,
"_featureID",
LookUp(FEATURE_TABLES,Text(FeatureName) = Text(FeatureLookUp.FeatureName)).'Delivery Feature ID',
"_featureName",
LookUp(FEATURE_TABLES,Text(FeatureName) = Text(FeatureLookUp.FeatureName)).'Feature Name',
"_projectName",
LookUp(PROJECT_TABLES,Text(ProjectNameLookUp) = Text(ProjectLookUp.ProjectNameLookUp)).'Project Name',
"_projectID",
LookUp(PROJECT_TABLES,Text(ProjectNameLookUp) = Text(ProjectLookUp.ProjectNameLookUp)).'Project ID'))
What I get from the collection:
Project ID | Project Name | Feature ID | Feature Name | Story ID | Story Name |
1 | Project 1 | 11 | Feature 1 | 1111 | Story 1111 |
2 | Project 2 | 22 | Feature 2 | 2221 | Story 2221 |
2 | Project 2 | 22 | Feature 2 | 2222 | Story 2222 |
4 | Project 4 | 44 | Feature 4 | 4444 | Story 4444 |
What I am needing:
Project ID | Project Name | Feature ID | Feature Name | Story ID | Story Name |
1 | Project 1 | 11 | Feature 1 | 1111 | Story 1111 |
2 | Project 2 | 22 | Feature 2 | 2221 | Story 2221 |
2 | Project 2 | 22 | Feature 2 | 2222 | Story 2222 |
3 | Project 3 |
|
|
|
|
4 | Project 4 | 44 | Feature 4 | 4444 | Story 4444 |
5 | Project 5 | 55 | Feature 5 |
|
|
Solved! Go to Solution.
Hi @todaytoo ,
According to your description, you want to show the all Project in your collection. And you have three table in Dataverse .
I test it in my side , here are the steps you can refer to :
(1)This is my test data:
The "FeatureLookUp" and "ProjectLookUp" in the 'Story' Table are LookUp type columns.
The "ProjectLookUp" in the 'Feature_Table' is LookUp type columns.
For your need , I think you need to get the corresponding data in the story first, just like you are doing now, and then we have to get the value that does not exist in the Feature table, use the Collect function to chase to the Collection we got earlier, and then in the same way to get the value that does not exist in the Project table, and use the Collect function to track to the Collection we obtained earlier.
(2)Then i use this code to get the table you need(You need to change the table names and column names I have here to the corresponding names on your side):
ClearCollect(
test,
ShowColumns(
AddColumns(
Stories,
"FeatureId",
FeatureLookup.FeatureID,
"ProjectId",
ProjectLookUp.ProjectID,
"FeatureName",
FeatureLookup.FeatureName,
"ProjectName",
ProjectLookUp.ProjectName
),
"cr667_stortyid",
"cr667_storyname",
"FeatureId",
"FeatureName",
"ProjectId",
"ProjectName"
)
);
ClearCollect(
test_feature,
test.FeatureId
);
ClearCollect(
test_features,
RenameColumns(
ShowColumns(
AddColumns(
Feature_Tables,
"ProjectId",
ProjectLookUp.ProjectID,
"ProjectName",
ProjectLookUp.ProjectName
),
"cr667_featureid",
"cr667_featurename",
"ProjectName",
"ProjectId"
),
"cr667_featureid",
"FeatureId",
"cr667_featurename",
"FeatureName"
)
);
ForAll(
test_features,
If(
!(ThisRecord.FeatureId in test_feature),
Collect(
test,
ThisRecord
)
)
);
ClearCollect(
Projects,
RenameColumns(
ShowColumns(
ProjectTests,
"cr667_id",
"cr667_name"
),
"cr667_id",
"ProjectId",
"cr667_name",
"ProjectName"
)
);
ForAll(
Projects,
If(
!(ThisRecord.ProjectId in test.ProjectId),
Collect(
test,
ThisRecord
)
)
)
Then we can get the 'test' Table like this :
Best Regards,
Wearsky
Hi @todaytoo ,
According to your description, you want to show the all Project in your collection. And you have three table in Dataverse .
I test it in my side , here are the steps you can refer to :
(1)This is my test data:
The "FeatureLookUp" and "ProjectLookUp" in the 'Story' Table are LookUp type columns.
The "ProjectLookUp" in the 'Feature_Table' is LookUp type columns.
For your need , I think you need to get the corresponding data in the story first, just like you are doing now, and then we have to get the value that does not exist in the Feature table, use the Collect function to chase to the Collection we got earlier, and then in the same way to get the value that does not exist in the Project table, and use the Collect function to track to the Collection we obtained earlier.
(2)Then i use this code to get the table you need(You need to change the table names and column names I have here to the corresponding names on your side):
ClearCollect(
test,
ShowColumns(
AddColumns(
Stories,
"FeatureId",
FeatureLookup.FeatureID,
"ProjectId",
ProjectLookUp.ProjectID,
"FeatureName",
FeatureLookup.FeatureName,
"ProjectName",
ProjectLookUp.ProjectName
),
"cr667_stortyid",
"cr667_storyname",
"FeatureId",
"FeatureName",
"ProjectId",
"ProjectName"
)
);
ClearCollect(
test_feature,
test.FeatureId
);
ClearCollect(
test_features,
RenameColumns(
ShowColumns(
AddColumns(
Feature_Tables,
"ProjectId",
ProjectLookUp.ProjectID,
"ProjectName",
ProjectLookUp.ProjectName
),
"cr667_featureid",
"cr667_featurename",
"ProjectName",
"ProjectId"
),
"cr667_featureid",
"FeatureId",
"cr667_featurename",
"FeatureName"
)
);
ForAll(
test_features,
If(
!(ThisRecord.FeatureId in test_feature),
Collect(
test,
ThisRecord
)
)
);
ClearCollect(
Projects,
RenameColumns(
ShowColumns(
ProjectTests,
"cr667_id",
"cr667_name"
),
"cr667_id",
"ProjectId",
"cr667_name",
"ProjectName"
)
);
ForAll(
Projects,
If(
!(ThisRecord.ProjectId in test.ProjectId),
Collect(
test,
ThisRecord
)
)
)
Then we can get the 'test' Table like this :
Best Regards,
Wearsky
Thank you so much! Exactly what I needed. I really appreciate it!
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 in the Forums 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. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08 23 @WarrenBelz 31 @DBO_DV 10 @Amik 19 AmínAA 6 @mmbr1606 12 @rzuber 4 @happyume 7 @Giraldoj 3@ANB 6 (tie) @SpongYe 6 (tie) 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. Community MembersSolutionsSuper UsersSolutions @anandm08 10@WarrenBelz 25 @DBO_DV 6@mmbr1606 14 @AmínAA 4 @Amik 12 @royg 3 @ANB 10 @AllanDeCastro 2 @SunilPashikanti 5 @Michaelfp 2 @FLMike 5 @eduardo_izzo 2 Meekou 2 @rzuber 2 @Velegandla 2 @PowerPlatform-P 2 @Micaiah 2 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 Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27 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 Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8 SunilPashikanti8
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