# OPC UA MonitoredItem Service Set - Filter **URL:** \ **Category:** Ignition\ **Created:** [May 19, 2026, 5:30pm UTC](https://forum.inductiveautomation.com/t/opc-ua-monitoreditem-service-set-filter/115605 "2026-05-19T17:30:00Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [May 19, 2026, 7:17pm UTC](https://forum.inductiveautomation.com/t/opc-ua-monitoreditem-service-set-filter/115605/4 "2026-05-19T19:17:29Z")
Yeah, not currently possible. But discussed. See this topic: > [@OPC UA Get node attributes by Node Id](https://forum.inductiveautomation.com/t/opc-ua-get-node-attributes-by-node-id/114719/3): > > I’ve always wanted to add system.opcua.readAttribute and system.opcua.writeAttribute, but even with its status as something of a wishlist item of mine, it hasn’t been able to claw its way into this world. I think in part because the reality of the implementation is it will be ugly, like the BACnet read/write raw scripting functions, where Milo types have to be injected into the system.opcua namespace so they can be referenced by scripts using these functions, particularly writeAttribute. The target server would have to publish the nodes to implement the filter. --- _[View the full topic](https://forum.inductiveautomation.com/t/opc-ua-monitoreditem-service-set-filter/115605)._