You’re offline. This is a read only version of the page.
42
I have 2 Dataverse tables with a n:1 Relationship:
Table "Wohn-Einheit" is connected with table "Bau-Projekt" through a LookUp Column called: "Projekt".
In my App i have 2 Comboboxes:
Items:
Share
Report'Wohn-Einheiten'
Filter('Bau-Projekte'; Projekt = EinheitCombobox.Selected.Projekt.Projekt)
The problem now is, that the Values of the LookUp are all Empty.
Here i'm comparing GUID's but also if i comparing Projektnumbers in Text-Format it isn't working...
I also tried it with a variable and the OnChange Action but this is also not working...
What am i doing wrong?
Anyone has a idea? Thank you!
No problem - glad it was resolved!
I finaly got a solution for this:
PowerApps was very buggy and like i said, it gave me the Record but without any data in the other columns.
My workaround was now, that i declared a variable in OnChange which will LookUp the selected Record with the GUID (Which was the only column, beside the displayed column of the Combobox).
But thank you for your help! Appreciate it 🙂
I think it could be a feature - I don't know what the lookup function does behind the scenes, but traditionally, it literally functions as a search through all the entries. If you disable the ability to search, then you aren't able to use a lookup. Does that make sense?
Hi Developingteal,
i finaly got the real issue here, why the Combobox.selected can't access the LookUp Column.
The IsSearchable switched back to false, for it's own... so after i saw that the combobox isn't searchable anymore, i set it to true and the combobox had the weird behaving again.
So it's because the IsSearchable = true Combobox. When i set the IsSearchable = false it's working totaly fine.
Do you have a idea, why this is or is this a power apps bug? The best way for me is to use the Searchable function 🙂
Thank you!
Yeah I would definitely look for a workaround with the n:1 relationship. That is kind of a theme with powerapps that certain functionalities typical of an typical coded app really don't exist or are not possible.
Your main app could be offline useable, but I am not really certain so don't take my word for it.
Also mark as solution what worked for you or give a kudos to something that helped you out.
No way, you're right!
I looked again today on my Test-App, didn't made any changes, and today it's working?!
But unfortunatly for my Main App, there was no miraculous healing for this Issue with n:1 relation.
Maybe it's better to look for a work around, to be able to get to the same result with a different approach 🙂
Do you think it can also be that my main App is offline useable?
Do you happen to have an idea?
Thank you!
sometimes apps has a delay with processing things, so maybe take some time and look at it tomorrow. I think it could be an issue too with that relationship you are describing, power apps typically does not like n:1 and I don't think I have ever gotten an n:1 to work - hence if you have some way to flip it, it might be able to handle it.
Hi Developingteal,
thanks for your reply. The rows are existing.
For example, if i turn it around (Filter "Wohn-Einheiten" based on "Bau-Projekt"), it's working:
All responses (
Answers (
Filter('Wohn-Einheiten'; Projekt.Projekt = ProjektCombobox.Selected.Projekt)
And after i saw that this is working, i compared the 2 relationships and saw nothing suspicious; Quite the opposite, the settings of the 2 relationships are totaly the same, except for that the one is 1:n and the other n:1 .
Im totaly confused. Because i used this type of code in another App and it worked till yesterday and now im confused why. Ended up opened this completely new App and tried this with a other tables and as you can see, it's not working and i don't know, what to do next...
First, I would verify if the rows you are looking for do actually exist. The next step would be to verify the relationships, etc. I don't see anything in particular that seems wrong, just verify that everything does actually exist, as it seems to not give you any error messages, so your code is correct, it is just there is missing access or a relationship.
#1
WarrenBelz
146,658
Most Valuable Professional
#2
RandyHayes
76,287
Super User 2024 Season 1
#3
Pstork1
65,999
Most Valuable Professional
