172
Hello there,
Around 4 months ago, I was able to create web applications to one of our clients using the new app designer in the CRM, but for some reason that option is not showing up when creating a new app, it just shows up unified interface option.
Does anyone know why it let me to do it a few months ago and now is not available?
If this option was removed, it was definitely a bad decision.
Thank you.
*This post is locked for comments
Hi Michael,
I understand your concerns and your frustrations from enterprise stand point with 100/1000s of users and a technology that's changing at a rapid space.
Here is how we deal with situations you mentioned above.
The classic web client is not deprecated yet, you can still use it, you can still create separate site map and deploy it but its just that the App Model that has been changed, that is mostly in line with the Model Driven app model of PowerApps. Its kind of same for all the deprecated or old feature, they will still work for years to come but its just not recommended for any new projects or solutions
I am sure the Classic client will still be around for years, but it would be better to plan for moving to unified interface slowly and train the users
To keep up with the changes and updates, we normally subscribe to all the Office 365 and Dynamics 365 update notifications and these are sent some time months before the update, so it gives us chance to know more and even test on a sandbox before we allow that to be applied on our PROD. So my point here is notifications, communications from MS helps us to hand this reasonably well. So my recommendation would be please subscribe or opt-in for all the notification email or also check office 365 message centre and make sure you are fully aware of updates and changes and release notes.
I am not a Microsoft Employee but I found that if you have any serious issues caused by any updates they done, you can definitely raise it with them and they will definitely provide a solution or at least provide guidance as to how you could still use the old feature and stuff.
/soapbox on
There are however some very sound reasons why this was a poor decision on Microsoft's part.
1) Adapting to the Unified Interface is a very significant change management issue
When dealing with systems running at an Enterprise level, with Users in the 100s or 1000s rather than the 10s, training up your user base to make use of a complete UI can be an exercise that takes months.
In a BAU Support situation, you need to be able to construct things *in the interface that all your users are using*, not the one that they may be using next year. There was no notification in advance that this change was going to happen - it just happened overnight. We had a situation that an App that was due to be deployed in January as an extension to an existing system had to be simply abandoned for this very reason. It will now (possibly) be deployed in the latter half of 2019 once the massive re-training exercise has completed.
2) While it improves every week (/golfclap for the weekly releases guys), the Unified Interface is NOT as stable as the Web Client
Again, Enterprise systems need to work reliably week after week. I shudder as I read the "Online Releases" page each week with it's list of "Did they really break that!!!" fixes in it.
Frankly I wonder how anyone can now sensibly propose Dynamics 365 C.E. for such Enterprise Clients. If I'm pitching a multi-million Enterprise build to replace a particular LOB system, the Client is expecting their investment to remain stable functionally for Years, not Months. They have think about things like Change Management; User adoption; QRGs and SOPs and all that boring stuff that allows ordinary operators to function.
At this moment I find it hard to predict what functionality will be available and more importantly how it will be operated next month let alone next year.
/soapbox off.
Now all make sense, thank you Kokulan.
Hi
With recent updates to Dynamics 365, the App model has been improved and changed to be Model Driven App (One type of PowerApp). Model-driven up does not support the old web client anymore.
it is recommended that any future or new projects should be done in Unified Interface as Microsoft will slowly move away from the classic web client (Once the Unified Interface achieves full feature parity).
Please see the following line "Microsoft’s goal is to make the Unified Interface the primary, and only client interface for all Dynamics 365 customer engagement apps."
https://www.preact.co.uk/blog/dynamics-365-unified-interface-frequently-asked-questions
The unified interface is based on fully-responsive design and works on all devices. You only have to customize once and use it on any client. Since classic web client is going to be replaced by the Unified interface, I would highly recommend that if you are creating any new app or solution, Unified interface is the best choice.
Please refer to following links as well to know more about this.
https://www.preact.co.uk/blog/dynamics-365-october-2018-update-what-you-need-to-know
#1
Mohamed Amine Mahmoudi
83
Super User 2025 Season 1
#2
Community Member
52
#3
Victor Onyebuchi
6
Share
Report
All responses (
Answers (
