Spießrutenlaufen is everywhere. Even fundamental actions like creating a new entity in CRM are subject to irreversible hasty choices that we all come to regret later.
Introducing CRM Tipsters Illustrated Guide to Entity Creation in Dynamics CRM.
Download a full size image or a hi-res PDF version.
This poster needs to be converted to a create new Entity wizard, including big flashing warnings when you’re doing something stupid. Awesome stuff!
With Update 1 on CRM 2016, add Feedback entity to the Uncheck List.
It’s already included. Instructions are to clear All checkboxes which, I believe, includes Feedback as well. The power of foresight.
Flow of the decisions seems slightly backwards to me. Surely the question “is it an Activity” should be first (which also means it ought to be first in the UI). If it is, then the ownership and various other things are decided for you. If not, then you get to choose them.
No Adam, the first question is what it should be – do you have a solution or are you trying to create an entity with an effing new_ prefix.
Is my font selection for the chart OK with you?
OK, not first, you are right that you need to do this inside a Solution. My point is that it seems odd to consider things like Ownership and granular security first, then decide if it is an activity, which effectively decides this for you. Also if an activity should not be visible in the Activity Menus, the “No” arrow needs to just skip the step to select “Display in Activity menus”. Routing it to renaming the primary field is no good, since for Activities that must always be “Subject”.
Font is fine, thanks for asking!
I guess you have a point, Adam, deciding whether entity is an activity should be one of the first steps. Mk II is coming 🙂