Skip to main content
Closed

Automatic data conversion on rename of column

Related products:Software Factory
Kevin Horst
Diederik van Duuren
Harm Horstman
+10
  • Andre te Raa
  • Kevin Horst
    Kevin Horst
  • Diederik van Duuren
    Diederik van Duuren
  • Vincent Doppenberg
  • Harm Horstman
    Harm Horstman
  • Robbert van Tongeren
    Robbert van Tongeren
  • Benjamin Westra
  • John Lunenburg
    John Lunenburg
  • Geurt
    Geurt
  • John Sangers
    John Sangers
  • Arie V
    Arie V
  • Martin
  • Jochem Pieper
    Jochem Pieper
  • Tejo van de Bor
    Tejo van de Bor
  • Eric F
    Eric F

When renaming a column the column is treated as a new column. Meaning it will get the default value and not the old value of the previous column. To make the rename complete you have to also setup the data conversion to the old column. Please make the data conversion automatic (set the old column) on a rename since this is the expected behavior of a rename action. 

Did this topic help you find an answer to your question?

10 replies

Arjan Sollie
Thinkwise blogger
Forum|alt.badge.img+14
  • Thinkwise blogger
  • 85 replies
  • September 22, 2020

I also believe that when you specifically use the rename column task, it should also set up a data conversion for that column.


Robbert van Tongeren
Thinkwise blogger

I just realize I had the same problem.

For me the problem occurred when I created a new project version and did not generate the definitions.
When I created the project version and renamed a column, then generated the definition it did not create a correct record in the data conversion.
But when I created a new project version and then generate the definition before renaming the column it seemed to work.

Could you verify this?


Forum|alt.badge.img+17
  • Author
  • Moderator
  • 777 replies
  • September 22, 2020
Robbert van Tongeren :

I just realize I had the same problem.

For me the problem occurred when I created a new project version and did not generate the definitions.
When I created the project version and renamed a column, then generated the definition it did not create a correct record in the data conversion.
But when I created a new project version and then generate the definition before renaming the column it seemed to work.

Could you verify this?

Robert this is correct. I guess this would make this a bug instead of a wish.


Jasper
Superhero
  • 678 replies
  • October 14, 2020

Hi Erwin,

 

Please report a bug for this if you haven't done so already. I will close this idea.


Blommetje
Forum|alt.badge.img+13
  • Partner
  • 210 replies
  • May 13, 2022

Is this still an issue? Sometimes I have this issue. Can’t really pinpoint when. 


Mark Jongeling
Administrator
Forum|alt.badge.img+23
Blommetje :

Is this still an issue? Sometimes I have this issue. Can’t really pinpoint when. 

When you do not generate the definition after going to a new project version, the Software Factory fails to add Data conversion data when renaming objects. So, to avoid this, please generate definitions after creating a new project version.


Forum|alt.badge.img+17
  • Author
  • Moderator
  • 777 replies
  • May 16, 2022
Blommetje :

Is this still an issue? Sometimes I have this issue. Can’t really pinpoint when. 

 
There is an issue if you rename both the table and column within that same table. I reported this for the development team to investigate. 

 


Robert Jan de Nie
Thinkwise blogger
Forum|alt.badge.img+6
Mark Jongeling :
Blommetje :

Is this still an issue? Sometimes I have this issue. Can’t really pinpoint when. 

When you do not generate the definition after going to a new project version, the Software Factory fails to add Data conversion data when renaming objects. So, to avoid this, please generate definitions after creating a new project version.

Why does a user have to do this, if it is a given that this needs to happen, why not just schedule one in the background?


Mark Jongeling
Administrator
Forum|alt.badge.img+23
Robert Jan de Nie :
Mark Jongeling :
Blommetje :

Is this still an issue? Sometimes I have this issue. Can’t really pinpoint when. 

When you do not generate the definition after going to a new project version, the Software Factory fails to add Data conversion data when renaming objects. So, to avoid this, please generate definitions after creating a new project version.

Why does a user have to do this, if it is a given that this needs to happen, why not just schedule one in the background?

Well, from the 2022.2, it will 😉

At the end of the copy project version task, a Generate Definition will be automatically scheduled.


Robert Jan de Nie
Thinkwise blogger
Forum|alt.badge.img+6
Mark Jongeling :
Robert Jan de Nie :
Mark Jongeling :
Blommetje :

Is this still an issue? Sometimes I have this issue. Can’t really pinpoint when. 

When you do not generate the definition after going to a new project version, the Software Factory fails to add Data conversion data when renaming objects. So, to avoid this, please generate definitions after creating a new project version.

Why does a user have to do this, if it is a given that this needs to happen, why not just schedule one in the background?

Well, from the 2022.2, it will 😉

At the end of the copy project version task, a Generate Definition will be automatically scheduled.

I love it when I propose something and you guys have already thought of it. <3



Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings