I think the Unified Interface will be great for the ordinary user. Admins and power users will have to wait until v10 to fully transition, if even.
I'm not a fan of the UCI. We don't have anyone in strictly a Sales role, or strictly a Customer Service role. They all bleed over within one another. Our consultants are entering opportunities when we get scope changes and support projects. Our sales reps review support tickets to see if there's an opportunity to upsell. From what I've seen so far, pigeon holing people into individual modules, AKA hubs, is a pain in the neck for our organization.
I found a workaround for it in our Sandbox instance so that my testers can test in the legacy environment - in your URL, you'll see 'forceUCI=1'. If you change that to 'forceClassic=1' it will pull up the legacy web interface. I don't know how long it will last, but rather than having to stop developing and complete training on how to work with UCI, then conduct a user training session, this allows them to keep doing what they're doing until we get to a development stopping point.
@Aaron Back, MCP
I saw that after I posted - this forum is bookmarked so I can go through and get it all figured out once we promote our development. Thanks!
I'm struggling with UCI. Testing solutions we're developing is proving to be quite a headache with the changes that rolled out.In my sandbox environment I've created a custom entity with a main form and default views. On the entity information page, I selected 'Service' under 'Areas that display this entity'.In order for my testers to access CRM, I then created an app called 'Sandbox' which uses the default sitemap and default solution. I've confirmed in the app editor and in the customization menu that my Sandbox app contains my custom entity. Then I updated the Customer Service Hub app to include the custom entity, form, and default views, then saved and published both apps. Neither one of my apps showed the solution in the site map like I expected it should since I added the entities access to the app.Why didn't the apps Site Maps update automatically when I added the custom entity to the app, since I already had 'Customer Service' selected? I would think that the setting on the entity information page would auto-configure the app site map?Is this a known bug/intentional feature? Is the entity information page no longer tied to the site map, even though I'm using the default site map?
HiAt the recent CRMUG event in Manchester one of the MS Architects was highlighting features of the interface and referred to the web interface as 'legacy interface'.On further questioning, he advised that the legacy interface is going to be deprecated and that at some point in the future (v9.2 IIRC) new instances will no longer have the option of the legacy interface.
Whilst we're not rushing to move over to UCI, it has focused our attention on moving over to it in a managed fashion.Jamie
"On further questioning, he advised that the legacy interface is going to be deprecated and that at some point in the future (v9.2 IIRC) new instances will no longer have the option of the legacy interface."@Jamie Hirst - I think you can generally add three versions to the one the first time you heard an MS rep say a particular feature would be deprecated at.