Modern Library - Not able to Customize NewForm.aspx

%3CLINGO-SUB%20id%3D%22lingo-sub-39718%22%20slang%3D%22en-US%22%3EModern%20Library%20-%20Not%20able%20to%20Customize%20NewForm.aspx%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-39718%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20SharePoint%20Folks%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20facing%20an%20issue%20with%20Modern%20Document%20Library.%20As%20a%20part%20of%20my%20customization%2C%20I%20have%20to%20customize%20newform%20with%20tabbing%20becasue%20large%20number%20of%20columns.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20piece%20of%20work%20I%20have%20done%20earlier%20with%20classic%20version.%20But%20with%20the%20new%20changes%20from%20Microsoft%20on%20Document%20Libraries%2C%20now%20I%20am%20not%20able%20to%20edit%20NewForm.aspx%20page%20and%20without%20that%20I%20wont%20be%20able%20to%20do%20any%20customizations.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20came%20across%20an%20article%20in%20this%20forum%20where%20they%20have%20announced%20the%20Field%20level%20JSLink%20implementation.%20Does%20this%20implies%20Client%20Side%20Rendering(CSR)%20is%20disabled%20for%20forms%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20any%20solution%20or%20workaround%20for%20this%20scenario%3F%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHappy%20Coding!!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESri%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-39718%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2013%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDocument%20Library%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-380379%22%20slang%3D%22en-US%22%3ERe%3A%20Modern%20Library%20-%20Not%20able%20to%20Customize%20NewForm.aspx%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-380379%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F189854%22%20target%3D%22_blank%22%3E%40Robin%20Nilsson%3C%2FA%3E%2C%26nbsp%3BYeah%2C%20I%20was%20going%20to%20use%20PowerApps%2C%20but%20it's%20a%20GCC%20tenant%20(which%20doesn't%20have%20PowerApps%20yet%2C%20it's%20been%20delayed%20at%20least%206%20months%20beyond%20when%20it%20was%20supposed%20to%20be%20available...another%20story...)%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20for%20calculated%20fields%2C%20agree%2C%20it%20makes%20sense%20it%20shouldn't%20be%20on%20New%2FEdit%20since%20it's%20calculated.%20It%20just%20doesn't%20show%20on%20Display%20either...probably%20due%20to%20the%20face%20that%20Display%20appears%20to%20be%20driven%20off%20the%20Edit%20property.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20Robin!%3C%2FP%3E%3CP%3EBen%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-380329%22%20slang%3D%22en-US%22%3ERe%3A%20Modern%20Library%20-%20Not%20able%20to%20Customize%20NewForm.aspx%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-380329%22%20slang%3D%22en-US%22%3EGreat%20work!%20I%20confirm%20your%20analysis%20on%20Display%20form%20not%20acting%20as%20expected%20when%20using%20the%20.SetShowInDisplayForm%20property%20of%20a%20field.%20I'd%20consider%20that%20a%20bug%2C%20actually%20-%20if%20there's%20a%20reason%20to%20not%20display%20something%2C%20it%20should%20be%20honored.%20I%20don't%20train%20much%20on%20using%20the%20info%20panel%20-%20I'm%20torn%20by%20its%20ease%20of%20use.%20But%20if%20a%20list%20uses%20PowerApps%20to%20interact%20with%20a%20list%2C%20the%20info%20panel%20is%20a%20way%20to%20get%20around%20any%20processing%20the%20PowerApps%20might%20do%2C%20which%20could%20cause%20problems.%3CBR%20%2F%3E%3CBR%20%2F%3ECalculated%20fields%20have%20always%20been%20like%20that%20in%20SharePoint%20-%20only%20available%20on%20the%20Display%20Form.%20When%20I've%20needed%20to%20show%20it%20on%20an%20edit%20form%20I%20used%20customization%20to%20pull%20the%20field%20value%20and%20display%20it.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-380176%22%20slang%3D%22en-US%22%3ERe%3A%20Modern%20Library%20-%20Not%20able%20to%20Customize%20NewForm.aspx%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-380176%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F189854%22%20target%3D%22_blank%22%3E%40Robin%20Nilsson%3C%2FA%3E%26nbsp%3BThanks%2C%20I%20was%20using%20the%20method%20you%20outlined%20already%2C%20I%20just%20needed%20to%20do%20little%20more%20testing.%20I%20was%20changing%20too%20many%20properties%20at%20once%20when%20I%20was%20originally%20testing.%20The%20New%2FEdit%20does%20appear%20to%20work%2C%20however%2C%20the%20Edit%2FDisplay%20is%20where%20it%20all%20falls%20apart.%20I%20took%20the%20time%20to%20go%20through%20all%20the%20configurations%20and%20this%20is%20what%20you%20get%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20402px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F95542i3C3E079AECE56D4C%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%222019-03-21_12-57-39.png%22%20title%3D%222019-03-21_12-57-39.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EEssentially%2C%20Display%20follows%20along%20with%20the%20Edit%20property%20rather%20than%20the%20Display.%20I'm%20assuming%20this%20is%20due%20to%20the%20quick%20edit%20in%20the%20information%20pane.%20But%20what%20would%20make%20sense%20it%20to%20only%20show%20the%20%22Display%22%20fields%20in%20the%20information%20pane%2C%20and%20the%20%22Edit%22%20fields%20once%20you%20click%20%22Edit%20All%22.%20So%2C%20when%20dealing%20with%20Modern%20UI%2C%20you%20really%20only%20have%20New%20and%20Edit.%20Display%20is%20just%20ignored%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%2C%20I%20realized%20one%20of%20the%20fields%20I%20was%20using%20was%20a%20calculated%20column.%20Those%20actually%20just%20ignore%20all%20the%20rules%20and%20won't%20show%20at%20all.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20could%20maybe%20make%20the%20argument%20that%20you%20don't%20need%20Display%2C%20as%20you%20can%20display%20everything%20you%20need%20in%20the%20list%20view%20and%20should%20only%20click%20on%20the%20info%20panel%20if%20you%20need%20to%20make%20a%20change.%20This%20may%20be%20the%20route%20I%20try.%20However%2C%20there%20are%20also%20times%20when%20you%20want%20a%20set%20of%20the%20fields%20in%20the%20list%20view%20for%20sorting%2Ffiltering%2Fgrouping%20but%20don't%20want%20to%20show%20all%20the%20fields.%20Once%20someone%20finds%20the%20list%20item%20they%20are%20looking%20for%2C%20they%20should%20be%20able%20to%20click%20it%20to%20view%20all%20the%20fields%20but%20not%20be%20able%20to%20change%20specific%20fields.%20Right%20now%20that%20doesn't%20seem%20to%20be%20possible%20with%20the%20built-in%20functionality%20in%20the%20modern%20UI.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-377962%22%20slang%3D%22en-US%22%3ERe%3A%20Modern%20Library%20-%20Not%20able%20to%20Customize%20NewForm.aspx%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-377962%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F519%22%20target%3D%22_blank%22%3E%40Ben%20Stegink%3C%2FA%3E%26nbsp%3B%20I%20just%20tried%20this%20on%20a%20test%20modern%20list%20and%20it%20worked.%20I%20had%20to%20wait%2010-15%20minutes%20before%20the%20field%20actually%20disappeared%20from%20the%20form.%3C%2FP%3E%3CP%3EThis%20test%20was%20to%20remove%20a%20field%20from%20the%20New%20Form.%20It%20used%20the%20PnP%20library.%20If%20you%20haven't%20used%20that%20before%2C%20you'll%20need%20to%20install%20it%3C%2FP%3E%3CP%3EInstall-Module%20-Name%20SharePointPnPPowerShellOnline%3C%2FP%3E%3CP%3EChange%20the%20TENANTNAME%2C%20SITENAME%2C%20LISTDISPLAYNAME%2C%20FIELDINTERNALNAME%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3E%24cred%20%3D%20Get-Credential%3CBR%20%2F%3EConnect-PnPOnline%20-Url%20https%3A%2F%2FTENANTNAME.sharepoint.com%2Fsites%2FSITENAME%20-credential%20%24cred%3CBR%20%2F%3E%24processedField%20%3D%20Get-PnPField%20-List%20%22LISTDISPLAYNAME%22%20%7C%20Where%20%7B%24_.InternalName%20-eq%20%22INTERNALFIELDNAME%22%7D%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%23SetShowInDisplayForm%3CBR%20%2F%3E%23SetShowInEditForm%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%24processedField.SetShowInNewForm(%24false)%3CBR%20%2F%3E%24processedField.Update()%3B%3CBR%20%2F%3EInvoke-PnPQuery%3CBR%20%2F%3EDisconnect-PnPOnline%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-377917%22%20slang%3D%22en-US%22%3ERe%3A%20Modern%20Library%20-%20Not%20able%20to%20Customize%20NewForm.aspx%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-377917%22%20slang%3D%22en-US%22%3E%3CP%3EAnybody%20come%20up%20with%20a%20solution%20for%20this%20yet%3F%20I%20don't%20even%20want%20to%20do%20anything%20complex...just%20hide%2Fshow%20various%20fields%20on%20the%20new%2Fedit%20form%20and%20on%20the%20display%20form.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%2C%20doing%20this%20in%20GCC%2C%20so%20PowerApps%20isn't%20even%20on%20the%20table.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20tried%20using%20PowerShell%20to%20leverage%26nbsp%3BSetShowIn___Form(%24false%2F%24true).%20It%20sort%20of%20works%2C%20however%2C%20it%20appears%20that%20in%20the%20modern%20UI%20everything%20is%20an%20%E2%80%9CEditForm%E2%80%9D.%20So%20your%20New%2FEdit%2FDisplay%20forms%20are%20always%20identical%20based%20on%20the%20%24true%2F%24false%20for%20SetShowInEditForm()%20(using%20PnPPowerShell).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20anyone%20have%20any%20other%20ideas%20on%20having%20a%20different%20new%2Fedit%20form%20than%20I%20do%20a%20view%20form%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-282295%22%20slang%3D%22en-US%22%3ERe%3A%20Modern%20Library%20-%20Not%20able%20to%20Customize%20NewForm.aspx%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-282295%22%20slang%3D%22en-US%22%3E%3CP%3EI%20agree%2C%20PowerApps%20is%20a%20convenience%2C%20not%20a%20solution.%26nbsp%3B%20Pushing%20these%20technology%20upgrades%20out%20with%20reduced%20capabilities%20is%20not%20helpful.%26nbsp%3B%20At%20a%20minimum%2C%20modern%20experience%20should%20maintain%20the%20features%20that%20classic%20provided%3B%20it%20does%20not.%26nbsp%3B%20If%20I%20could%20force%20my%20end%20users%20to%20not%20use%20the%20modern%20experience%2C%20I%20would%20absolutely%20do%20so%20since%20they%20are%20expecting%20the%20same%20feature%20enhancements%20that%20are%20not%20available%20(script%20editor%2Fediting%20newform%2Fediting%20editform%2Fetc...).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-197071%22%20slang%3D%22en-US%22%3ERe%3A%20Modern%20Library%20-%20Not%20able%20to%20Customize%20NewForm.aspx%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-197071%22%20slang%3D%22en-US%22%3EDO%20NOT%20use%20powerapps.%20If%20you%20have%20site%20visitors%20in%20your%20modern%20site%2C%20they%20won%E2%80%99t%20see%20your%20fancy%20powerapps%20form.%20Instead%20they%20will%20see%20a%20friendly%20notice%20that%20they%20require%20a%20powerapps%20license.%20What%20a%20perfect%20replacement%20over%20classic%20methods!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-40155%22%20slang%3D%22en-US%22%3ERe%3A%20Modern%20Library%20-%20Not%20able%20to%20Customize%20NewForm.aspx%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-40155%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20the%20classic%20mode%2C%20we%20used%20listforms%20just%20as%20forms%20to%20place%20data%20bound%20controls%26nbsp%3Bon%20them%20and%20styled%20them.%20mostly%20we%20created%20own%20listforms%20bound%20to%20custom%20content%20types.%20all%20of%20this%20was%20pretty%20%22freestyle%22%20and%20everyone%20used%20it's%20own%20javascript%20frameworks%20and%20UI%20styling%20components.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20think%20it's%20a%20question%20of%20time%2C%20until%20we%20see%20a%20standardized%20way%20of%20form%20customizations%20in%20modern%20experience.%20if%20you%20want%20to%20build%20your%20own%20and%20mobile%20sp%20list%20UI%2C%20just%20use%26nbsp%3BPowerApps!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-40147%22%20slang%3D%22en-US%22%3ERe%3A%20Modern%20Library%20-%20Not%20able%20to%20Customize%20NewForm.aspx%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-40147%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F4760%22%20target%3D%22_blank%22%3E%40Srinivas%20Narula%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETraditionally%20in%20SharePoint%20we%20used%20to%20modify%20the%20list%20forms.%20It's%20questionably%20if%20this%20is%20the%20right%20approach.%20I've%20always%20seen%20the%20lists%20in%20SharePoint%20a%20place%20to%20store%20my%20data%20and%20nothing%20more.%20At%20least%20since%20SharePoint%202013%20with%20its%20search%20web%20parts%20and%20display%20templates.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20I%20have%20lists%20to%20store%20my%20data%3C%2FP%3E%3CP%3ESearch%20web%20parts%20to%20spit%20out%20html%3C%2FP%3E%3CP%3Eand%20css%20to%20make%20it%20look%20good.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20could%20even%20use%20the%20search%20web%20parts%2C%20workflows%20or%20apps%26nbsp%3Blet%20users%20update%20list%20items.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20depending%20on%20your%20requirements%20I%20would%20consider%20apps%20as%20a%20means%20to%20interact%20with%20your%20lists.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-40133%22%20slang%3D%22en-US%22%3ERe%3A%20Modern%20Library%20-%20Not%20able%20to%20Customize%20NewForm.aspx%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-40133%22%20slang%3D%22en-US%22%3E%3CP%3EI%20wasn't%20aware%20one%20could%20tab%20metadata%20fields%20in%20the%20old%20form%20customizations.%26nbsp%3B%3C%2FP%3E%3CP%3ECoincidentally%20this%20is%20a%20feature%20my%20users%20were%20used%20to%20in%20OpenText.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-39827%22%20slang%3D%22en-US%22%3ERe%3A%20Modern%20Library%20-%20Not%20able%20to%20Customize%20NewForm.aspx%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-39827%22%20slang%3D%22en-US%22%3EThanks%20%40Jaun%20%26amp%3B%20%40Marcel%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-39788%22%20slang%3D%22en-US%22%3ERe%3A%20Modern%20Library%20-%20Not%20able%20to%20Customize%20NewForm.aspx%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-39788%22%20slang%3D%22en-US%22%3EShort%20answer%3A%20the%20team%20has%20not%20released%20yet%20a%20way%20to%20customize%20list%20forms%20in%20the%20way%20you%20used%20to%20do%20in%20the%20classic%20mode%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-39723%22%20slang%3D%22en-US%22%3ERe%3A%20Modern%20Library%20-%20Not%20able%20to%20Customize%20NewForm.aspx%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-39723%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Srinivas%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECheck%20out%26nbsp%3Bthis%20brand%20new%20article%20of%20Vesa%20Juvonen%20about%20the%20possibilities%20of%20customizing%26nbsp%3Bthe%20different%20modern%20experience%20%22parts%22%3A%20%3CA%20href%3D%22https%3A%2F%2Fmsdn.microsoft.com%2Fen-us%2Fpnp_articles%2Fmodern-experience-customizations%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmsdn.microsoft.com%2Fen-us%2Fpnp_articles%2Fmodern-experience-customizations%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%2C%20Marcel%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

Hi SharePoint Folks,

 

I am facing an issue with Modern Document Library. As a part of my customization, I have to customize newform with tabbing becasue large number of columns.

 

This piece of work I have done earlier with classic version. But with the new changes from Microsoft on Document Libraries, now I am not able to edit NewForm.aspx page and without that I wont be able to do any customizations.

 

I came across an article in this forum where they have announced the Field level JSLink implementation. Does this implies Client Side Rendering(CSR) is disabled for forms?

 

Is there any solution or workaround for this scenario??

 

Happy Coding!!

 

Sri

13 Replies
Highlighted

Hi Srinivas

 

Check out this brand new article of Vesa Juvonen about the possibilities of customizing the different modern experience "parts": https://msdn.microsoft.com/en-us/pnp_articles/modern-experience-customizations

 

Best, Marcel

Highlighted
Short answer: the team has not released yet a way to customize list forms in the way you used to do in the classic mode
Highlighted
Thanks @Jaun & @Marcel
Highlighted

I wasn't aware one could tab metadata fields in the old form customizations. 

Coincidentally this is a feature my users were used to in OpenText.

Highlighted

Hi @Srinivas Narula,

 

Traditionally in SharePoint we used to modify the list forms. It's questionably if this is the right approach. I've always seen the lists in SharePoint a place to store my data and nothing more. At least since SharePoint 2013 with its search web parts and display templates.

 

So I have lists to store my data

Search web parts to spit out html

and css to make it look good.

 

You could even use the search web parts, workflows or apps let users update list items.

 

So depending on your requirements I would consider apps as a means to interact with your lists.

Highlighted

In the classic mode, we used listforms just as forms to place data bound controls on them and styled them. mostly we created own listforms bound to custom content types. all of this was pretty "freestyle" and everyone used it's own javascript frameworks and UI styling components.

 

I think it's a question of time, until we see a standardized way of form customizations in modern experience. if you want to build your own and mobile sp list UI, just use PowerApps!

Highlighted
DO NOT use powerapps. If you have site visitors in your modern site, they won’t see your fancy powerapps form. Instead they will see a friendly notice that they require a powerapps license. What a perfect replacement over classic methods!
Highlighted

I agree, PowerApps is a convenience, not a solution.  Pushing these technology upgrades out with reduced capabilities is not helpful.  At a minimum, modern experience should maintain the features that classic provided; it does not.  If I could force my end users to not use the modern experience, I would absolutely do so since they are expecting the same feature enhancements that are not available (script editor/editing newform/editing editform/etc...).

Highlighted

Anybody come up with a solution for this yet? I don't even want to do anything complex...just hide/show various fields on the new/edit form and on the display form.

 

Also, doing this in GCC, so PowerApps isn't even on the table.

 

I tried using PowerShell to leverage SetShowIn___Form($false/$true). It sort of works, however, it appears that in the modern UI everything is an “EditForm”. So your New/Edit/Display forms are always identical based on the $true/$false for SetShowInEditForm() (using PnPPowerShell).

 

Does anyone have any other ideas on having a different new/edit form than I do a view form?

 

 

Highlighted

@Ben Stegink  I just tried this on a test modern list and it worked. I had to wait 10-15 minutes before the field actually disappeared from the form.

This test was to remove a field from the New Form. It used the PnP library. If you haven't used that before, you'll need to install it

Install-Module -Name SharePointPnPPowerShellOnline

Change the TENANTNAME, SITENAME, LISTDISPLAYNAME, FIELDINTERNALNAME

 

$cred = Get-Credential
Connect-PnPOnline -Url https://TENANTNAME.sharepoint.com/sites/SITENAME -credential $cred
$processedField = Get-PnPField -List "LISTDISPLAYNAME" | Where {$_.InternalName -eq "INTERNALFIELDNAME"}


#SetShowInDisplayForm
#SetShowInEditForm


$processedField.SetShowInNewForm($false)
$processedField.Update();
Invoke-PnPQuery
Disconnect-PnPOnline

 

Highlighted

@Robin Nilsson Thanks, I was using the method you outlined already, I just needed to do little more testing. I was changing too many properties at once when I was originally testing. The New/Edit does appear to work, however, the Edit/Display is where it all falls apart. I took the time to go through all the configurations and this is what you get

2019-03-21_12-57-39.png

Essentially, Display follows along with the Edit property rather than the Display. I'm assuming this is due to the quick edit in the information pane. But what would make sense it to only show the "Display" fields in the information pane, and the "Edit" fields once you click "Edit All". So, when dealing with Modern UI, you really only have New and Edit. Display is just ignored

 

Also, I realized one of the fields I was using was a calculated column. Those actually just ignore all the rules and won't show at all.

 

You could maybe make the argument that you don't need Display, as you can display everything you need in the list view and should only click on the info panel if you need to make a change. This may be the route I try. However, there are also times when you want a set of the fields in the list view for sorting/filtering/grouping but don't want to show all the fields. Once someone finds the list item they are looking for, they should be able to click it to view all the fields but not be able to change specific fields. Right now that doesn't seem to be possible with the built-in functionality in the modern UI.

Highlighted
Great work! I confirm your analysis on Display form not acting as expected when using the .SetShowInDisplayForm property of a field. I'd consider that a bug, actually - if there's a reason to not display something, it should be honored. I don't train much on using the info panel - I'm torn by its ease of use. But if a list uses PowerApps to interact with a list, the info panel is a way to get around any processing the PowerApps might do, which could cause problems.

Calculated fields have always been like that in SharePoint - only available on the Display Form. When I've needed to show it on an edit form I used customization to pull the field value and display it.
Highlighted

@Robin Nilsson, Yeah, I was going to use PowerApps, but it's a GCC tenant (which doesn't have PowerApps yet, it's been delayed at least 6 months beyond when it was supposed to be available...another story...) 

 

As for calculated fields, agree, it makes sense it shouldn't be on New/Edit since it's calculated. It just doesn't show on Display either...probably due to the face that Display appears to be driven off the Edit property.

 

Thanks Robin!

Ben