Not sure what version this question was raised against, we have found the same issue in PRPC v7.1.5 as well. We have created a very simple view with one column - pyID, however we are still facing the same issue from Pega end.
We have mapped the class to the correct key and all configurations are identical with the other class configurations as well.
Thank you for posting your query in the PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write Post button here. Once created, please reply back here with the URL of the new post.
You may also refer this discussion link as a reference in the new thread.