Class of 2030 and later

Kellie DeMers

Has anyone been running into issues querying, exporting, etc. with relationship records that have an education class year of 2030 or later if your system is set up for a default two digit year (e.g. '30 instead of 2030).  Our system does not want to include these records in queries.  I have chatted with BB support about this and they say it is an issue, but just wondering if anyone else was experiencing the same thing.  .  

Carolyn Moatz

We haven't added the class of 2030 yet, so we're not running reports on it yet, but the solution may lie in Windows (assuming that's what you use). Go to Control Panel/Clock, Language, and Region, then click on Region and Language, select Advanced Options, and go to the Date tab, there's a box labeled calendar which will allow you to move the two-digit year past 2030 (mine was set to 2029).

Kellie DeMers

I did troubleshoot this with BB and they said that their system does not recognize a 2 digit class year after the class of 2029.  The system switches over to 2030 after that and the problem I am running into is that my queries and exports are not recognizing the four digit format so the kids with that class year are not coming over in the query and exports.  I was wondering if anyone else was having this issue and if they had developed a workaround.

Carolyn Moatz

It is really strange. I added myself as the class of 2030 to see what would happen, and I can pull on it if I set Windows to two digit years up to 2029 and pull the class of 2030, but if I set the two digit year any further, it pulls the class of 1930 instead. My suggestion for a work around, if only until Blackbaud sorts it out, would be to set Windows to 2029 and do a find and replace for 2030 to '30 when you export (assuming it's to excel or merged to word or something), but build your queries and reports with the year 2030. Unfortunately, anything that goes to pdf will say 2030, but at least you'll be able to report on it. I had been under the assumption that the Windows fix would be all I needed, but apparently not.

Kellie DeMers

Actually, my Windows was already set to 2029 and it was still doing it that way.  And if I try to put in the class year of 2030 as '30, it reformats it back to 1930.  My queries are already built with the '2030' and that is what it is not reading.  But thanks for trying.  I guess I will have to wait until BB gets their act together and devises a fix for it.

John Heizer

Y2K strikes again, sixteen years later! 

Dodie Udall

Kellie DeMers:

I did troubleshoot this with BB and they said that their system does not recognize a 2 digit class year after the class of 2029.  The system switches over to 2030 after that and the problem I am running into is that my queries and exports are not recognizing the four digit format so the kids with that class year are not coming over in the query and exports.  I was wondering if anyone else was having this issue and if they had developed a workaround.

I am having this exact same issue. One temporary fix is to go into Configuration, Business Rules and change Alumni preferences to use the four digit format. My class of 2030 showed up in my query after making that change. However, it means your alum show up as John Doe 2018, rather than John Doe '18. So my work around is to change it just for the query I need, and then revert the business rule back to the two digit format after pulling my query. This is obviously not a long term fix, but it does work for the short term. Hopefully BB will get it fixed on their end.

Chas Dreyfus

Kellie DeMers:

Has anyone been running into issues querying, exporting, etc. with relationship records that have an education class year of 2030 or later if your system is set up for a default two digit year (e.g. '30 instead of 2030).  Our system does not want to include these records in queries.  I have chatted with BB support about this and they say it is an issue, but just wondering if anyone else was experiencing the same thing.  .  

I also ran into this problem. Support enabled me to access Regional Settings in the Applications area of Blackbaud Hosting Services. There, under Formats, I opened Additional Settings, and on the Date tab increased the upper limit of the calendar year to 2034. That seems to have solved the problem for the next four years. I was surprised to see there's a fixed range of years, and the lower limit moved to 1935. That's our earliest grad year. So, we're OK until the Class of 2035 enters Kindergarten.

Heather MacKenzie

Purely for my curiosity's sake only, since I am not in the education world in my work these days, what situation are you in that you are already entering data regarding a class year that is 13 years ahead of today?

Stephanie Crawley

Heather MacKenzie:

Purely for my curiosity's sake only, since I am not in the education world in my work these days, what situation are you in that you are already entering data regarding a class year that is 13 years ahead of today?

Our current students have class years attached to them, rather than saying 8th grade, and then having to update every single child as they progress each year.  We are a PK3 through 12th school.  Our current PK3 students have a class year of 2032.

Heather MacKenzie

Stephanie Crawley:

 

Heather MacKenzie:

Purely for my curiosity's sake only, since I am not in the education world in my work these days, what situation are you in that you are already entering data regarding a class year that is 13 years ahead of today?

Our current students have class years attached to them, rather than saying 8th grade, and then having to update every single child as they progress each year.  We are a PK3 through 12th school.  Our current PK3 students have a class year of 2032.

 

Thanks, Stephanie!

Stephanie Crawley

Chas Dreyfus:

Kellie DeMers:

Has anyone been running into issues querying, exporting, etc. with relationship records that have an education class year of 2030 or later if your system is set up for a default two digit year (e.g. '30 instead of 2030).  Our system does not want to include these records in queries.  I have chatted with BB support about this and they say it is an issue, but just wondering if anyone else was experiencing the same thing.  .  

I also ran into this problem. Support enabled me to access Regional Settings in the Applications area of Blackbaud Hosting Services. There, under Formats, I opened Additional Settings, and on the Date tab increased the upper limit of the calendar year to 2034. That seems to have solved the problem for the next four years. I was surprised to see there's a fixed range of years, and the lower limit moved to 1935. That's our earliest grad year. So, we're OK until the Class of 2035 enters Kindergarten.

 

Thanks, Chas, for this fantastic tip!  I chatted with Support, who opened a ticket with the engineers group, and after a couple of days they added Regional Settings to my products in my Blackbaud Hosting Services page.  Then I went into it as you described above and changed the upper limit of the convert from 2 digit year setting to 1960, when our school was founded.  It fixed the query problems I was having.  YAY!!!!  Just hope it doesn't create any issues with birthdates for Alum and Parents- I wouldn't think so, but I will pay attention to that going forward.

Brian Davies

Per Blackbaud tech when I realized the issue:

This was a known issue that was resolved in RE 7.95 Patch 3


 updated a few weeks ago, no issues since.

Carlene Johnson

Brian Davies:

Per Blackbaud tech when I realized the issue:

This was a known issue that was resolved in RE 7.95 Patch 3


 updated a few weeks ago, no issues since.

So, to confirm.... Once folks update to 7.95 Patch 3 or higher, when exporting based on business rule set to 2 year vs. 4 year, they will no longer run into the issue of blank class years for `30 or higher?  Is that corrrect?

Brian Davies

Carlene Johnson:

Brian Davies:

Per Blackbaud tech when I realized the issue:

This was a known issue that was resolved in RE 7.95 Patch 3


 updated a few weeks ago, no issues since.

So, to confirm.... Once folks update to 7.95 Patch 3 or higher, when exporting based on business rule set to 2 year vs. 4 year, they will no longer run into the issue of blank class years for `30 or higher?  Is that corrrect?

 

My queries, reports and exports are now working correctly.

Stefan Syski

Thanks to all on this post!  I just ran into this issue with our incoming Class of 2030 (we start in 3rd grade), and was able to solve the problem using this string.


We are hosted by Blackbaud in the Microsoft Azure environment (that is, we load the RE Database View by logging into RE NXT first and then clicking on the database-stack icon).  For others in the same type of hosted status, you can find Regional Settings as a menu option when you click on the database-stack icon.  From there you just follow Chas' instructions (see 9/15/17 post).