STIG | Structured Threat Intelligence Graph | Database library

Use the following, which makes use of calculated properties in combination with the Select-Object cmdlet applied to the results from your Group-Object call:

After 4-5 days of testing in my 2.024 line long page code, I finally found the reason why neighther checkboxes, radios and HREF´s did not work in the page .. reason : a damn JavaScript .. here is what blocked the mouse interaction:

Set a variable to the DIV before the form, and use that in the callback function.

I think @Rory McCrossan's idea to use closest() would work, the only issue is that if you have display none on the container with the button in it, then the button won't be visible to begin with.

You could adjust your markup a bit so that the Edit button and the form are both siblings of a common parent. That would allow you to use nextSibling() in vanilla JS, or next() in jQuery

You can use UNION ALL and WHERE predicates to decide which columns to add to the unpivot:

You shouldn't be using Response.Write unless you actually want the contents of the Response.Write statement to be displayed in your output, and you really need to start a new line for your conditional statements. Here's what you appear to be trying to do. I'm assuming that your SQL is correct and the only issue here is with your VBScript.

You need to use the push operator, here is the documentation: https://docs.mongodb.com/manual/reference/operator/update/push/

I think this should work:

Your JMESPath may very well be correct for one object but as its name implies, and as your debug: var=A.stdout_lines shows, stdout_lines is a list

So, you can do one of several things:

• recognize that your stdout_lines only contains one object and just feed that into json_query as {{ A.stdout_lines[0] | json_query(jmesquery) }}
• use the map filter to apply that same filter to every list item, with something like {{ A.stdout_lines | map("json_query", jmesquery) | list }}
• rewrite your JMESPath to apply that filter to the input list, akin to json_query("[*].configuration.AND THE REST HERE")

Those last two will naturally produce a different output shape, since they are lists of lists, and so it will look like [['ge-0/0/0']] when output, but they do have the advantage that if your stdout_lines ever does mysteriously start to contain more objects, they will be json_query-ied as expected

I suggest you to keep both filters separated, so you will be allowed to filter by date and by free-text simultaneously.

One advantage of this approach is that you can separate the localized date visualization from the standard date format which you are using to store the information in your database.

In my proposal below, to implement such a multiple filter, i have defined a custom data-attribute which will contain just only the date of the event - this is however, not strictly necessary - finally, i'm combining both search criteria in the filter callback of the filterable widget: