Answered

Access to Dataverse Table in Component Using Custom Properties?

(0) Share

Report

Posted on by Kobaek

I am trying to create component with gallery and text fields for browsing and editing data which is in a Dataverse table.

For the component I have defined a custom property of the type, "Table".

The parameter has default value, Table({Name: "TestName}), as dummy content.

Using the parameter inside the component works fine. I can also create input from the app using the component such as Table({Name: "NewTestName"}).

However, I can't seem to figure out how to correctly pass a table from dataverse.

I am simply providing the table name (also added to the App) into the custom property in the component included in the App.

Error message: "The record passed in has none of the expected fields: Name".

The table in Dataverse does have a column called "Name" (and additionally all of the automatically create columns).

Any ideas about what I am missing here?

Categories:

Building Power Apps

I have the same question (0)

All responses (4)

Answers (1)

Michael E. Gernaey 53,928 Super User 2025 Season 2 on at

Like (0)

Report
Copy link

Link copied!

Hello,

Here is your issue.

When you create an Input Property on a Component, you have to define what the schema looks like of the record / table or technically you can put {} which is { and } without a space (its just me lol), or for a Table you can put
Table({})

But can you show me what you defined in the Input Property definition? or just try Table({}) where some tables may work properly this way

It will not just automap fields to fields it has no way to know what to map and what to leave out. So think of it as passing only what you need. So alot of times peope pass a collection of data versus a "Database Table" because Table in the input property does not equal a Table in database. Its just a table structure.

Cheers
If you like my answer, please Mark it as Resolved, and give it a thumbs up, so it can help others
Thank You
Michael Gernaey MCT | MCSE | Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey

Was this reply helpful? Yes No
Michael E. Gernaey 53,928 Super User 2025 Season 2 on at

Like (0)

Report
Copy link

Link copied!

I do want to add though if you just pass Table({}) you are going to pass lots of other metadata etc that you may not need. Its better if you can to reduce to whatever fields you need, just as a normal.

I am assuming you have not turned on App Access Context, hence why you cannot see the Table directly in the component.
Cheers
If you like my answer, please Mark it as Resolved, and give it a thumbs up, so it can help others
Thank You
Michael Gernaey MCT | MCSE | Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey

Was this reply helpful? Yes No
Kobaek 13 on at

Like (0)

Report
Copy link

Link copied!

Thank you for the reply.

Ok, does that mean it is not possible to pass a reference to a Dataverse table into a component?
Instead it is "only" passing in-memory tables (as it would be with a Collection)?
Is this understanding correct?

I am building a model-based app and working on a Canvas App in a custom page, and in this case I do not see an option for creating components, and I am therefore using Component Library, which does not have the option for enabling Application access.
Please also correct me if you think some of this is misunderstood 🙂

I might have other options than I have understood so far, but right now it seems to me that I maybe should consider creating a standalone Canvas App instead and create application scope components instead.
The reason is, that I am trying to create a few standard components which I envision to use with different configurations and for editing/viewing different sets of data (dataverse tables) in the same application.

Was this reply helpful? Yes No
Verified answer

Michael E. Gernaey 53,928 Super User 2025 Season 2 on at

Like (1)

Report
Copy link

Link copied!

The short answer is Yes, its not really intended to do that.

Because in your component, you want to access things by saying things like First(myTable).Name but you cannot do that because it doesn't know how to figure out a property name at design time because you haven't defined it in the schema.

Then if you do define the schema, then how do you set the properties without looping through the table to set the property.

So yes you can pass tables, its just that you have to use a ForAll or Collection to satisfy the schema.

Does that make sense?
Cheers
If you like my answer, please Mark it as Resolved, and give it a thumbs up, so it can help others
Thank You
Michael Gernaey MCT | MCSE | Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey

Was this reply helpful? Yes No