GlobalController breaking: Variable does not exist

[Unportant]

We're getting the below errors when we try to compile all classes. I've chased down possible problems in our own code that might be causing this, but I can't find any .... of course, I'm not certain exactly what's going on in the code ... I can only assume that it's trying to reference the standard Contact field. Compilation Complete Compilation Errors found: GlobalController: line 1259, column 463: Variable does not exist: MiddleName GlobalController: line 1311, column 195: Variable does not exist: MiddleName GlobalController: line 1644, column 221: Variable does not exist: MiddleName Thanks, Nick

[CnP.Support.AM]

Good day @Unportant

To avoid the above error, please enable Middle Name at User Interface.

[Unportant]

CnP.Support.AM , thanks for the response. I'm not sure what you're talking about.

* I can't find anything like this in CnP Settings in SFDC or in CnP proper (which shouldn't be applicable anyways, as this is similarly not working in sandboxes that aren't hooked up to CnP).
* In the "Contact & Account Mappings" section of CnP Settings, there's the following warning text ... which also refers to a page in the Settings that does not seem to exist:

• Before mapping the "Middle Initial" to the standard Contact field "Middle Initial" make sure it is active in the Settings > Name Settings > "Enable Middle Names for Person Names"

* I found a help page about some post-install updates that need to be made in sfdc after Winter '21 .... but it all seems to be about CnP Events, and doesn't really apply to us.
* The running user in SFDC does have access to the MiddleName field.

Thanks,
Nick

[CnP.Support.AM]

Good day @Unportant

It is a known issue and hopefully will be addressed in an upcoming release. However, for now, the workaround is to enable the Middle Name at User Interface: Go to SFDC > Setup > Customize > User Interface > Name Settings.

[Unportant]

CnP.Support.AM okay, thanks .... I can't find this issue being tracked anywhere, or even mentioned anywhere. This workaround has collateral damage for us, so we're in a bit of bind unless the underlying issue gets fixed sooner than later.

[CnP.Support.AM]

Good day @Unportant

This issue has been identified while testing for the upcoming version and will be addressed in the next release.

Sorry for the inconvenience.