There is a need to be able to write data acquired from wireless devices specifically, but others as well. If you know the registered AP, or a MAC address, and the device goes offline, so does the data. This new feature, in conjunction with USER DEFINED FIELDS, would allow faster troubleshooting of problematic network devices.
If you dont yet understand: A wireless CPE has been working fine, but suddenly goes down for unknown reason. If you could look in the custom fields (or additional named user defined fields), it would be infinitely helpful to open the device object up and see where the device was formerly connected to. Other useful info such as former signal strength, CCQ etc, could help determine if the device is experiencing wirelesss conditions that are different than normal for the connection. This happens often when a local WiFi AP is brought up by the well meaning customer, but right under where the CPE is mounted on the building. I know this happens–many times. It is also the source of interference that is not often considered, and Mikrotik gets blamed for ‘unstable’ connections, or ‘Nstreme’ doesnt work. Often it is nothing wrong with your AP, because of course you have hundreds of other extremely stable connections on that AP.
So lets have the ability to write to at least the custom fields, maybe via ros_command(), or maybe even develop dude_command(). Since there are only three custom fields, it limits what you can do, but it certainly would be a start. 