When I get some time i'll try and validate this. But my concern is that in the MIM Portal Schema -> creating an attribute, using it, then deleting the attribute, and creating one with the same name (different data type) breaks the MIM Reporting on SCSM.
You might ask, "why the hell would you do this?" My answer is, when trying to use said attribute "AccountExtension" in DEV as a String data type, doesn't bode well with RCDC that use integer like values in their UoCDropDownList options
E.g. :
<my:Control my:Name="AccountExtension" my:TypeName="UocDropDownList" my:Caption="{Binding Source=schema, Path=AccountExtension.DisplayName}" my:Description="{Binding Source=schema, Path=AccountExtension.Description}"
my:RightsLevel="{Binding Source=rights, Path=AccountExtension}">
<my:Options>
<my:Option my:Value="7" my:Caption="1 week" my:Hint="7 days"/>
<my:Option my:Value="14" my:Caption="2 weeks" my:Hint="14 days"/>
<my:Option my:Value="21" my:Caption="3 weeks" my:Hint="21 days"/>
<my:Option my:Value="30" my:Caption="1 month" my:Hint="30 days"/>
<my:Option my:Value="60" my:Caption="2 months" my:Hint="60 days"/>
<my:Option my:Value="90" my:Caption="3 months" my:Hint="90 days"/>
</my:Options>
<my:Properties>
<my:Property my:Name="Required" my:Value="{Binding Source=schema, Path=AccountExtension.Required}"/>
<my:Property my:Name="ValuePath" my:Value="Value"/>
<my:Property my:Name="CaptionPath" my:Value="Caption"/>
<my:Property my:Name="HintPath" my:Value="Hint"/>
<my:Property my:Name="ItemSource" my:Value="Custom"/>
<my:Property my:Name="SelectedValue" my:Value="{Binding Source=object, Path=AccountExtension, Mode=TwoWay}"/>
</my:Properties>
</my:Control>
When having this defined for a string data type for AccountExtension, it breaks the UocDropDownList behavior and gives unexpected results (like summary table showing a deletion when it's actually being set, and values not being translated to their corresponding
captions)
Therefore I deleted the attribute and turned it into an integer data type with the same name. Now my RCDC works, but Reporting broke.