web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Campo “Responsável pel...
Power Apps
Suggested Answer

Campo “Responsável pela Análise” não aparece na view, mas está preenchido no formulário

(0) ShareShare
ReportReport
Posted on by

Estou enfrentando um problema em um app model-driven no Power Apps (Dataverse).

Tenho um campo chamado “Responsável pela Análise” (lookup de usuário).

 
  • No formulário, o campo está preenchido corretamente.

  • Porém, na view (lista inicial), essa coluna aparece em branco.
 

Detalhes:

 
  • Existe apenas um único campo com esse nome (não é campo duplicado)

  • Outros campos de responsável (ex: “Responsável pelo Suporte”) aparecem normalmente na mesma view

  • Já removi e adicionei novamente a coluna na view, mas o problema continua

  • A app e a tabela já foram publicadas


  •  

Alguém já passou por isso ou sabe o que pode causar esse comportamento?

Captura de tela 2026-06-19 095921.png
Categories:
I have the same question (0)
  • Suggested answer
    Assisted by AI
    Sunil Kumar Pashikanti Profile Picture
    2,211 Moderator on at

    This is a known behavior with Dataverse lookups. If a value populates correctly on the main form but appears blank within a system view, it typically comes down to one of these core issues:

    Security Restrictions: This is the most common cause. If the running user lacks Read permissions on the targeted table (in this case, the User table), or if Column-Level Security is enabled on that specific lookup field, the grid engine will mask the data and display it as blank.
     
    A View is essentially a SQL-like join. To display a lookup column in a grid, the view engine has to look at your main table, follow the lookup relationship, and pull the "Primary Name" from the other table. If the user's security role lacks Read access to that secondary table, the system will still let them see the main rows in the view, but the grid engine will silently fail to pull the related name, leaving just that specific column completely blank.

    Field Mismatch in the View Canvas: Double-check that the view is referencing the exact same schema name as the form field. If a field was ever recreated, renamed, or duplicated with similar display names, the view might simply be pointing to a different, unpopulated column.

    Primary Name Column Resolution: Dataverse views display the value stored in the Primary Name column of the lookup's target record. If the targeted record has an empty or unpopulated primary text field, the lookup column in the view will have no string to display and will appear empty.

    Asynchronous Caching: Occasionally, metadata changes do not immediately sync to the grid rendering engine. Try performing a "Publish All Customizations" in your solution, then clear your browser cache or test in a private browsing window.

    Since your other lookup fields are rendering correctly, start by verifying your security roles and read access boundaries on the target table.
     
    ✅ If one of the responses here solved your issue, please mark it as Accepted so others facing the same problem can benefit as well.
    👍 If this or any other reply here helped you, feel free to give it a Like. It helps others and is always appreciated.

    Sunil Kumar Pashikanti, Moderator
    Blog: https://sunilpashikanti.com/posts/
  • Suggested answer
    11manish Profile Picture
    3,052 on at
    Since:
    • The field displays correctly on the form.
    • Other user lookup fields display correctly in the same view.
    • Re-adding the column didn't help.
    The most likely causes are:
    • Field Security enabled on that specific lookup field.
    • View metadata corruption (test with a brand-new view).
    • The view is referencing a different column than the one shown on the form.
    As a quick test, create a brand-new personal or system view with only that lookup column and see whether the value appears. That result will usually pinpoint
     
    whether the issue is with the field itself or the existing view definition.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
Valantis Profile Picture

Valantis 481

#2
WarrenBelz Profile Picture

WarrenBelz 379 Most Valuable Professional

#3
11manish Profile Picture

11manish 291

Last 30 days Overall leaderboard