Feridun Kadir Expert CRM Services Ltd Principal Consultant

I think that Price Lists are not working as expected in CRM 4.0.

Here's a scenario. I have two price lists defined, Retail and Wholesale. I add some products and create price list items for them on the retail list. I add some other products and add them to the wholesale price list. But I don't set the default price list for any products.

My understanding (and I think CRM help supports this) is that the default price list is optional and that provided a product has a price list item for a price list that matches the price list of an opportunity or an order etc, the product can be added to a record.

So, if I have an order with a retail price list I would expect to be able to add products that have price list items on the retail price list.

What I find, in practice, is that I can't add any products to opportunities etc unless I set a Default Price List - which is weird because this is not a mandatory field.

And when I set a Default Price List of say retail, I find that products that only have retail price list items can be added to an opportunity with a wholesale price list. I sort of understand this, because I guess that is what the default price list is for. But I don't understand why products that don't have a default price list can't be used.

Consider a scenario where a contract is linked to an account. Create a case, complete the title and and the account to the customer field, save the record. Click in the Contract field. The Form Assistant does not show the contract for the customer.

Now, create a case, complete the title and add a contact (that is linked to the account) as the customer. Save the record, click in the Contract field. The Form Assistant shows the contract for the parent account.

I believe is this is incorrect behaviour and the Form Assistant should show the available contracts when the account is selected as customer as well as when the contact is selected as customer.

When tracking an e-mail from within Outlook, the from e-mail address is matched unexpectedtly to a user record.

The match is unexpected because the from address on the e-mail does not match the Primary E-mail on the user record but it does match the Windows Live ID field.

Tracking e-mails should not match on the Windows Live ID field.

Note: The CRM database was migrated from OnLine to OnPremise.

When tracking an e-mail from within Outlook, the from e-mail address is matched unexpectedtly to a user record.

The match is unexpected because the from address on the e-mail does not match the Primary E-mail on the user record but it does match the Windows Live ID field.

Tracking e-mails should not match on the Windows Live ID field.

Note: The CRM database was migrated from OnLine to OnPremise.

When two accounts are merged, the value of fulfilled orders can change. To reproduce, complete the following steps:
�Create two accounts named ABC Ltd.
�Ensure you have a product in the product catalog with a value in list price and a price list item that is set to 100% of list price.
�Create an order against one of the accounts, add a product and then fulfil the order.
�After fulfilling the order, change the list price of the product, then review the order; the value of the order has not changed (as expected).
�Now, merge the two ABC Ltd accounts selecting the one without the order as the master. As expectd, the order linked to the second ABC transfers to the first ABC.

However, the value of the order is recalculated using the new price even though the order was fulfilled. This is not expected and undesirable. The value of fulfilled orders should never change.

Workaround to prevent the value on orders from changing

On the ribbon for orders there is a button labelled Lock Pricing. The purpose of this is to prevent changes to prices on line items for open orders.

According to the CRM help, this means �type of pricing behavior that prevents changes to the price per unit for products in open orders or invoices�.

Even if a price changes in the product catalog, the original price will remain for any open orders or invoices in which Prices Locked has been enabled. Note that the help refers to open orders.

To prevent the value of fulfilled orders changing, click Lock Pricing before fulfilling an order. When merging accounts and where an order has Lock Pricing selected the prices on order line items do not change if the product price changes after the order is fulfilled. It should not be necessary to do this to prevent the pricing on fulfilled orders changing.

Scenario: Create two relationships between opportunity and contact (one as 1:n and the second as N:N)

Add a sub grid to an opportunity form for each relationship.

Only the first sub grid shows the Add Record and Open Associated Sub Grid icons.

It doesn't seem to matter which sub grid is shown first, but only the first one has the icons.

Add a section to a form, in the section add a quick view control and/or a map control and regular fields from the entity.
Then select multiple records of the entity and click Edit. In the Edit Multiple Records window the regular fields that are in the same section as the quick view or map control are not shown.

Workaround: move the regular fields to a section that does not have a quick view or map control.

Not sure if this is a bug or by design but I thought worth pointing out.

Follow these steps:
1. Navigate to a contact that has a value in Company name
2. Click the lookup control for Company Name
3. Click + New

In the Quick Create form, Account name is populated with the value that is in Company Name. This is not expected. I would expect Account Name to be blank.

Consider an entity with two fields, Field A and Field B on a form.

The fields are laid out so that after tabbing from Field A focus moves to Field B.

There is an OnChange event for Field A that changes the value of Field B. However, the event fails to set the value of Field B. If instead, the OnChange event is fired by modifying the value of Field A and then clicking elsewhere on the form rather than pressing tab, the event does set the value of Field B.

Similarly if the OnChange event explicitly sets focus to another field than Field B before attempting to set its value the change succeeds.

Field A in my test was a lookup field. I have not tested with other field types.

I think this is a bug.

Tested with CRM On-Premise with Update 0.1

Deleting a custom field can result in rollup queries failing and any goals that use the rollup query (via a goal metric) can no longer recalculate.

Recalculate on the goal gives a query builder error. There is no way to identify the problematic field on the rollup query. The rollup query shows the filter criteria for the record set, clicking on Preview records causes the error. There is no way on the rollup query record to adjust the columns in the preview. The only solution is to delete the rollup query and start again.

There should be a way to modify the rollup query preview columns. Also, the rollup query should show as a dependency on the field.

This has been previously logged but more than 6 years ago with no resolution.