Currently in web view, there is no custom field area for non-constituent relationship records. We rely this field (relationship attributes) for some of our processes and having it absent in webview is a problem.

We especially use non-constituent custom fields on our org contact records. To give a concrete example, we send out a yearly holiday card with a pretty complex set of criteria. While some of these criteria are basics like constituent codes and gift amount in the past year, we also have a number of business contacts that we've marked to receive the card every year, regardless of the org's giving behavior. We pull data this way each year for the card print (using a relationship query), and need to be able to update records to include this code as new Contacts need to have the custom field added and we remove the code for contacts we no longer want to automatically include yearly.

Earlier this week I was updating Fundraiser assignments in webview for constituents who are no longer considered to be potential donors and for a few constituents, the only Actions on their record were our annual Holiday Card for a number of years. I wanted to check which contact had the attribute and found I could not access that information in webview. I needed to know if the custom field was still present on any of those records so I could follow up with my gift officers about whether we still want to send the card. I had to open database view and search for that record there in order to get the full picture of information.

Relationship records in webview are currently one of the more frustratingly lacking in terms of parity with database view. It is really important that these discrepancies be remedied before we're in the Total Web Solution.

I'm sure others use non-constituent relationship record custom fields strategically the way that we do. Please consider making sure this functionality is availably in webview.