25R2 Delivery continuity changes

It is possible, at least it was for me.

However, I noticed a slightly different behavior if the Entity was created AFTER 25R2 for some reason.

So for instance, entity RequestTask was added in 25R2. I’ve customized (added) a couple custom fields to it, but doing the regular CDB changes to add the fields would “work” during development (i.e. direct execution from Studio Developer), but it would fail during delivery, because during delivery it seems like it was trying to recreate the Request_Task_Tab table, which it’s not supposed to.

So for “newly released” entities, I had to make sure my CDB was using the new ‘#’ to add fields, i.e.:

For fields added to “older” entities (entities released by IFS before 25R2), I didn’t change my CDBs, and got zero issue during either development (direct execution) or during delivery build

For fully customized entities added before 25R2, I just had to add the Prepare_For_EBR command to the CDBs at the end

Although for  adding a new custom entity post 25R2 I would absolutely recommend using the new ‘#’ methods too)

If you do have the time and inclination though, I’d definitely recommend using the .ddlsource files instead, so that your customers would be “ready” for Delivery Continuity if they ever became a DC Customer. Even if you are NOT a DC customer, nothing stops you from being DC-Ready, if that makes sense :)

In short however, yes, it is possible to retain your CDBs, you just want to:

1. Prepare fully custom entities for EBR in their CDBs if they are older entities
2. You don’t need to do anything if they’re just fields added to older entities
3. You can still use CDBs but with the EBR Methods (#) for either new Cust Entities post 25R2 or adding fields to Core entities that were added Post 25R2
4. Generally speaking, you really want to use the EBR Methods for any new customization work undertaken post 25R2, basically, but the system is backwards compatible as long as you prepare your custom entities for EBR in your existing CDBs