Показать сообщение отдельно
Старый 16.03.2017, 11:11   #37  
raz is offline
raz
NavAx
Аватар для raz
NavAx Club
Лучший по профессии 2014
Лучший по профессии 2009
 
1,490 / 1060 (38) ++++++++
Регистрация: 22.07.2003
Адрес: МО
Вы будете смеятся, но я тоже без доступа
Но вот тут можете посмотреть.

Cédric LUCHEZ

24 hours ago
During the Tech. Conference, there is a slide with the roadmap package seal. It's about the hard seal of App Suite, and the best example is to add a new product dimension. We have to overlay the macros for example, what's the solution ? I'm very worried about that.
Even if we have a lot of tools to create extensions, and more in the furure, it's not enough to manage all the cases. Actually the only things we have in our ISV's is to create parm methods, hookable and delegates only in App Suite. For the parm methods, there is a solution in the future. But the 'hookable' will still needed on private method as I saw. And I don't talk about the delegates.

I understand the goal for the cloud solution but what about the local version ?
Have we for all of our delegates and hookable, create a case to add them in Foundation model in App Suite ?

Phillip Arrieta

21 hours ago
Personally I believe this is a terrible decision on Microsoft's part. Clearly they do not understand the nature of application modifications that we as solution developers and integrators are required to make to satisfy customer requirements. In many cases we are required to disable or fundamentally change the functioning of an application feature, and it will never be possible to achieve this through extension alone. Also, modification is only way that we can correct Microsoft's own bugs in case of urgency without having to wait for the support process to run its course. Microsoft, rethink this decision. As partners and integrators, we will be less able to satisfy customer requirements because of this change, and consequently we will be less able to sell your software. It's lose lose all around.

Dave Froslie

19 hours ago
Thanks for raising your concerns, Phillip and Cedric. We do understand that this is a big change for the ecosystem, but we're committed to the direction and to supporting partners to be successful using extensions. Hopefully that came through during the presentation yesterday. If you didn't attend the conference or the session, I encourage you to watch the video once it become available to get more context on the background for this decision.

Regarding the specifics that Cedric raised, we are working towards a solution for product dimensions and I expect we will share the proposal in this and other forums soon. The hookable method challenge will be addressed for non-private methods in the class augmentation feature improvements. We would break encapsulation if we exposed private methods so we don't intend to make those hookable. The requirements that Robert Badawy presented had the following first two bullets:

- Author Pre and Post logic on public and protected (non-final) methods
- Access to public and protected variables and methods of base class

The current plan for on-prem is the same as the cloud (the models will be sealed).

Lastly, we're all going to have to change some due to this direction. More consideration will be required by partners to understand if a customer requirement is 'intrusive' or not and if it can be met given the extensibility capabilities. We realize that there will be non-intrusive customer requests where we have gaps in the Microsoft extensibility story. We will need to optimize our processes to be able to fill these gaps in a timely manner.

As I stated in the presentation, this is a journey that will take some time and effort. But we need to reduce the friction and cost in the ecosystem that prevents customers from staying current, so it's both necessary and ultimately beneficial for all.

Harold Albrich in reply to Dave Froslie

19 hours ago
And what if the customer requirement is 'intrusive'?


Phillip Arrieta in reply to Dave Froslie

18 hours ago
Dave, thanks for replying. One of the advantages and selling points of Dynamics AX has always been the flexiblity with which customizations of the application can be made. With this change, you are eliminating this selling point. Customer requirements are frequently intrusive, and we as integrators need flexibility from the product in order to be able respond to these requirements and deliver the solution in a timely and cost effective manner. You can talk about supporting partners with extensions all you want, but at the end of the day you are only making it more difficult for us to do our jobs, and making it more difficult for us to sell the product as a viable solution. Locking down the application might be in Microsoft's interest, but it is certainly not in ours. This "new direction" can be summarized as shooting yourselves and your partners in the foot.


Phillip Arrieta in reply to Harold Albrich

18 hours ago
So far, I guess the answer is "buy from the competition".

Rizwan Ahmed

16 hours ago
Just a thought, Does Microsoft take into account the business / sales into extensibility discussions?
The points raised by Cédric LUCHEZ, Phillip Arrieta and Harold Albrich are valid and painful realities while working D365O. There are requirements that just cant be done without over layering.
There are requirements where customer gets charged $$$$ in charge backs when dealing with actual scanerios.

Daisuke Kobayashi

7 hours ago
One fast question,
Will this change be released as Platform update or Application update?
We have to apply it in one year if it was released as Platform update.
Вложения
Тип файла: docx AppSuiteLock.docx (147.4 Кб, 137 просмотров)

Последний раз редактировалось raz; 16.03.2017 в 11:20.
За это сообщение автора поблагодарили: fed (2), Logger (3), ax_mct (7), alex55 (1).