Old CDT vs New CDT

RE: Old CDT vs New CDT

ManuelHTG — Mon, 27 Apr 2020 13:55:15 GMT

You should check if you have dependents on the old CDT. Anyways, if you are adding a new column, I would really consider doing the modification on the old CDT and just use one CDT,

The DB is going to be affected in the same way, and replacing CDTs can be much more of a pain.

RE: Old CDT vs New CDT

Mike Schmitt — Mon, 27 Apr 2020 13:52:44 GMT

How similar was the new CDT's name to the old CDT name?

I've had many, many instances of building different (even just slightly different) CDTs pointing to the same table, each with their own entry in the Data Store as required, and never had an internal conflict like what you describe.

RE: Old CDT vs New CDT

naomi0001 — Mon, 27 Apr 2020 13:48:58 GMT

The old CDT had not been deleted anywhere. If the question is why did I create a new CDT, it was so that I wouldn't have to do any kind of production deployment before I was ready. This was a POC, experimental. I didn't alter the original CDT because I didn't want to change the dependents. No, there were no changes made in production, either directly or through approved channels. This has occurred in a development environment.

RE: Old CDT vs New CDT

ManuelHTG — Mon, 27 Apr 2020 13:43:36 GMT

why would you do that? Did you do the changes in PRD directly? did you delete the old cdt or check the dependents on it?