First of all I want to thank all the contributors here, I've learned more from your advices than from the official guides. However, as though I was thoroughly searching for the solution for my problem, I haven't found the solution on these pages for the last two days, so I was forced to open a new topic.
Namely, I am building a custom form application based on one SharePoint list, "Expences". There, I have a lookup column called "Budget line" that is a lookup column, getting values from "Title" column of the another list, "Budget line", and another lookup column called "Project", getting values from "Title" column of the list "Project". The "Budget line" list also has the "Project" column, getting the same data. Graphic representation of the relationships is in the attached image below.
What I want to achieve is when the Project is picked via combo box in PowerApps form, that the another combo box with Budget lines offers only items that are related to the chosen project (single choice in both cases). OK, easy, used "Depends on..." on Properties tab of the combo, and I got the following formula in its "Items" field
Filter('Budget line', Project:ID = ChosenProjectCombo.Selected.Id)
However, I got an error, showing the red tilde under the equation sign (you can see that in the image below - I have translated the list/column names in the text of this post for you to handle it with more ease) . I have checked the formula on existing posts on this forum and it seems that is valid.
What I doubt the origin of the problem is that when I unroll the data source "Budget line" to see its contents, I see only [Record] as lookup column data, not the values. Is there a solution to "dig down" through the data source to retrieve the values of the record?
You're my only help, thank you in advance!
Solved! Go to Solution.
Hi @valex ,
Is the "Project:ID" column a LookUp type in your 'Budget line' SP List?
Does the the "Project:ID" column in your 'Budget line' SP List reference values from the "ID" column in Project List?
Regarding the formula that you mentioned, I think there is something wrong with it. I have made a test on my side, please try the following workaround:
Set the Items property of the 'Budget line' ComboBox in your Edit form to following to following:
Filter(
Choices(Expenses.'Budget line'),
Value in Filter(
'Budget line',
Project:ID.Value = ChosenProjectCombo.Selected.Id
).Title
)
or
Filter(
Choices(Expenses.'Budget line'),
Value in Filter(
'Budget line',
Project.Value = ChosenProjectCombo.Selected.Value // use .Value rather than .Id
).Title
)
Please consider try above solution, check if it could help in your scenario.
Note: Please replace the data source name, field name in above formula with actual SP List name and Column names from your own side. The above formula is different from the solution @WarrenBelz provided.
Regards,
Hi @valex ,
I am flying a bit blind without seeing your data structure properly, but for a start try (you also had an extra bracket I have removed)
Filter(
'Budzetske pozicije',
Projekat_x003a_ID = Projekatlzbor.Selected.Id.Value
).Title
Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.
Thank you @WarrenBelz - I've tried already with the variations of picking column name behind the filter and not, but the result is the same, still red on equation and an error in formula. The screenshot with extra bracket was in one of hundred variations, thank you. What bothers me is that the formula was autogenerated by PowerApps "Depends on...", and it is valid when you use it between fields that have regular datasources (not nested lookup like in this case)...
Hi @valex ,
This should not be difficult to track down - you have two values - Projekat_x003a_ID in your list 'Budzetske pozicije' and you have a Combo Box / Drop-down called Projekatlzbor. I have realised that Projekat_x003a_ID is probably a Numeric field, so that will change my answer below and that this field is also a Record according to your screenshot. So try this
Filter(
'Budzetske pozicije',
Projekat_x003a_ID.Value = Value(Projekatlzbor.Selected.Id)
).Title
Note that Projekat_x003a_ID.Value may be different depending on the record structure.
Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.
That seems more logical then my formula, @WarrenBelz, thank you, and now there is no error. However, the dropdown produces no choices in production 😞
I have created plain numerical columns in my parent list and copied the ID's of Project and Budget line to them, then used the formula from my initial post here (with .Title at the end) and it worked. So definitely there is something strange happening with lookup fields...
@valex ,
Did you mention a lookup column? Try this
Filter(
'Budzetske pozicije',
Projekat_x003a_ID.Id = Value(Projekatlzbor.Selected.Id)
).Title
Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.
Hi @valex ,
Is the "Project:ID" column a LookUp type in your 'Budget line' SP List?
Does the the "Project:ID" column in your 'Budget line' SP List reference values from the "ID" column in Project List?
Regarding the formula that you mentioned, I think there is something wrong with it. I have made a test on my side, please try the following workaround:
Set the Items property of the 'Budget line' ComboBox in your Edit form to following to following:
Filter(
Choices(Expenses.'Budget line'),
Value in Filter(
'Budget line',
Project:ID.Value = ChosenProjectCombo.Selected.Id
).Title
)
or
Filter(
Choices(Expenses.'Budget line'),
Value in Filter(
'Budget line',
Project.Value = ChosenProjectCombo.Selected.Value // use .Value rather than .Id
).Title
)
Please consider try above solution, check if it could help in your scenario.
Note: Please replace the data source name, field name in above formula with actual SP List name and Column names from your own side. The above formula is different from the solution @WarrenBelz provided.
Regards,
@v-xida-msft, @WarrenBelz, thanks to both of you, guys - now this works like a charm and you saved my day 🙂 I thought that the problem was in lookup nesting and that I have to retrieve the parent of a parent like a table and then to filter it (showing items as [Record] and not values confused me), but it was all in proper syntax.
Dear @valex,
I have come across this issue too and your topic helped me understand my issue, although I do have to ask šta znači "budžetske pozicije"? 🙂
Have a great day!
-Ajdin
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