#1721 Locked attribute in one Synchro Data Source prevents other Synchro Data Source to update it
Hi team,
I think I found a bug with data synchronization.
Just FYI I am using TeemIP extension, but I believe this is not related to this extension, but it is a common issue.
I am administering Server class and IPv4Address class with data synchronization.
I don't want regular users to be able to modify Server objects in iTop, objects which have been imported to iTop with data synchronization. So that applies also to Management IP field.
In the synchro data source for class Server, on Attributes tab, I have Update Policy for managementip_id field set to Locked.
In the synchro data source for class IPv4Address, on Properties tab, I have Delete Policy set to Delete.
I sync the IPs between external source and iTop with synchro data source for class IPv4Address.
Then I use the IDs of just imported IPs in the synchro data source for class Server and let the synchro run.
This works just as expected, all good.
The problem comes when some IP address dissapears from my external source.
I run the synchro for IPs and the synchro is trying to delete the IP object because of the Deletion Policy. I would expect iTop to detach this IP from Server object and delete it from the database.
But instead, the synchro return a deletion error: "Unable to delete the destination object: The field Management IP is not writable because it is mastered by the data synchronization. Value not set."
I understand this is happening, because the IP object is used in Server object and I am trying to update the Server object, which is under control of different synchro data source, and it has the Update Policy for managementip_id field set to Locked.
If I change the settings of Server DS, when I set Update Policy for managementip_id field to Unlocked, my synchronization works as expected - detaches the IP from Server object and removes the IP object from iTop.
But I think this is a bug.
The Update Policy on Attributes tab should affect only human iTop users. It should not prevent data synchronization to update field. Because right now, to have my synchronization work, I need to unlock the managementip_id field for everybody, hence allowing the human iTop users freely update the IP address of a Server although it should be managed ONLY by data synchronization.
Is this something you would consider a bug and hopefully fixing it?
Thanks,
Martin
Is there anybody aware of this issue?
It would be great to get some feedback as I believe this is a significant synchrnization error in iTop.