Instead, we have to find a proper position where the code extension is possible, and the instance of the UI element which we want to hide is available and accessible.
By going through all available extension hook in controller source code ( naming convention extHook... ), it is identified that the hook extHookGetDataForDetailScreen could be used. This hook will be called once the batch odata request to retrieve data for detail view display is returned from CRM backend.
The idea of hook implementation is get the to-be-hide UI element instance and call its method setVisible to hide it. This hook is done in your extension controller.
The whole source code of this extension project could be found in github: https://github.com/i042416/testOpportunityExtension
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
12 | |
9 | |
8 | |
7 | |
7 | |
6 | |
6 | |
6 | |
6 | |
4 |