Adding a CI Build with powershell

Question

Hi,
Adding a CI Build (class: System.Build) with powershell to Service Manager 2012 R2 results in an error, but the Build is added with the correct properties. Here is the error message:
New-SCSMObject : Item has already been added. Key in dictionary: 'Notes'  Key being added: 'Notes'
At line:1 char:15
+ new-SCSMObject <<<<  (get-scsmclass System.Build) -propertyhashtable ($build)
    + CategoryInfo          : InvalidOperation: (Notes:ManagementPackProperty) [New-SCSMObject], ArgumentException
    + FullyQualifiedErrorId : property 'Notes' has already been added to collection,SMLets.NewSMObjectCommand
here is what I do:
$build=@{Displayname = "Test 1"}$build+=@{AssetStatus = "Deployed"}$build+=@{ObjectStatus = "Active"}$build+=@{Category = "Software"}$build+=@{Title = "Test"}$build+=@{Version = "1"}new-SCSMObject (get-scsmclass System.Build) -propertyhashtable ($build)
If I querry this Object with
get-scsmobject (get-scsmclass System.Build$) -Filter "Displayname -eq 'Test 1'"
I get the warning:
WARNING: The property 'Notes' already exists, skipping.
Exception: The member "Notes" is already present.
In my Build Form there are also two "notes" fields.
So my questions:
a) does this occur on other installations?
b) If not: any idea, where this comes from or how I could find out.
b) If yes: how do you deal with it?
tia
Patrick Wahlmüller

Answer 1

Hi Roman,
Thanks for your response.
Here are some findings: Smlets are not exact enough, because in the System.build Object there are 2 Notes Fields. One from the System.ConfigItem class and one from the System.Build class. I do not understand the reason for two notes fields, but the smlets
have a problem with it and the result is a warning. You can suppress this by
get-scsmobject (get-scsmclass
System.Build$)
-Filter "Displayname -eq 'Test 1'" -WarningAction silentlycontinue
(thanks to
Jason)
When I use native cmdlets:
Get-SCSMClassInstance -class $buclass -Filter 'Displayname -eq "Test 1"'
Results in two notes fields:
Notes
System.ConfigItem_Notes
But, I'll give it a try with native cmdlets, since the are part of the product.
But one question remains: Why are there two notes fields?
Patrick Wahlmüller