Skip to main content

Hello @Nonprofit Success Pack​!!!

 

So I have a few thoughts about something I just discovered regarding TDTM. 😐

 

My dev team and I just discovered that the the TDTM "config" on Trigger Handlers records present in our Production and Full Sandbox orgs is NOT mirrored on Partial Copy, Developer Pro and Developer Sandboxes. Which means that if Trigger Handler records are "inactivate" in Production and a new Developer Sandbox is spun up to work on let's say development enhancements around NPSP Address Management improvements based on the assumption that they are "inactive" then we would find ourselves in a little bit of a pickle.

 

Should we have known/remembered that Trigger Handler records are records and due to the nature of Developer Sandboxes coming with ZERO records? Yes we should have. Does the note on this piece of documention help? Yes it does, but with that said I have a couple of ideas/thoughts. It is possible that some of these are already being worked on or other, but wanted to share with community see what others have to contribute. 🙂 #Forward Looking Statement.​

 

  1. Could I recommend that on top of the note on the Manage Trigger Handlers for NPSP, that a BIG RED WARNING SIGN on Table-Driven Trigger Management (TDTM) Overview and/or other sections of TDTM documentation informs people that TDTM "config" is NOT mirrored from Production orgs to Partial Copy, Developer Pro, or Developer Sandboxes. Please and thank you!
  2. I know Trigger Handler records are records and that they do not come to these sandboxes, but is there any way to build some sort of customization that when they are "initialize" in one of these type of sandboxes per the note that the config in Production is mirrored? If not no worries, I know it is a tall ask, but if I do not ask then I do not know. 😃
  3. I think my final thought is....what about Custom Metadata Types. I feel like this is an even taller ask as I think all the code would need to get refactor to read from CMT rather than records, but at least CMT is metadata and that comes through sandbox refreshes, change sets and etc. Maybe you are working or thinking about this already and maybe you cannot say much, but maybe a wink? 😉

 

Thanks for hearing me out and well thank you for having this space to share my thoughts. Cheers!

18 条评论
0/9000