(imported comment written by Lee Wei)
Is there any way to modify the relevance code generated by the query wizard and then regenerate the excel spreadsheet? I tried the session relevance editor, but it doesn’t appear to automatically split rows on the “$x$” delimiter like the query wizard does.
Hi Boyd,
No, there is not a break out to change the generated code right now before processing. I provided the code more as an FYI after fact. You are also correct that the delimiter is only used for the Excel Connector internally.
We have a few properties that use the same name (we have a lot of console operators, so conflicts sometimes happen). This creates unexpected results because the query wizard appears to use "bes property " and that will only return the first property of the same name. Is there any possibility that this could be reworked to go by property ID instead?
If you are using the latest version 3.2.0.0, I would have expected duplicate property names to be taken care of. When I detect duplicate names, I use the property ID construct as you have suggested. So why not just use IDs across the board? I tested using the ID versus "bes property " and the performance difference is startling. So I am left with deciding whether to resolve conflict, or to get performance. Isn’t the answer to everything almost always somewhere in the middle? So I use "bes property " when no duplicates, and IDs when there are duplicates.
Not to beat a dead horse, but this is another program that bug #38567 is affecting (http://forum.bigfix.com/viewtopic.php?pid=24212#p24212). Any news on when this bug will be fixed? It’s affecting a query that I wanted to generate for Installed Applications. I wanted to use Excel to make it easier to do sorting and grouping.
The bug is fixed in the next release, probably version 8.1 and code name “Euclid”. We expect this to be available in early February. Incidentally, the main purpose of this release is to rebrand everything as IBM. However, we do slip in a lot of fixes as appropriate.
Lee Wei