Adding Related Money Fields to a View

Posted by Jim Steger on December 3, 2009  |  Comments (1)

Recently Mike tried adding a money attribute from the Account entity on one of our existing Contact views. For illustration purposes, let’s assume it was the contact’s parent account’s credit limit field as shown below:

Much to his surprise, he received a generic CRM dialog box when he tried to run the resulting contact query.

After a bit of research, it turns out that CRM is expecting a transactionCurrencyId for that related entity, in this case account. Therefore, the solution was to either add the Currency field (transactioncurrencyid) from the related entity or you can add the money attribute’s Base value instead (assuming you aren’t utilizing multi-currency).

Note that if the money attribute of the records returned from your query are null, the query will work. However, once that field is populated with data for one of the returned records, you will receive the error.

Also, we had a case where adding a money field from the main entity caused a similar problem. In that instance, we had some records missing a transactioncurrencyid value (possibly from a mangled import). So, be sure to check your data and ensure that valid transactioncurrencyid exists on all your records.

Hope this helps!