Misleading suggestions when updating table schema

What up bro I have a large fact table with many partitions that have had a new column added recently. For all historic partitions this column will remain empty (as we do not have the historic records). For any rows in partitions going forward, the column will be populated. We do not ever plan to reprocess the historic partitions. However, when updating the table schema, the new column is not recognized as present (which it is, but only in the most recent partition), and Tabular Editor suggests to remove it. This also happens when the update table schema function is executed by right-clicking on the new partition. See image: Could you make it so that update table schema takes all partition definitions into account when using it on the table level? And if using it on a specific partition, then suggest based on the content of that partition? - Suggest appropriate actions when updating table schema on existing facts based on context in which it is used Alternative solution: Can easily be worked around by adding the column manually