I added a select column to my BAQ. I used the Kinetic Application Studio to add the new column to my grid and data form in my current layer in my sandbox environment. Somehow, I made a mistake and now I see the database name (tablename.columnname) for the grid title. I tried removing the grid from the grid columns. But that column still appears when I preview the current layer; eventhough, it’s no longer in the column list. The orphan column does not exist in the BAQ select clause. Even worst is that that column appears in a previous layer.
I have a working, clean example of the code in our production instance, so I tried creating a solution that included the BAQ, Dashboard and Menu and tried installing them into our sandbox where I’ve been working, but the orphan column is still there.
Is this a problem that can be fixed in Application Studio or must I use the Classic Editor? How can I fix this?
Next to the Ship Date column which was connected to [InvcDtl_ShipDate] I had another column that had the title “InvcDtl.ShipDate” which wasn’t in the grid’s list of column.
Through some experimentation, I found that placing the name “InvcDtl.ShipDate” in the Hide Columns removing the unwanted coulmn. That was about an hour ago.
I just saw your request and thought I should try to show you the bad column, so I emptied the Hide Columns and Previewed the screen again. I don’t understand what happend, but the unwanted column (what I was calling an orphaned column) do longer appears.
