-
Allow ehanced extensions & debug directly on binaries (without XPP files)
Because we deliver deployable packages (Bin) to a customer, there is no 'xpp' and no possibilities to make enhanced extension on that. Of course, we want to give the opportunity to our customers to make extensions on our functionalities. But we want to be sure that our code will not be stole by someone who is malicious. The extension is a wonderful thing, but allow the possibility to easily stole the code if we deliver the content of the models. I think we are not only ISVs / Partners who be aware of that... We want to have a way to protect our code but we want to give the possibility to a customer to make extensions based on our code too. And we want to allow the possibility to debug too. But with the binaries it's complicated. No possibilities to see some piece of code, only the stack. It's the same issue for a D365FO app on appsource... So, it will be very helpful if we have the possibility to make enhanced extensions & debug directly on binaries.
-
Allow extension for FormDataSource
Is there any plan to introduce extension for FormDataSource ? I mean, we can create display on table but I did'nt find a way to create a display on form for a formdatasource. Because in my case I need the context of my form sometimes. For example on ReqTransOverview form in one of my cases. I already thought to create a table class extension with some event to recreate my context and create a display on this context, but It's not pretty :) Is this possible to add a thing like [Datasource], [formdatasourcestr(form1, table1)] or anything else before my display to set my source context directly on my fom class extension ? Or introduce an new Extension class on FormDatasource ? (The worst idea I think) That question has been asked a long time ago on yammer and on Connect but never on that portal.
You’re offline. This is a read only version of the page.
