This behavior usually comes down to how relationships and data are actually linked in Microsoft Dataverse when building views in Power Apps.
What’s happening
Even though you’re able to:
- Add columns from the related table
- Configure the relationship
The view will only show data if records are actually related at the data level.
So if your new relationship columns are blank, it typically means:
There is no matching related record for those rows.
Why the existing one works
The working relationship already has:
- Proper lookup values populated
- Matching parent-child records
Your new relationship may be:
- Correctly configured
- But not populated with data yet
Things to check
✔ 1. Verify lookup values
Go to a record in your main table and check:
- Is the new lookup field populated?
- Does it point to a valid record?
If it’s empty → the view will show blank.
✔ 2. Confirm relationship type
Make sure the relationship is:
- Correct (1:N or N:1 as expected)
- Using the correct lookup column
Even if properties “look the same,” the actual lookup field used matters.
✔ 3. Check data consistency
Open both tables and confirm:
- Records exist in the related table
- They are properly linked via the lookup
✔ 4. Re-add columns after relationship change
Sometimes the designer caches metadata:
- Remove the related columns
- Save & publish
- Add them again
✔ 5. Publish all customizations
After changes:
- Click Publish All Customizations
- Refresh the app
Common gotcha
Just creating or editing a relationship does not backfill existing data.
So even if:
- Relationship = correct
- Columns = visible
Data will still be blank until records are linked.
Summary
- View shows data only when records are actually related
- Most likely cause: lookup field is not populated
- Fix by ensuring proper data linkage between tables
If this resolves your issue, please mark the answer as accepted and give it a like. It helps others in the community and supports knowledge sharing. Thanks!
