• Replies 29 replies
  • Subscribers 12 subscribers
  • Views 64581 views
  • Users 0 members are here
Options
Related

How to create a new Part TOC menu item that does a custom search?

KalleAnka
Offline
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,
Parents
  • I made some tests with the instance_data property of the new ItemType and set it manually to "Part" via SQL. This seems to improve the locking behavior, but I am not sure what it actually does. You can use this query to find the current value in a new database view: 
    SELECT        KEYED_NAME, INSTANCE_DATA 
FROM            innovator.ITEMTYPE
WHERE        KEYED_NAME LIKE N'%YOUR_NEW_ITEMTYPE%')
    The following three also don´t work: - Save As - Where used - Structure browser All three link to the new ItemType and not to original Part. The behaviour makes sense. But especially "Save As" would be cool feature. In quite 90% of all cases our users use Save as to create a new Part. Right now the new ItemType is just a better version of SavedSearch. With "Save As" included it would become really powerful. Do you know, who gave the presentation about this topic? I was at ACE Europe 2016 but did not have time last year.
Reply
  • I made some tests with the instance_data property of the new ItemType and set it manually to "Part" via SQL. This seems to improve the locking behavior, but I am not sure what it actually does. You can use this query to find the current value in a new database view: 
    SELECT        KEYED_NAME, INSTANCE_DATA 
FROM            innovator.ITEMTYPE
WHERE        KEYED_NAME LIKE N'%YOUR_NEW_ITEMTYPE%')
    The following three also don´t work: - Save As - Where used - Structure browser All three link to the new ItemType and not to original Part. The behaviour makes sense. But especially "Save As" would be cool feature. In quite 90% of all cases our users use Save as to create a new Part. Right now the new ItemType is just a better version of SavedSearch. With "Save As" included it would become really powerful. Do you know, who gave the presentation about this topic? I was at ACE Europe 2016 but did not have time last year.
Children
No Data