Modern Sites/Pages limitations - Project Road Blocks.
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: I need to be able to disable / hide fields on a modern UI form (NewForm.aspx / EditForm.aspx). Previously this would have been done using JS in a SEWP/CEWP. The only solution I have found here is to hide it from the form by customizing the content type (but this hides it from everyone). The newly released powerapps functionality (https://powerapps.microsoft.com/en-us/blog/custom-form-launch/) would have solved this easily but comes with its own quirks that cause issues for the requirements below. Attachments - the Modern form supports adding attachments to items but the powerapps functionality does not - PA only supports read only operations when it comes to attachments (At least for now) which prevents me from using PA to solve issue 1. Multiple notes - Previously I would have dealt with this by simply turning on versioning and "append changes" to a multiline text box. However, when append changes is turned on, the Modern UI changes to a classic form. Powerapps handles it better but only shows the latest addition to the text box - any previous entries are not shown on the PA form but are correctly stored on the list item. 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