During our setup and learning phase, we tried lots of things and manually added properties to existing services. If I delete one of these custom properties, then it vanished for all services. If then for whatever reason, the service template is triggered, these deleted properties reappear even though they are not in the Properties section of "Generated service" in the service template.
Do you know why and how I can stop this from happening?
Hi Ben,
thank you for your question. Yes, I delete the custom property (gear icon – delete).
Daniel
Hi Ben,
I’ve been able to narrow it down now. The properties are only removed in the Service.xml of the service I am currently on while deleting them. The properties are hidden from view on all services but they remain in the Service.xml of the other services. If the service template is triggered on one of the services with the properties still present in the service.xml, then they are reinstated. That would explain why the values are not lost. 293 of 343 Services have the deleted properties in the Service.xml. I was able to find them by searching the content for a certain word. It was easy in this case because I had named one of the properties dan_test. This is not creating any issues but I would like to clean it up. Have you ever seen this behaviour before? We are currently on 10.00.13 but this started much earlier.
Hi Daniel,
Could you check in your service Template if you there also deleted the property assignment in the 'Generated Service' tab? If in the Service Template you give a value to a property, and the property does not exist. Then the property will be created.
This might be the reason why you see the property reappear after the Service Template gets triggered.
Hi Stacey,
the reappearing properties are not listed in the Properties section of the Generated service tab, that is what is confusing me. I most likely already checked the service template XML if the values are still there but not visible on the cube but I’ll double-check, just to be on the safe side.
The properties are not in the service template.xml but…. they are in the service.xml inside the folders of the services even though they have been removed from the service and are not visible. So, now I know the “HOW” but not the “WHY”.
Hi Daniel,
In this case it seems to best flag this item to techsupport. Then they can further investigate if this use case can be repeated and if a small fix in the software is needed.
Hi Daniel,
On your first remark "If I delete one of these custom properties, then it vanished for all services.": this is the expected behavior.
Properties are stored in sets per item type. So views, elements, and services each have a distinct set of properties. Properties of a view are available for all views, properties of elements are available for all elements, and properties of services are available for all services.
So deleting a service property will indeed delete it for all services, adding a service property will make it available for all services. If you want to remove a property from one service but not the other, you should only clear the value but not delete the property itself.
Hello Michiel,
thank you for your answer.
Yes, I am aware, sorry that I didn’t mention that. I was trying to communicate that the removal itself works fine and as expected but for whatever reason, the deletion is somehow undone if the service template is triggered. The properties even have the values back.
It is not creating a problem but can cause confusion because many unused values are present, making the tab a little messy.
Hi Daniel, just for sake of clarity. When you say that you delete a Custom Property, you refer to the Custom Property itself and not the value of a Custom Property on one of the services? Correct?