Parent Application Service added to a tag-based Application Service via CSDM wizard would be removed after service recalculationIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #6e9db4; } a:visited { font-size: 12pt; color: #7057C7; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: 500px !important; width: auto; height: auto; } } With Application Service Wizard you can create an application service to adhere to CSDM standards. You can select 'Tags' as the Service Population Method and scheduled job 'Populate Calculated Services' is executed once a day to map new tag-based services. From the Xandu release, the 'Parent Application Service' includes a class based filter and only Application Services records are displayed. Prior to the Xanadu release, Tag-based Service Maps could be added as the Parent Application Service to another Tag-based Service Maps. When this configuration was used, the Parent Application Service was removed from the CSDM wizard after the 'Populate Calculated Services' job was executed. Steps to reproduce: Navigate to module 'Application Service' under 'CSDM' application.Open CSDM wizard of a tag-based Application Service.At '1.Provide Basic Details' step, find ' Set Relationships' section and click 'Parent Application Service' tab.Move a Parent Application Service from 'Available' list to 'Selected' list.Click Update button to save the change.Now, navigate to module 'Scheduled Jobs' under 'System Definition' application.Search job with name 'Populate Calculated Services' and click 'Execute Now' button.Open the CSDM wizard of the same Application Service in step 2 again.Notice the 'Parent Application Service' added at step 4 is removed from 'Selected' list. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #6e9db4; } a:visited { font-size: 12pt; color: #7057C7; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: 500px !important; width: auto; height: auto; } } Vancouver & earlier releases Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #6e9db4; } a:visited { font-size: 12pt; color: #7057C7; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: 500px !important; width: auto; height: auto; } } This observed phenomenon is working as designed. The recalculation function implemented by Scheduled Job 'Populate Calculated Services' works as expected as it only includes tagged CIs or CIs brought from traversal rules. The reason is when using CSDM wizard to add Parent Application Service, it's trying to create a manual endpoint from parent service to child service.Because parent service is also a tag-based service, when recalculating service, endpoints for non-tagged / not-traversed CIs are removed. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #6e9db4; } a:visited { font-size: 12pt; color: #7057C7; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: 500px !important; width: auto; height: auto; } } If there is a business requirement to add a relationship between two tag-based services on a dependency map, you can manually create a CI relationship between these two tag-based services. In this case, the relationship will not be removed after recalculating the service. Navigate to 'CI Relationships' module.Click 'New' to create a new relationship CI.Select the tag-based Application Service for Parent and Child.Select Type of "Depends on::Used by" and save the record. These two tag-based services are shown on the dependency map.Run Scheduled Job 'Populate Calculated Services', the Parent Application Service won't be removed from CSDM wizard.