Personalized Community is here!
Quickly customize your community to find the content you seek.
Latest TechTalk Videos
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I have a requirement to set the detailed input parameter in vendor aging report dialog to 'yes' and hide it to prevent user from changing it.
I have managed to set it to yes through extending VendAgingReportContract and wrapping parmdetailed() method to return true by default.
My question is how to hide the field from the input parameter dialog?
I remember doing this for a custom report. The way to do it is to add the following attribute to the parameter you want to hide in the data contract:
I think there was a community question for this exact same requirement you have, let me see if I can find it.
I think it was this one:
Hope this helps.
thank you for the reply
As far as I know in d365fo we cannot override classes, so I cannot override the contract class in order to add the control visibility attribute
Right, I didn't realize you were extending an existing report. Not sure if you can modify method's attributes through CoC.
Another valid approach for this would be to extend the original Output menu item for the report and change the Object property to a custom controller class, and from there build your own report, DP and contract class (or duplicate the original objects, in your case), so you'll have full control of what you want to show.
Granted, it seems like too much work for just hiding one parameter.
Also, this method is not always recommended in the sense that, if Microsoft upgrades/fixes any code related to that report, you'll have to also apply those changes to your objects.
I'd leave this question open in case someone else wants to weigh in.
Business Applications communities