we use sharepoint online because it support external sharing and managing the lists/fields through content types, but if we start customizing our lists using PowerApp, then we will loose one of the main features found in sharepoint online, which is sharing with external users!!also we no more have control over the fields. there is a main issue in Office 365, is that things sometimes make you confused.
#Change text edit to read only mode free#
Second question, to test things out, can you please advice what i need to do exactly inside powerapp to set the field as Read-Only inside the Edit form? as i did not find a way to change the DisplayMode to View, where when i click on the DisplayMode for the field i got a free text to enter a function as Youngthanks for the reply and help.i am not sure if i should follow the PowerApp appraoch. so not sure if i have to live with all these limitations just to have a filed as read-only on edit forms.
i also remember when i wanted to use powerapp, i skipped this option because powerapp did not support external users accessing it. where sharepoint should allow us to re-order the list fields from the content type and apply this to all the lists which use the same content type + the ability to control the visibility of the fields in New,Edit and Display forms using PnP and get the affect on all the list which uses the column, as so on. So what i am trying to say, is that sometime we got new methods to implement things, but if we blindly follow these approaches (such as customizing the list's edit and new forms using powerapp), then we will loose many advantages of using sharepoint. if i set a columns to be hidden on Edit and/or New forms using PnP, this will not affect the cusotm powerapp edit form, for example this PnP script which will hide a column inside the Edit form while show it inside Display form, will be ignored by powerapp:. If we re-order the columns inside the content type, this re-ordering will not affect the power-app's custom Edit/New forms.Ģ. As using powerapp to create custom edit/new forms, means we have to live with these limitations (i am viewing things from the sharepoint point of view), compared to using the built-in modern Edit and New list forms :-ġ. Now i were trying to avoid using PowerApp for this simple scenario/requirement, i would use it for more complex scenarios if/when needed in the future. So can anyone advice on this please? how we can set a field as read-only inside an Edit form inside modern YoungThanks for the reply.
$customfield = $.GetByInternalNameOrTitle($fieldTitle) $SiteURL = " $Context = New-Object ($SiteURL) also using PnP i am only able to hide the field inside the Edit form (but i do not have the option to set it as Read-Only), Where i am using the modern UI, as in classic UI i can add a script editor web part and make the field Read-Only using a simple Jquery.
I want this column to be read-only inside Edit form while to have it editable inside Create/New form. and i have a column of type Date named " OriginalApprovedDate".
you can change the backgroud to make it look different from a normal EditText.I am working on a custom list inside SharePoint online classic team site. even in read-only state, the text can be copied by user.
#Change text edit to read only mode code#
With this code you can make EditView Read-only or Normal. This is my implementation (a little long, but useful to me!):