Old Customizations

Hello!
It's me. Three months later, still slogging through this customizations report little by little. I've taken your advice here and have been putting xx_ in front of procedures I know to not be used anymore. Other lessons learned I wanted to share.
1) Chat GPT has been helpful for quickly understanding what a procedure does (I am not a SQL Wizard)
2) There's a documentation of standard localized procedures here.  This will help you quickly identify procedures on the list that definitely need to be updated for v16.
Anyone else slogging through this report and have lessons to share?

Hello!
It's me. Three months later, still slogging through this customizations report little by little. I've taken your advice here and have been putting xx_ in front of procedures I know to not be used anymore. Other lessons learned I wanted to share.
1) Chat GPT has been helpful for quickly understanding what a procedure does (I am not a SQL Wizard)
2) There's a documentation of standard localized procedures here.  This will help you quickly identify procedures on the list that definitely need to be updated for v16.
Anyone else slogging through this report and have lessons to share?

Kanani Reichlin said:

Anyone else slogging through this report and have lessons to share?

We had a variety of custom report issues when we first worked with v16 last winter, and over the summer support and I gradually moved from "this is out of scope! We can't support your custom report parameter code", to, "OK, this is a defect", and we are in a much calmer place these days.

Some painfully gleaned tips re: custom reports and v16:

• Check any report parameter dropdowns that involve an fyear. You may need to convert that to varchar to get dropdowns to display in v16.
• Check any report parameter dropdowns that involve order-by code that includes "inactive desc". This code may need to be modified to get dropdowns to display in v16.
• Some standard, hidden parameters that were deprecated in some previous version but have been working fine 'til v16 may now cause problems with an y custom parameter code that involves bracketed ids, e.g. <<1>>, and so on. Double check any of these.

I will say that, where possible, I have tried to come up with solutions to changes that will work in both v15 and v16, even if a bit janky, so that I can make the changes and test them one by one instead of having to do a huge tranche of updates immediately after the upgrade, when we'll have a ton of other things going on, and then have to worry about 60+ different customizations that might not have been updated properly, or might have an unforeseen issue or interaction.

Gawain Lavers said:

I have tried to come up with solutions to changes that will work in both v15 and v16

Likewise. None of the report parameter issues/fixes I mentioned above were considered resolved until the report worked as expected in v15 and v16.

Kanani Reichlin said:

Chat GPT has been helpful for quickly understanding what a procedure does

This is brilliant- I'd never would have thought of it!  It may help me understand some custom procedures where I'm currently mumbling "what the ___ were they trying to do?" :-)