Unanswered

Mapping all Data Fields to their Data Source or table

(0) Share

Report

Posted on by bkatz

Apologies if this has been asked previously but I have not been able to find anything on this.

I have an application which has multiple data sources, SQL, onedrive/excel, sharepoint, etc. I want to know if there is a way to export the schema to see for every field if there is a datasource what it is? I want to make sure I don't have any redundancies and be able to delete columns from tables that aren't being used so it is as clean as possible of a backend. I look up names by unique IDs of locations and pair it with location names in another table, phone numbers from another table, etc.

Ideally I'd like to print or save this schema so that I have it in case of a loss or in case something gets deleted or changed in the future I can have it as a reference.

Is this possible?

Thank you in advance.

Categories:

Building Power Apps

I have the same question (0)

All responses (2)

Answers (0)

v-jefferni on at

Like (0)

Report

Hi @bkatz ,

I'm afraid there is no way to achieve that need in Power Apps currently. It is not a good idea to reduce columns from data sources if it is a production App. Logically, you have tables firstly to store all data that you need, then create the App that connects to the tables as data sources to show off the view and interface to users and for them to interact with the data sources. The App is the "tool" for interaction, the tables are the basis. If you don't need a column in a table, it should not be needed in the App as well.

Hope this helps.

Best regards,

Community Support Team _ Jeffer Ni
If this post helps, then please consider Accept it as the solution to help the other members find it.

Was this reply helpful? Yes No
bkatz 36 on at

Like (0)

Report

I understand what you are saying but in this case I don't entirely agree. I have existing SQL tables with lots of columns on them and in some cases they are redundant to each other. For example Table1 has store name, address, phone number, unique ID (key) and an existing Table 2 has store name, address, email addresses, unique ID. As I clean up the tables, I can drop store name from one of the table to avoid having to update both each time I make a change. But if I can't see which table (1 or 2) I'm pulling the store name (in some kind of list) I don't know which one can be deleted. To your point once I determine which columns are not connected to any field in the application I could delete them entirely (that is my plan) but to get there a map of app fields to data souce fields would make for a much simpler process. Does that make sense?

Was this reply helpful? Yes No