Nov 19 2017 03:41 PM
Evening everyone,
I'm looking for some advice on how I can get around some roadblocks i'm hitting with the modern UI. Here's the issues:
These requirements could be met fairly quickly using the classic UI with only a little bit of JS for the field hide / disable part - SharePoint does the other two requirements out of the box with no issue.
Any input on how these requirements can be met using powerapps or the modern UI would be appreciated.
I'm not against using SPFx Web Parts / Extensions but don't want to create completely custom forms as I feel that goes against everything that was mentioned at ESPC17.
Thanks.
M
Nov 19 2017 10:51 PM
Nov 20 2017 02:38 AM - edited Nov 20 2017 03:32 AM
Nov 20 2017 02:38 AM - edited Nov 20 2017 03:32 AM
Thanks for your input Juan, much appreciated.
It looks like I'll need to stick with Classic mode for now or wait until the attachment functionality is available in Powerapps.
Unfortunately attaching files is a mandatory requirement so Powerapps can't be used in this instance.
The modern UI looks and works well but given the fact I can't customize the form or use the append text feature on a multi-line text box (it reverts to a classic form) takes that out of the tool belt as well.
I have looked at SPFx extensions to add command bar / context buttons but I've not been able to come to a complete solution meeting all requirements; Either attachments go, or the append text feature goes.
Without re-writing a lot of code that works out of the box in classic mode, my options seem limited to either using Classic Mode or waiting to be able to use attachments (read/write) through Powerapps
If anyone can think of a workaround / method that the Modern UI can be used while still being able to attach files and keep a history of case notes (either through append text to a multiline textbox or by linking to a seperate list) then let me know.
Thanks again for your help Juan.
Jun 13 2018 03:54 PM