Skip to main content
Solved

During deployment Column isnt deployed making the check script fail

  • November 4, 2024
  • 2 replies
  • 40 views

Dennis1690
Vanguard
Forum|alt.badge.img+4

As the title states, im running a deployment in which a column should be added to the upgrade script. However it doesnt upgrade the table with the new column. This results in a failed deployment.

What I did:

Validate, Run full creation and smoke test my development enviroment. I made sure the column exists and works.

Validate and check my Full create script in development. This contains the new column.

Set the correct SF_model_info

Deployment package

run the deployment.

 

Added the log for reference. Thanks in advance

Best answer by Dennis1690

Thanks for your response. 

 

I solved it by restoring a database and going a few deployments back. It happened earlier in the proces.

View original
Did this topic help you find an answer to your question?
This topic has been closed for replies.

2 replies

Ester
Moderator
Forum|alt.badge.img+5
  • Moderator
  • 59 replies
  • November 5, 2024

Hey Dennis,

Some steps that might help:

  • Open Data > Data migration. Does your column appear there as changed?
  • Open Model Overview > Branches > Form > Data migration and upgrade. Does the version that is listed here, indeed does not have this column?
  • Open the script ...\2.50.4\Deploy\Upgrade\2.50.4\020_Upgrade.sql of the package, does this has the upgrade?
  • One dummy-proof question, Does the column still exist? It is not generated or deleted during generation or something. 

If the column exists in data migration as changed, but not in the script, please create a ticket in TCP, because that might be an SF-issue. 

If the column does not exist in data migration, the version you upgrade from might be wrong. Try the task “Set source for data migration and upgrade”. If that does not work, the column did not exist in that version and does exist in the current branch, please also create a ticket so we can look further into this situation.

Please, let me know if this helped and what the problem was. 


Dennis1690
Vanguard
Forum|alt.badge.img+4
  • Author
  • Vanguard
  • 25 replies
  • Answer
  • November 6, 2024

Thanks for your response. 

 

I solved it by restoring a database and going a few deployments back. It happened earlier in the proces.


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