SOLVED

Add-PnPFieldFromXml - Assistance

%3CLINGO-SUB%20id%3D%22lingo-sub-2033053%22%20slang%3D%22en-US%22%3EAdd-PnPFieldFromXml%20-%20Assistance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2033053%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENew%20here%2C%20far%20from%20being%20any%20kind%20of%20developer%20but%20always%20looking%20to%20learn.%26nbsp%3B%20This%20time%20around%20for%20me%20its%26nbsp%3BAdd-PnPFieldFromXml%20and%20specifically%20adding%20multiple%20site%20content%20types.%3C%2FP%3E%3CP%3EAs%20I'm%20learning%20SharePoint%20rather%20than%20keep%20manually%20entering%20the%20same%20Content%20types%20over%20and%20over%20in%20new%20team%20site%20iterations%20I%20wanted%20to%20run%20a%20script%20and%20add%20the%20required%20Content%20Types.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20I%20run%20the%20below%20and%20try%20and%20run%20the%20Add-PnPFieldFromXml%20for%20another%20field%20I%20receive%20an%20error%20%22dd-PnPFieldFromXml%20%3A%20The%20local%20device%20name%20is%20already%20in%20use.%20(Exception%20from%20HRESULT%3A%200x80070055)%22%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-applescript%22%3E%3CCODE%3E%24docownXml%20%3D%20'%3CFIELD%20type%3D%22Choice%22%20displayname%3D%22Document%20Owner%22%20required%3D%22TRUE%22%20group%3D%22Some%20Group%20Name%22%20id%3D%22%7BAn%20ID%7D%22%20fillinchoice%3D%22TRUE%22%20name%3D%22Some%20Name%22%20description%3D%22%22%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3CCHOICES%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3CCHOICE%3EChoice%201%3C%2FCHOICE%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3CCHOICE%3EChoice%202%3C%2FCHOICE%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3CCHOICE%3EChoice%203%3C%2FCHOICE%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3CCHOICE%3EChoice%204%3C%2FCHOICE%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3C%2FCHOICES%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3CDEFAULT%3E%3C%2FDEFAULT%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3C%2FFIELD%3E'%0A%0AAdd-PnPFieldFromXml%20-FieldXml%20%24docownXml%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20assuming%20running%20multiple%26nbsp%3BAdd-PnPFieldFromXml%20in%20a%20script%20is%20not%20supported%20or%20I'm%20missing%20something%3F%3C%2FP%3E%3CP%3EDoes%20anyone%20have%20any%20suggestions%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20note%2C%20I%20do%20not%20have%20access%20to%20the%20%2Fcontenttypehub%2F.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20and%20Happy%20New%20Year!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2034544%22%20slang%3D%22en-US%22%3ERe%3A%20Add-PnPFieldFromXml%20-%20Assistance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2034544%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F918507%22%20target%3D%22_blank%22%3E%40cawool%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eit%20is%20definitely%20supported%2C%20maybe%20you%20have%20a%20column%20already%20with%20the%20same%20name%3F%3C%2FP%3E%3CP%3Ei%20have%20used%26nbsp%3BAdd-PnPFieldFromXml%26nbsp%3B%20for%20various%20types%20and%20its%20is%20working%20for%20me%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2034638%22%20slang%3D%22en-US%22%3ERe%3A%20Add-PnPFieldFromXml%20-%20Assistance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2034638%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F918507%22%20target%3D%22_blank%22%3E%40cawool%3C%2FA%3E%26nbsp%3BHi%2C%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EHave%20you%20tried%20Get-PnPProvisioningTemplate%3F%20It%20simplifies%20your%20work%20even%20further%20with%20much%20more%20possibilites%20in%20deploying%20conten%20types%2C%20lists%2C%20pages%20etc.%3CBR%20%2F%3E%3CBR%20%2F%3EYours%20sincerely%2C%3CBR%20%2F%3EAref%20Halmstrand%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2035461%22%20slang%3D%22en-US%22%3ERe%3A%20Add-PnPFieldFromXml%20-%20Assistance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2035461%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F142422%22%20target%3D%22_blank%22%3E%40Valeras%20Narbutas%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EIts%20not%20that%20I%20cannot%20add%20a%20field%20type%2C%20I%20cannot%20add%20multiple%20field%20types%20using%26nbsp%3BAdd-PnPFieldFromXml.%26nbsp%3B%20I'm%20trying%20to%20add%20three%20field%20types%2C%20it%20adds%20the%20first%20one%20but%20fails%20on%20the%20next%20ones.%26nbsp%3B%20If%20I%20selectively%20only%20run%20the%202nd%20or%203rd%26nbsp%3BAdd-PnPFieldFromXml%20it%20works%20fine%20so%20I%20know%20the%20fields%20dont%20already%20exist%20plus%20they%20have%20unique%20names%20different%20from%20the%20out%20of%20the%20box%20ones.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20be%20clear%20I'm%20running%20three%26nbsp%3BAdd-PnPFieldFromXml%20in%20a%20script%20as%20I%20dont%20believe%20you%20can%20add%20all%20the%20required%20field%20types%20using%20one%20XML.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERelevant%20part%20of%20script%20below%3A%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-applescript%22%3E%3CCODE%3E%24docownXml%20%3D%20'%3CFIELD%20type%3D%22Choice%22%20displayname%3D%22Document%20Owner%22%20required%3D%22TRUE%22%20group%3D%22some%20group%20name%22%20id%3D%22%7Ban%20ID%7D%22%20fillinchoice%3D%22TRUE%22%20name%3D%22a%20name%22%20description%3D%22%22%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3CCHOICES%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3CCHOICE%3EChoice%201%3C%2FCHOICE%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3CCHOICE%3EChoice%202%3C%2FCHOICE%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3CCHOICE%3EChoice%203%3C%2FCHOICE%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3CCHOICE%3EChoice%204%3C%2FCHOICE%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3C%2FCHOICES%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3CDEFAULT%3E%3C%2FDEFAULT%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3C%2FFIELD%3E'%0AAdd-PnPFieldFromXml%20-FieldXml%20%24docownXml%0A%0A%24appnameXml%20%3D%20'%3CFIELD%20type%3D%22Choice%22%20displayname%3D%22Application%20Name%22%20required%3D%22TRUE%22%20group%3D%22some%20group%20name%22%20id%3D%22%7Ban%20ID%7D%22%20fillinchoice%3D%22TRUE%22%20name%3D%22a%20name%22%20description%3D%22%22%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3CCHOICES%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3CCHOICE%3EChoice%201%3C%2FCHOICE%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3CCHOICE%3EChoice%202%3C%2FCHOICE%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3CCHOICE%3EChoice%203%3C%2FCHOICE%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3CCHOICE%3EChoice%204%3C%2FCHOICE%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3CCHOICE%3EChoice%205%3C%2FCHOICE%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3CCHOICE%3EChoice%206%3C%2FCHOICE%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3CCHOICE%3EChoice%207%3C%2FCHOICE%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3CCHOICE%3EChoice%208%3C%2FCHOICE%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3C%2FCHOICES%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3CDEFAULT%3E%3C%2FDEFAULT%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3C%2FFIELD%3E'%0A%0AAdd-PnPFieldFromXml%20-FieldXml%20%24appnameXml%0A%0A%24doccredate%20%3D%20'%3CFIELD%20type%3D%22DateTime%22%20format%3D%22DateOnly%22%20displayname%3D%22Document%20Creation%20Date%22%20required%3D%22TRUE%22%20group%3D%22some%20group%20name%22%20id%3D%22%7Ban%20iD%7D%22%20name%3D%22a%20name%22%20description%3D%22%22%3E%3C%2FFIELD%3E'%0AAdd-PnPFieldFromXml%20-FieldXml%20%24doccredate%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20the%20script%20tries%20to%20run%20the%20second%20(and%20third)%20Add-PnPFieldFromXml%20it%20fails%20with%20the%20below%20error%3A%3C%2FP%3E%3CP%3E%3CSPAN%3Eadd-PnPFieldFromXml%20%3A%20The%20local%20device%20name%20is%20already%20in%20use.%20(Exception%20from%20HRESULT%3A%200x80070055)%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EHope%20this%20makes%20sense.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThanks%2C%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2036337%22%20slang%3D%22en-US%22%3ERe%3A%20Add-PnPFieldFromXml%20-%20Assistance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2036337%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F918507%22%20target%3D%22_blank%22%3E%40cawool%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFirst%20of%20all%2C%26nbsp%3B%3CA%20title%3D%22Add-PnPFieldFromXml%22%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fsharepoint-pnp%2Fadd-pnpfieldfromxml%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EAdd-PnPFieldFromXml%3C%2FA%3E%26nbsp%3Bcmdlet%20adds%26nbsp%3B%3CSPAN%3Ea%20%3CSTRONG%3Efield%3C%2FSTRONG%3E%20to%20a%20list%20or%20as%20a%20site%20column%20based%20upon%20a%20CAML%2FXML%20field%20definition%20and%20not%26nbsp%3B%3CSTRONG%3Econtent%20type%3C%2FSTRONG%3E.%20Using%20this%20command%20you%20can%20add%20multiple%20site%20columns%2Ffields%20to%20a%20single%20content%20type.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EYou%20are%20getting%20this%20exception%20because%20there%20is%20already%20a%20field%20with%20name%20%22local%20device%22%20on%20your%20SharePoint%20site.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3E%3CSPAN%3ESo%2C%20I%20will%20suggest%20you%20to%20use%20%3CSTRONG%3Eunique%3C%2FSTRONG%3E%20DisplayName%2C%20Name%20and%20ID%20in%20CAML%20every%20time%20you%20are%20using%26nbsp%3BAdd-PnPFieldFromXml%26nbsp%3Bcmdlet.%3C%2FSPAN%3E%3C%2FP%3E%3CHR%20%2F%3E%3CP%3EPlease%20click%20%3CSTRONG%3EMark%20as%20Best%20Response%3C%2FSTRONG%3E%20if%20my%20post%20helped%20you%20to%20solve%20your%20issue.%20This%20will%20help%20others%20to%20find%20the%20correct%20solution%20easily.%20It%20also%20closes%20the%20item.%20If%20the%20post%20was%20useful%20in%20other%20ways%2C%20please%20consider%20giving%20it%20%3CSTRONG%3ELike%3C%2FSTRONG%3E.%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2036799%22%20slang%3D%22en-US%22%3ERe%3A%20Add-PnPFieldFromXml%20-%20Assistance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2036799%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F373269%22%20target%3D%22_blank%22%3E%40ganeshsanap%3C%2FA%3E%26nbsp%3BHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20should%20apologies%20first%20for%20mixing%20up%20my%20terminology%2C%20not%20sure%20why%20I%20did%20that%20but%20you%20knew%20what%20I%20was%20referring%20to%20so%20thanks.%3C%2FP%3E%3CP%3EI%20will%20go%20away%20and%20give%20this%20another%20look%20and%20take%20on%20your%20comments%20and%20hopefully%20post%20back%20with%20success%20asap.%26nbsp%3B%20I%20think%20I%20see%20my%20problem%20now.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi,

 

New here, far from being any kind of developer but always looking to learn.  This time around for me its Add-PnPFieldFromXml and specifically adding multiple site content types.

As I'm learning SharePoint rather than keep manually entering the same Content types over and over in new team site iterations I wanted to run a script and add the required Content Types.

 

If I run the below and try and run the Add-PnPFieldFromXml for another field I receive an error "dd-PnPFieldFromXml : The local device name is already in use. (Exception from HRESULT: 0x80070055)"

$docownXml = '<Field Type="Choice" DisplayName="Document Owner" Required="TRUE" Group="Some Group Name" ID="{An ID}" FillInChoice="TRUE" Name="Some Name" Description="">
                <CHOICES>
                    <CHOICE>Choice 1</CHOICE>
                    <CHOICE>Choice 2</CHOICE>
                    <CHOICE>Choice 3</CHOICE>
                    <CHOICE>Choice 4</CHOICE>
                </CHOICES>
                <Default></Default>
                </Field>'

Add-PnPFieldFromXml -FieldXml $docownXml

 

I'm assuming running multiple Add-PnPFieldFromXml in a script is not supported or I'm missing something?

Does anyone have any suggestions?

 

To note, I do not have access to the /contenttypehub/.

 

Thanks and Happy New Year!

8 Replies

@cawool 

it is definitely supported, maybe you have a column already with the same name?

i have used Add-PnPFieldFromXml  for various types and its is working for me

@cawool Hi,


Have you tried Get-PnPProvisioningTemplate? It simplifies your work even further with much more possibilites in deploying conten types, lists, pages etc.

Yours sincerely,
Aref Halmstrand

@ValerasNarbutas 

Hi,

Its not that I cannot add a field type, I cannot add multiple field types using Add-PnPFieldFromXml.  I'm trying to add three field types, it adds the first one but fails on the next ones.  If I selectively only run the 2nd or 3rd Add-PnPFieldFromXml it works fine so I know the fields dont already exist plus they have unique names different from the out of the box ones.

 

To be clear I'm running three Add-PnPFieldFromXml in a script as I dont believe you can add all the required field types using one XML.

 

Relevant part of script below:

$docownXml = '<Field Type="Choice" DisplayName="Document Owner" Required="TRUE" Group="some group name" ID="{an ID}" FillInChoice="TRUE" Name="a name" Description="">
                <CHOICES>
                    <CHOICE>Choice 1</CHOICE>
                    <CHOICE>Choice 2</CHOICE>
                    <CHOICE>Choice 3</CHOICE>
                    <CHOICE>Choice 4</CHOICE>
                </CHOICES>
                <Default></Default>
                </Field>'
Add-PnPFieldFromXml -FieldXml $docownXml

$appnameXml = '<Field Type="Choice" DisplayName="Application Name" Required="TRUE" Group="some group name" ID="{an ID}" FillInChoice="TRUE" Name="a name" Description="">
                <CHOICES>
                    <CHOICE>Choice 1</CHOICE>
                    <CHOICE>Choice 2</CHOICE>
                    <CHOICE>Choice 3</CHOICE>
                    <CHOICE>Choice 4</CHOICE>
                    <CHOICE>Choice 5</CHOICE>
                    <CHOICE>Choice 6</CHOICE>
                    <CHOICE>Choice 7</CHOICE>
                    <CHOICE>Choice 8</CHOICE>
                </CHOICES>
                <Default></Default>
                </Field>'

Add-PnPFieldFromXml -FieldXml $appnameXml

$doccredate = '<Field Type="DateTime" Format="DateOnly" DisplayName="Document Creation Date" Required="TRUE" Group="some group name" ID="{an iD}" Name="a name" Description=""/>'
Add-PnPFieldFromXml -FieldXml $doccredate

 

When the script tries to run the second (and third) Add-PnPFieldFromXml it fails with the below error:

add-PnPFieldFromXml : The local device name is already in use. (Exception from HRESULT: 0x80070055)

 

Hope this makes sense.

 

Thanks,

@cawool 

First of all, Add-PnPFieldFromXml cmdlet adds a field to a list or as a site column based upon a CAML/XML field definition and not content type. Using this command you can add multiple site columns/fields to a single content type.

 

You are getting this exception because there is already a field with name "local device" on your SharePoint site.

 

So, I will suggest you to use unique DisplayName, Name and ID in CAML every time you are using Add-PnPFieldFromXml cmdlet.


Please click Mark as Best Response if my post helped you to solve your issue. This will help others to find the correct solution easily. It also closes the item. If the post was useful in other ways, please consider giving it Like.

 

@ganeshsanap Hi,

 

I should apologies first for mixing up my terminology, not sure why I did that but you knew what I was referring to so thanks.

I will go away and give this another look and take on your comments and hopefully post back with success asap.  I think I see my problem now.

@cawool 

Hi,

I managed to get this working. It was the GUID that wasn't generating a unique ID each time. Fixed it with:
$FieldID = New-Guid

However, for some reason adding a custom DateTime field always results in the below error no matter what the GUID is/starts with.
Add-PnPFieldFromXml : Name cannot begin with the '4' character, hexadecimal value 0x34.

I can manually create it no problem and was hoping to use Get-PnPField with -Includes "SchemaXML" to see resultant XML but it doesn't like that... at all.

best response confirmed by cawool (Occasional Contributor)
Solution

@cawool 

 

Glad my approach worked for your original question.

 

For Current Error

You are getting this error because whenever you create any field it converts the number and special characters in Name attribute to hexadecimal values to store it as internal name of your field. Maybe it is not liking the '4' character at the beginning of field name.

 

So, you can pass the different DisplayName (which you see in list view and list forms) and Name (internal name) in your XML like:

 

 

$docCreationDate = '<Field Type="DateTime" Format="DateOnly" DisplayName="Document Creation Date" Required="TRUE" Group="some group name" ID="{an iD}" Name="DocCreationDate" Description=""/>'
Add-PnPFieldFromXml -FieldXml $docCreationDate

$fourDate = '<Field Type="DateTime" Format="DateOnly" DisplayName="4 Date" Required="TRUE" Group="some group name" ID="{an iD}" Name="FourDate" Description=""/>'
Add-PnPFieldFromXml -FieldXml $fourDate

 

 


Please click Mark as Best Response if my post helped you to solve your issue. This will help others to find the correct solution easily. It also closes the item. If the post was useful in other ways, please consider giving it Like.

 

@ganeshsanap Hi,

 

We have success!  Not sure what was going on before but my DisplayName did not have a number in it even though it was complaining about it.  I deleted the site and started a fresh and made sure my code was clean and as it should be.

 

Thank you for your assistance, much appreciated!