Comments
-
Yea, that's kind of what I figured. That's what I get for trying to do things the "right" way vs direct DB manipulation. Want me to submit any kind of bug thing anywhere (SW Technical Support, GIT, etc)?
-
Bumping this to see if anyone has any other method of doing this that won't break everything. To simplify: 1 SAM template with 3 components (the real one has many more, again, simplification). After applying template to node, I need to disable component 1 and 2, and enable component 3 on Node 1...disable component 1 and 3,…
-
Do you have another method of doing this? I'm all ears, as I couldn't find any documentation stating another method leveraging REST.
-
It's nothing special, just a typical update based on the REST documentation. As you can pull the SWIS URI like any other object, and update it like any other object (at least assumed), what would be unusual or anything about it?
-
Unfortunate, but thanks.
-
I replied, but these lovely forums marked it as spam for whatever reason. In summary, until the write up gets brought back: 1) Not on the template level, on the assigned to node level. 2) Both methods, direct update using component's URI and the BulkUpdate using the component's URI were pulled…
-
No, the assigned template level. Long story short...template will have numerous components, all disabled except for a templated component. What I'm looking to do is effectively a true up script. Hit the device I'm bringing into SW to see what elements it has, once I have that, script assigns the template to the node (no…
-
That's what I was afraid of, that this wasn't isolated...
-
Is there any update on this? Looking at SWQL Studio, my assumption is that this is still a no unfortunately.
