Inconsistent Behavior in Script Token Replacements for "Missing" Properties | Welcome

daviddhall · 2025-09-16T14:13:25.447000Z

Hi Folks -I'm on UIv4 and newish to LM: I chased this for way too many hours and realized that my optional/missing properties (and thus the tokens substituted in the scripts) seem to function differently in !posh (UIv3?) than in the DataSource modules "Test Active Discovery" section... AND in "Test Collection Script".If the property didn't exist:In !posh and the module's Collection, it seemed to basically substitute the token for an empty string.In the module's ActiveDiscovery, it seemed to leave them in place, untouched.This was a little difficult to figure out because the module's "Test Active Discovery" isn't helpful. It only displays successful key/value tables or a gentle ambiguous error "no instances found" popup. Also unfortunate, because the module's collection script "Test Script" seems to substitute them with an empty string - unlike what it does right above for Active Discovery.Perhaps I'm doing this wrong? Anyone else see this? Seems I need to check for empty/null strings AND also the actual token strings before proceeding? This was unnecessarily difficult to figure out on my own. I'm still hopeful there is a "better way" (TM) for debugging and building modules that I'll miraculously stumble upon. (I'd love any tips)I'll post a follow up to this with my simple test script and the Outputs I saw.

Discussions

Inconsistent Behavior in Script Token Replacements for "Missing" Properties | Welcome | LogicMonitor Community