Hi,

It sounds it could either be due to an ACL or due to a onBefore Query Business rule that could be restricting the user from having visibility to the existence of the field. Keep in mind that the read ACL could exist at any level within the hierarchy of the table you have. It's ok to create a new ACL when needed. The impact will be the new behavior you're introducing based on the change that you perform. Make sure you properly test your change against intended and unintended behaviors.

Thanks,

Berny