Extension of Knowledge Class - Breaks the String Displays (Labels) on Knowledge Form

Question

Hi,
A strange issue - hopefully others have encountered this and not just me:
I'm in the process of adding an additional custom DatePicker to the Knowledge Form (KnowledgeMainForm).
When the Knowledge Class (System.Knowledge.Article) is extended, and a new custom property is created - it breaks the
default binding for all the Form's labels (Title, Description, Comments etc).
The normal behaviour is that the default Labels on a form initially appear as:
[Title:],
which then dynamically update to Title: - without the '[]' brackets.
In my case, these fields remain with the '[]' brackets - see img below:
*edit = unable to post images - the img link is:
https://www.dropbox.com/s/u976gj4qqoyf7zy/kaexample01.jpg
This only occurs when a new property is created in the Knowledge Class (string, datepicker, boolean, anything).
Scenario:
- Create new MP to host Knowledge Article (KA) Class extension in Authoring Tool
- Extend the KA class (System.Knowledge.Article / Knowledge Article) to that new MP
- Save new MP
- Create new property in new MP
- Save new MP and Seal MP
- Upload Sealed MP into SCSM 2012
I've been able to replicate this in 3 different instances of SCSM 2012
Has anyone encountered this and if not, is anyone able to replicate this:
I've included the new KA Class extension mp below.
The only customisation was to add an additional String property: Property_23.
<ManagementPack ContentReadable="true" SchemaVersion="2.0" OriginalSchemaVersion="1.1" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<Manifest>
<Identity>
<ID>SCSM_INT_KM_Classes</ID>
<Version>1.0.0.2</Version>
</Identity>
<Name>SCSM_INT_KM_Classes</Name>
<References>
<Reference Alias="System">
<ID>System.Library</ID>
<Version>7.5.8501.0</Version>
<PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
</Reference>
<Reference Alias="Console">
<ID>Microsoft.EnterpriseManagement.ServiceManager.UI.Console</ID>
<Version>7.5.2905.0</Version>
<PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
</Reference>
<Reference Alias="Alias_a3476d86_9ec5_4f6b_96b4_4d80e9d8bf69">
<ID>System.Knowledge.Library</ID>
<Version>7.5.2905.0</Version>
<PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
</Reference>
</References>
</Manifest>
<TypeDefinitions>
<EntityTypes>
<ClassTypes>
<ClassType ID="ClassExtension_46440273_5853_4402_9ed7_2b8cfbf1819a" Accessibility="Public" Abstract="false" Base="Alias_a3476d86_9ec5_4f6b_96b4_4d80e9d8bf69!System.Knowledge.Article" Hosted="false" Singleton="false" Extension="true">
<Property ID="Property_23" Type="string" AutoIncrement="false" Key="false" CaseSensitive="false" MaxLength="256" MinLength="0" Required="false" Scale="0" />
</ClassType>
</ClassTypes>
</EntityTypes>
</TypeDefinitions>
<Categories>
<Category ID="SCSM_INT_KM_Classes.Category" Value="Console!Microsoft.EnterpriseManagement.ServiceManager.ManagementPack">
<ManagementPackName>SCSM_INT_KM_Classes</ManagementPackName>
<ManagementPackVersion>1.0.0.0</ManagementPackVersion>
</Category>
</Categories>
<LanguagePacks>
<LanguagePack ID="ENA" IsDefault="true">
<DisplayStrings>
<DisplayString ElementID="SCSM_INT_KM_Classes">
<Name>SCSM_INT_KM_Classes</Name>
</DisplayString>
</DisplayStrings>
</LanguagePack>
<LanguagePack ID="ENU" IsDefault="false">
<DisplayStrings>
<DisplayString ElementID="SCSM_INT_KM_Classes">
<Name>SCSM_INT_KM_Classes</Name>
</DisplayString>
<DisplayString ElementID="ClassExtension_46440273_5853_4402_9ed7_2b8cfbf1819a">
<Name>Extension of Knowledge Article</Name>
<Description>Extension of class Knowledge Article</Description>
</DisplayString>
<DisplayString ElementID="ClassExtension_46440273_5853_4402_9ed7_2b8cfbf1819a" SubElementID="Property_23">
<Name>Property_23</Name>
</DisplayString>
</DisplayStrings>
</LanguagePack>
</LanguagePacks>
</ManagementPack>

Answer 1

Looks like you've found a legit form design bug in the KA form. I'm just guessing here, but I suspect that the form strings builder is choking on the extended class name.
Report it in connect
so we can <strike>blackmail</strike> ask the product team to try to get it fixed.