The data for this list is stored in a CSV file or an XML file. For just a simple, single selection list only the data file is required.<\/p>\n 2. Cached list.<\/strong><\/p>\n A configuration file (.ini) contains a command to generate the data file for this list (CSV or XML). The command is only executed ONCE per PrimalScript session and the data file is kept around. If you exit PrimalScript and start it again, the command will be executed again. This is very helpful for data that is dynamic, but does not change very often, e.g. available PowerShell modules.<\/p>\n 3. Dynamic list.<\/strong><\/p>\n A dynamic list executes the command you specified each time you invoke that list. The data format once again is either CSV or XML. A good example for this type of list is the \u201cfile\u201d example we provided. It lists the folder content of the directory the current file resides in. Since files get created, deleted or renamed all the time, this list has to always use current data.<\/p>\n Ok, so how does the data part work? You can use a CSV file if your data is single line items.<\/p>\n If you have only simple strings, then you do not even need to use commas. Just list your items one per line. The data file for this is also just a simple CSV file.<\/p>\n The first column contains the human readable string, the second column is an image index (we get to that later) and the third column is the data we want inserted when selected. You can use this translation for a lot of things to simplify selections, file names to full path names, weird SQL table names to more understandable terms e.g. \u201cCustomer Table\u201d to \u201cSQLQCust64527872NMA7657\u201d. If you have seen some SQL databases you know what I mean.<\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n An XML file can be used if the text you want to be inserted has more than one line. The functions.xml file is an example for this. Selecting an item inserts the corresponding code into your script.<\/p>\n![\"image\"](\"https:\/\/www.sapien.com\/blog\/wp-content\/uploads\/2015\/09\/image10.png\" "\\"image\\"")
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nData Format<\/strong><\/h2>\n
<\/a><\/p>\n
Sometimes you need to provide a little more information or translate some weird strings into something human readable. GUIDs used for DSC resources are a good example. I cannot remember that many numbers nor can I really distinguish them when I see them. So we show a translation that makes sense but insert the GUID when selected<\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n