On a newly created Analysis Property, I look at a BigFix Computer in the Console and for that property, I get the result of 3 periods “…” for some clients (mostly AIX) when most all other clients give me the property output (a concatenated list of users). When I look at the analysis property result for that computer from Analyses > it shows "<error>"
with a hover over of “…”. When I look at the property result in WebReports, it returns "<not set>"
.
Is the 3 periods representing null in the console or some other error?
trn
July 26, 2021, 7:53pm
2
Not sure what is going on with Web Reports output, but in the console ‘…’ indicates a very long string.
You may get some joy by casting to rope, but results will be mixed (at best)
trn
July 26, 2021, 8:13pm
4
I value my sanity, so I have learned to keep clear!
It is well into the evening this side of the pond, so I have no examples with me, but it went along the lines of
rope (concatenation ";" of <whatever>)
I do recall getting more computers to display something other than the three dots, but it was not a bulletproof method.
I think I had more success by omitting common parts of the result and extending the relevance so I could discard some less useful results.
I’ll look tomorrow, but it was a while ago and I probably changed tack.
Web Reports, is better at displaying plural results than the console, so that may be another avenue to pursue.
@trn
Looking a massive string? Say no more!
rope ( concatenation of (sha256 of (it as string)) of integers in (1,1000))
The $64,000 Question is an American game show broadcast in primetime on CBS-TV from 1955 to 1958, which became embroiled in the 1950s quiz show scandals. Contestants answered general knowledge questions, earning money which doubled as the questions became more difficult. The final question had a top prize of $64,000, hence the "$64,000 Question" in the show's title.
The $64,000 Challenge (1956–1958) was its spin-off show, where contestants played against winners of at least $8,000 on The $64,0...
That said, the <not set>
error does not sound like a long string.
@cstoneba Please share your current relevance for your analysis?
1 Like
it seems to be working better now that I added “unique values of”.
1 Like