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 / Powerapp components ta...
Power Apps
Unanswered

Powerapp components table parameters column mapping schema corrupted

(0) ShareShare
ReportReport
Posted on by 502

Having worked with components for over a year now, I keep having issues where the component mapping schema for a table gets corrupted. Basically, the component doesn't respect the column names in the input table and will sporadically change the mapping so that the columns are incorrect.

IE if I have a table in the component input parameter like this:

Table({Col1:"col1 value", Col2:"col2 value"})

then in the powerapp where I have the instance of the component, I have that same table as the input, and I show that in a datatable, I'd expect to see:

Col1                  Col2

col1 value         col2 value

 

but it's really common for components to do this:

Col1                  Col2

col2 value         col1 value

 

It's been that way ever since I started with components, well over a year. any word on when Microsoft might address this bug?

Categories:
  • RandyHayes Profile Picture
    76,299 Super User 2024 Season 1 on at

    @dave-jorgensen 

    Yep...see this on a pretty regular basis.  It's pretty annoying and has been like this since the start.

    I find that if I change the schema on the component to add a dummy column to it and then take it out, it magically re-evaluates the schema properly.

    Don't forget...changing the schema formula on your component table property will wipe out that property in ALL instances of your component in the app...so venture cautiously in case you have a lot of customizations in those properties.

     

    I hope this is helpful for you.

  • dave-jorgensen Profile Picture
    502 on at

    yes, for sure, that works because it forces out a new schema. Other thing I've found that works is, in the instance where you use the component in the app, remove all the columns and add them back into the table 1 at a time, in the order they are supposed to be in the table. Prevents pushing out new schema (which as you know, overwrites the input of ALL instances). But would be great if we could get it fixed.

  • RandyHayes Profile Picture
    76,299 Super User 2024 Season 1 on at

    @dave-jorgensen 

    Totally agree!!!  Components were once considered experimental...now they are considered a feature - I still believe they are experimental or they would not have these issues...PLUS, they would not share a variable across all instances 😕

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 Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Leaderboard > Power Apps

#1
11manish Profile Picture

11manish 432 Super User 2026 Season 2

#2
Mohsin Ali Profile Picture

Mohsin Ali 347

#3
WarrenBelz Profile Picture

WarrenBelz 254 Most Valuable Professional

Last 30 days Overall leaderboard