Enhance the Export/Import Mechanism to not import un-used columns by the app been imported

Product Suggestions
1

I have observed that when migrating new applications form a development instance to QA and then to PROD, the Export/Import mechanism copies columns that are not being used by the app being imported. This led to have unused columns from other apps that were in-progress on QA and PROD instances.

It would be great if the Export/Import mechanism be revised to assure that only columns that are being used on the app are the ones that gets created.

2

Hi @ecarpena, thank you for the post. Could you share more about the un-used columns? Are these columns in a table used by multiple apps, and therefore you would like only specific columns to be imported, such as ones used by only a specific app?