Search Large Properties Overview
then maybe Search Large Properties is for you.
![]() This model api tool allows you to select which object type(s) you want to search, secondly in which Library(s) and lastly what text string to search for within the found large properties. The results are loaded into a grid where their large properties can be viewed in more detail via double clicking the row and finally creating a Plex list of the found objects if desired. A enhancement request has been submitted (20034239-1: RUN ASSOCIATED EDITOR) to CA for a new model api method to run the associated object editor but we will have to wait and see on that one.. Add-In SettingLaunch application from Plex Add-In tool bar. If you are unable to see the Add-In toolbar from View, Toolbars… menu option choose Show toolbar.
Alert Message “Application Models Dialog”This message is to alert the developer to the current application models found in their template plex.in file (found in CA Plex installation directory). System Section: [Options] System Key: GMFileX which will make up the list of libraries shown in the combo box.
![]() If you don’t see all your models that you want termed as application models you need to copy GMFile settings from your user plex.ini file to your template plex.ini file found in the CA Plex installation directory.
It is important to have a complete list because not only does this define which models are application models but also the logic is anything else must be a shipped library
Search Criteria Entry
Understanding the Results
Edit Large PropertyBy double clicking the grid row you can view the large property in a re-sizeable multi line edit box where you can copy and paste into another editor for further investigation. See Edit Large Property
![]() Note: You can toggle between Full Large Property mode and Local Modifications mode which is useful when comparing a function large property between versions. Performance“Good things come to those who wait” is a phrase propounding the virtue of patience OR a pint of Guinness which ever you prefer
Searching can take hours if you search on Functions, Panels, Values simply because of the sheer number of them and sizes of the large properties. At least you can run a search in the back ground or conduct the search at the end of the day, but what you can be sure of is the results will not contain human error and you can arguably have greater confidence in the results in contrast to you picking through the model(s) yourself. You could argue with your boss that you were working after hours also ;) Silly jokes aside performance is not great but the results are, remembering you can enter 10 search arguments to be conducted at the same time OR you can look at exporting all the large properties as text files as snap shots of the model which then can be searched using windows desktop search or equivalent such as Total Commander Earlier versions of the model api did lead to gpfs which would have been very frustrating had a process been running for hours for it then to fail but version3.0 of the model api has greater error handling and reduced memory leaks etc Performance Matrix 2011
Performance Matrix 2014 - CPU 3.30GHz, 8GB RAM, 64-Bit Windows7
|