Thanks. I’d followed some older example code for setting up a C++ class with a child Blueprint that included the FObjectFinder code. However, I’ve confirmed that my class automatically has access to the child Blueprint’s variable settings (I declare a variable in the C++ class and actually set its value in the Blueprint configuration) so I don’t need that call at all.