Miss-match in values of calculated type field, between a Database View and one of its view tablesIssue There is a Database view, which is a join of these two view tables: [sn_communities_idea] and [sn_communities_content]. A calculated type field on [sn_communities_idea] does not display the same value when accessing it directly through that table, as it does when accessing it through a Database view. When looking for the values of the column through the raw database, the value is the same in the database and in the Database view, but different from the one seen in [sn_communities_idea] table.CauseThis is expected behavior since the record has not been updated/saved in Ideas[sn_communities_idea], it does not have the current value stored in the database. The database view is displaying the value directly from the database. *Calculated fields are not designed to be used for real-time reporting. ResolutionSet up a Scheduled Job to Update/Save all the Ideas[sn_communities_idea] records. Alternately, create an Insert/Update/Delete Business Rule on [sn_communities_ideavote] (since it is the table being referenced in the field) to automatically update the associated records.