CRM 2013 Form - +New button behavior

[D365Ideas_Admin]

CRM 2011 had a Save and New button on the ribbon. CRM 2013 has a +New button, but the behavior has changed. Users anticipate that they can quickly enter multiple records by entering the field data and then press the +new button and then continue to enter the next record. This data entry pattern worked well in CRM 2011, but in CRM 2013, the +new button no longer saves the record. It doesn't even display a warning to the user - it just throws out the data and resets the form. The behavior should be changed back to the CRM 2011 behavior to facilitate this data entry pattern. This would also be consistent with the intent of having an auto-save behavior in CRM. As a minimum, if the behavior is not going to be changed, a warning should be displayed to the user that their data is going to be lost if they continue.

[D365Ideas_Admin]

Hi,

In the latest release, below is the behavior and that is an improvement from the behavior mentioned in this issue.:

1. When you try to navigate away from the record by clicking on '+New' when it has been newly created, a warning is shown to the user asking him to save the record.

2. If user updates a record that has been saved and auto-save has been turned on, the record gets saved automatically when the user clicks on '+New'.

3. If user updates a record that has been saved before and auto-save is off, a warning is shown to the user asking him to save the record.

We will look into addressing the concern of having a 'Save and New' button in a future release.

Thanks,

Neerja Rewal

PM, Microsoft

[D365Ideas_Admin]

This really needs to be looked at. Customers get so confused as do we when trying to work out why it works one way here and a different way there. Just changing the default view can cause changes. Weird is all I can say.

[D365Ideas_Admin]

Another area where this is affected is when adding related record from a subgrid. You add the first record, and you want to add another. Since there is no 'Save and New' you can only click 'Save' (or 'New' which incorrectly clears the form as you noted). After clicking Save, you can then click New, however this goes on to create a new record outside the context of your parent record. This means no mappings are applied, and you will end up with orphaned records if you're no careful.

[D365Ideas_Admin]

The new UI is riddled with inconsistencies and ambiguities like this - particularly for related records For example: - Add New vs Add Existing - Delete vs Remove vs Deactivate - Search vs Select - "Records associated with this view" shown/not shown - Single customer-type lookup or one account plus one contact lookup - Pop-out (with Navigation) vs Pop-Out (without Navigation) vs Navigate to

[D365Ideas_Admin]

Voting this up! This behaviour is really not ideal, we have customers just shaking their heads over this.

[D365Ideas_Admin]

We are a programmer and trainer I can say CRM 2013 UI is too bad enhancment

[D365Ideas_Admin]

I don't know who is the stupid guy who is not qualified and didn't know exactly the real need of features and advantage in CRM 2011 to decide to change the fantastic CRM 2011 UI to his stupid interface

[D365Ideas_Admin]

Thanks for the feedback guys. We were anticipating heavier usage of the quick create functionality to facilitate multiple create scenarios, however your feedback is taken for our main forms. We will consider this for our future roadmap in addressing this.

[D365Ideas_Admin]

Why is this not prioritized? This is such central/core functionality that it should be fixed asap. Some customers appreciate the less-is-more approach but only when it remains logical. And as mentioned in the previous comments - it doesn't. Why can there not be two + buttons over the grids* +* and [+] for Adding New and Adding existing respectively?

[D365Ideas_Admin]

This is three years old and it's still "Under Review". I have a feeling the CRM team doesn't actually care about their customer feedback. And it's obvious they don't do any usability testing because anyone could have told them this feature having gone missing was a mistake.