Export Selected Large Property


This tool allows a developer to select an object(s) (must have a large property associated) within the Object/Dependency browser and export the large properties as a text file.

LIMITATION: When using the substitute/replacement markers in the directory please note the configuration is gathered about the host model only. So if you choose a library object it will exported under the host model config and not its own config in the local model. There is not a model api ATOW to get an objects config according to its owning model. 


Adding Add-In

This allows you to launch the tool from CA Plex. For Object Browser Integration the client application must be registered as a Plex Add-In with certain macros used to specify how the selected objects are to be passed in as parameters.

$AllRefs -  Substitutes the internal references to the selected object(s) which is the recommended macro for Model API clients written with Plex itself. See Add_Add-In_Dialog.htm

Once the Add-In is completed including the macro parameter the application becomes available only via the right context menu of the Object Browser and now Dependency Browser (CA Case: 19644002-1: add-ins for dependecybrowser)


  • Launch tool from Object/Dependency Browser
To export object large properties, right-click an object in the Object/Dependency Browser and choose Create LP Export File [Stella Tools] from the Add-In Menu. Remember you can multi select from the Object/Dependency browser to export multiple large properties to separate files.
  • Export file destination is fetched from StellaCrtLPExportFile.ini. You may add the following substitute markers in your ini file setting which will be replaced at runtime with the current host model's configuration: $version $variant $language $level $hostmdlname
  • Choose to Export Full or Local modifications by ini file setting

Summary Message

If the object selected has no large property associated or an object that is virtual (not Real) you will get the following Stella tools generated CA Plex log messages


You will notice the file names have an unusual format: 
  • Source codeÐ ACTIVEçµµµImage_.Scripts.Image_LoadImage.TXT
  • MessageÐ FIELDSçCheckFieldFailed.TXT
  • FunctionÐ VALIDATEçMeta.TXT
In order to import the files back into CA Plex as a list, the files must be unique and record which object the large property belongs to in which library. CA Plex allows object names to contain characters that are prohibited in windows file names so the following source code is used to substitute the characters with a reserved character. Apologies to CA Plex sites that legitimately use these reserved characters in the object names but it will cause the import to fail.

So for example WSYBASE\AttributeString.onload="Init();" is created as a file called ValueÐ WSYBASEçAttributeString.onload=ðInit();ð.TXT