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,
Nice to see that I am not the only person who has low respect for items containing the term "Core" :-) Welcome to the dark side! But I don´t thnk we should kill the main grid (maybe later... :-) ). Creating a customized TOC view will high likely not solve the problems with the Actions that link to the false tables.
I made some attempts with JS. Mostly in the ItemType tab “Client Events” (event = onAfterNew). Problem: The events only react on changes in the new ItemType, not in Part. The whole issue is more in direction of Federation, which I have to deal with the next weeks anyway.
But maybe we should just think more radical.
In summary, the following functions are currently causing problems:
- Save As
- Lock / Unlock
- Structure Browser / Where Used (lower priority for me right now)
All of them have the same fundamental problem. The button actions link to the wrong tables. But they have one thing in common: All of them are CUI elements! (if you use SP9 or above).
Instead of modifying the ItemTypes or Methods, why not get rid of the standard Actions and use own CUI buttons that do the work right?
Something similar is e.g. done in the ItemType InBasket, where lock/unlock is replaced with claim/unclaim.
Nice to see that I am not the only person who has low respect for items containing the term "Core" :-) Welcome to the dark side! But I don´t thnk we should kill the main grid (maybe later... :-) ). Creating a customized TOC view will high likely not solve the problems with the Actions that link to the false tables.
I made some attempts with JS. Mostly in the ItemType tab “Client Events” (event = onAfterNew). Problem: The events only react on changes in the new ItemType, not in Part. The whole issue is more in direction of Federation, which I have to deal with the next weeks anyway.
But maybe we should just think more radical.
In summary, the following functions are currently causing problems:
- Save As
- Lock / Unlock
- Structure Browser / Where Used (lower priority for me right now)
All of them have the same fundamental problem. The button actions link to the wrong tables. But they have one thing in common: All of them are CUI elements! (if you use SP9 or above).
Instead of modifying the ItemTypes or Methods, why not get rid of the standard Actions and use own CUI buttons that do the work right?
Something similar is e.g. done in the ItemType InBasket, where lock/unlock is replaced with claim/unclaim.
