Skip to main content
Question

Delivery Creation Failed - 24R2 Release Update

  • December 19, 2024
  • 4 replies
  • 182 views

Forum|alt.badge.img+2

Hello All,

 

We are currently in the process of upgrading from 23.1.11 to 24.2.0 through the Release Update Studio. We successfully uplifted the customizations, and the creation of the topic environment and the sanity build were both successful. However, the delivery creation failed due to errors in the standard objects.
We have checked the log file and could see that there are numerous errors related to deploying standard core views/packages, even though the customizations have not impacted this area. We tried to deploy one of the errored standard API from Developer Studio by connecting to DEL env, and it got successfully deployed to database without any error (refer screenshot).

Interestingly, the creation of TOPIC environments from the Release Update Studio was successful, and the sanity build performed just before the failed delivery creation also succeeded. Therefore, the delivery creation should have been successful, as it theoretically uses the same code from the repository.

We are also unable to find an option to delete the DEL environment in order to recreate the Delivery Creation step.

Has anybody experienced similar issues? or do you have any idea what could be the cause?

I would appreciate any suggestion.

 

Regards,

Manisha

4 replies

Forum|alt.badge.img+2
  • Do Gooder (Customer)
  • 8 replies
  • April 8, 2025

Hi

We have the same/similar issue.  The topic and sanity builds went through successfully but the delivery has failed.  The errors relate to a developed table not creating properly and then a cascade effect by the looks of it.  Wondered if you had had a resolution that we could try?

Thanks Jay


Forum|alt.badge.img
  • Do Gooder (Partner)
  • 2 replies
  • May 14, 2025

Hi ​@AccManisC and ​@ZYBJAYH,

Was the issue solved in your release update?

I am facing the similar issue with 24R2 Order Delivery step. It failed with GENLED BI meta data import step which are IFS Core files. It seems like codes are ok, but it keeps failing. I Would like to know what went wrong in your cases and how it was solved?

 

Thank you in advance 

Dilan


Forum|alt.badge.img+2
  • Do Gooder (Customer)
  • 8 replies
  • May 14, 2025

Hi Dilan

What was causing our issue was a piece of developed code that was being loaded before the module it related to was trying to refer to it.  We got around this by moving the code into the custom layer which loaded after the core module it referred to.  Managed to do this in DevOps with a cut and paste.

After that, the delivery went straight through and has now been deployed, and more importantly it works.

The developed code was to define a new table, after that there was a ripple effect when the views that were being created in the core module where failing to ‘referencing view/column’ with similar errors to yours.

Hope that is of some help?

Thanks Jay


Forum|alt.badge.img
  • Do Gooder (Partner)
  • 2 replies
  • May 14, 2025
ZYBJAYH wrote:

Hi Dilan

What was causing our issue was a piece of developed code that was being loaded before the module it related to was trying to refer to it.  We got around this by moving the code into the custom layer which loaded after the core module it referred to.  Managed to do this in DevOps with a cut and paste.

After that, the delivery went straight through and has now been deployed, and more importantly it works.

The developed code was to define a new table, after that there was a ripple effect when the views that were being created in the core module where failing to ‘referencing view/column’ with similar errors to yours.

Hope that is of some help?

Thanks Jay


Hi Jay,


I appreciate your quick response. The developed code you're referring to is a customization, if I understand you correctly?

In my scenario, the customer solution is pretty standard; there is only 1 customized report in the work order module. The errors in the ‘Order Delivery’ step is referring to the GENLED module, which is untouched for this customer. FYI We are upgrading from 22R2 to 24R2.

Thank You

Dilan


Reply


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