Component Record Output Property Incomplete?

(1) Share

Report

Posted on by BenKraft

154

I have an "app scope" component that has an output property "Employee" of type record.

It currently returns a record from a Dataverse table within the app based on a text entry field that is contained within the component:

I expected that this would return the full record from the table, but in reality, it returns only a few select fields:

Where are the rest of the fields? Even the primary column is not included.

Categories:

Building Power Apps

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (9)

Answers (0)

Sort by

BenKraft 154 on at

Like (0)

Report
Copy link

Link copied!

I was thinking that this behavior possibly operates like variable casting where the fields aren't populated unless they're used by the app but that doesn't seem to be true; if I try to reference the other fields within the app, they remain blank.

Was this reply helpful? Yes No
Suggested answer

Haque 1,691 on at

Like (0)

Report
Copy link

Link copied!
Hi @BenKraft

The reason:

Power Apps does not automatically return all fields from a Dataverse record when you retrieve it inside a component. It returns a "lightweight" record instead containing only a limited set of fields, often just the primary key and a few default fields.

I barely know one reason (may be there are many - I need to navigate) why this behaviour: Power Apps optimizes data retrieval by returning only a subset of fields unless explicitly requested.

Explicitly specify all fields you want to return inside the component before assigning to the output property. For example:

// Instead of just LookUp(DataverseTable, TextField = TextInput.Text) LookUp( DataverseTable, TextField = TextInput.Text, { Field1: Field1, Field2: Field2, Field3: Field3, PrimaryField: PrimaryField, // add all other fields you need here } )

Use ShowColumns to specify the exact columns to retrieve:

LookUp( ShowColumns(DataverseTable, "Field1", "Field2", "Field3", "PrimaryField"), TextField = TextInput.Text )

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No
BenKraft 154 on at

Like (1)

Report
Copy link

Link copied!

@Haque Thanks for the response!

I was hoping that was not the case :/

I had tried a similar thing using With() to cast the record type within the output property, but I wasn't aware you're able to do that all within LookUp(), that's not even in the documentation!

I might take that approach, but it's disappointing that I have to specify all the fields in the whole table (I want to use the record for a lookup field in another table) without using a user-defined function to do something like another lookup based on the GUID.

Is there a minimum number of fields required for a record to be correctly interpreted by a patch function as a valid lookup object? I.e. if I want to Patch my found "Employee" to a Employee lookup field in another table.

I assume I need at least the GUID but it seems like it requires more than that:

Do I need to just keep adding the fields it says are missing until it works?

Was this reply helpful? Yes No
Suggested answer

Kalathiya 1,717 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Hello @BenKraft,

Please try this, I don’t think we need to specify all the column names in the LookUp function

Please try below formula:

LookUp('Watertown - Employees', 'Badge Number' = BadgeNumberInput.Text)

If this response resolves your issue, please mark it as the Verified Answer so it can help other community members as well.

---------------------------------------------------------------------------------

📩 Need more help? Just mention @Kalathiya and I’ll be happy to assist.

✔️ If this answer helped you, please tick “Does this answer your question?” so it can be marked as the Verified Answer.

💛 A Like always motivates me to keep contributing!

Was this reply helpful? Yes No
BenKraft 154 on at

Like (1)

Report
Copy link

Link copied!

@Kalathiya

That is the exact query I have in my original question that does not work.

Was this reply helpful? Yes No
Kalathiya 1,717 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Hello @BenKraft,

Try below approach:

First(Filter('Watertown - Employees', 'Badge Number' = BadgeNumberInput.Text))

If this response resolves your issue, please mark it as the Verified Answer so it can help other community members as well.

Was this reply helpful? Yes No
Suggested answer

Haque 1,691 on at

Like (0)

Report
Copy link

Link copied!
Hello @BenKraft,

For the Patch function, when we want to update a lookup field (such as an Employee lookup in another table), the minimum required fields in the record we pass are typically:

The Id field (the unique identifier of the record in the lookup table).

The Value field (the display name or primary column of the lookup record).

Nonte: This is the standard shape for a lookup object in SharePoint and Dataverse when patching:

Patch( TargetTable, Defaults(TargetTable), { EmployeeLookupField: { Id: EmployeeRecord.Id, Value: EmployeeRecord.PrimaryFieldName } } )

Note: If you only provide the Id without the Value, the patch may succeed but the UI might not display the lookup text correctly until refreshed.

We do not need to keep adding all missing fields one by one. Instead, you must ensure the record you pass to the lookup field has at least these two fields:

{ Id: EmployeeRecord.Id, Value: EmployeeRecord.PrimaryFieldName }

So, you don’t need to add all missing fields—just ensure you include the GUID (id) and the primary display field in the record you patch.

Was this reply helpful? Yes No
BenKraft 154 on at

Like (1)

Report
Copy link

Link copied!

@Haque I know something like that works for SharePoint, but I'm fairly certain that will not work for Dataverse:

Was this reply helpful? Yes No
Suggested answer

Haque 1,691 on at

Like (0)

Report
Copy link

Link copied!
Hi@BenKraft

If you already have the GUID of the related record, for an example:

Patch( Contacts, Defaults(Contacts), { firstname: "Jane", lastname: "Smith", accountid: { '@odata.type': "Microsoft.Dynamics.CRM.account", accountid: GUID("11111111-2222-3333-4444-555555555555") } } )

Note: The @odata.type metadata specifying the entity type.

So in you case, the following can be a try:

Patch( TargetTable, Defaults(TargetTable), { EmployeeLookupField: { '@odata.type': "#Microsoft.Dynamics.CRM.employee", // entity logical name with correct casing Id: EmployeeRecord.Id } } )

However, I see a different erro in your screen shot:

Invalid argument type. Expecting a record value, but of a difference schema.
Missing column. Your formula is missing a column 'Owner' with a type of 'Polymorphic'.

You can avoid that, you need to patch it witha a record like this:

Owner: { '@odata.type': "#Microsoft.Dynamics.CRM.systemuser", // or "#Microsoft.Dynamics.CRM.team" if assigning to a team Id: User().Email // or the GUID of the user/team you want to assign ownership to }

Was this reply helpful? Yes No