Hi,
On the ACE 2017 Europe conference, a technique that utilized Federated Data to add a TOC menu item that did a custom search was showcased. In my case, I want to add a new TOC menu item, besides the Part menu item, that searches among Released Parts. I.e., the menu item should be called "Parts Released", clicking it and then clicking the "Run Search" button should return a list of parts that are released.
On the conference, they said that I should create a new dummy ItemType, and redirect its requests to the real Part by modifying the onBeforeGet to server event. Apparently this is related to data federation according to the presenter. However, I do not remember the exact steps to implement this.
I got the impression that there should example code demonstrating this on Aras' GitHub page. However, I have browsed through several pages of Aras' repositories on GitHub, and I cannot find any project that sounds to be what I am looking or.
Does anybody know how to achieve what I am asking for? Or where sample code can be found?
Please tell me if you want me to clarify anything in my description.
Thanks,
I have done some basic cleanup of the sample project and added an image for a sample use case.
-> github.com/.../custom-itemtype-view
Currently, I am having mixed feeling about the current result.
I still like the idea and the basic sample works. But the current version is inflexibly and terrible to maintain.
Instead of treating each non-working CUI button separately, maybe a better approach is the use of CUI Methods, that handle the parameters passed to the original CUI buttons.
I made some successful attempts with the automatic linking of the original Part Actions and Reports to the FakePart with a additional Methods in the Presentation Configuration.
This way Actions and Reports were automatically added to the Main Window Menubar and Main Window PopUp Menu. But I still do not have enough programming knowledge to use this concept for all of the related CUI elements. Maybe things will become a little bit easier with the new xProperties, but I haven´t tried yet.
I do not work on the project often, but I think I'll find the missing piece of the puzzle someday.
All fresh ideas for this project are very welcomed!!!
I have done some basic cleanup of the sample project and added an image for a sample use case.
-> github.com/.../custom-itemtype-view
Currently, I am having mixed feeling about the current result.
I still like the idea and the basic sample works. But the current version is inflexibly and terrible to maintain.
Instead of treating each non-working CUI button separately, maybe a better approach is the use of CUI Methods, that handle the parameters passed to the original CUI buttons.
I made some successful attempts with the automatic linking of the original Part Actions and Reports to the FakePart with a additional Methods in the Presentation Configuration.
This way Actions and Reports were automatically added to the Main Window Menubar and Main Window PopUp Menu. But I still do not have enough programming knowledge to use this concept for all of the related CUI elements. Maybe things will become a little bit easier with the new xProperties, but I haven´t tried yet.
I do not work on the project often, but I think I'll find the missing piece of the puzzle someday.
All fresh ideas for this project are very welcomed!!!
