New answers tagged


The calculated field is calculated after the item added or updated. We cannot add or edit value for the calculated column, so it is not displayed on the New/Edit forms, they are displayed on the display form only or in views.


I just have the perfect solution for you, it's called "Cascading Dropdown" ! Please refer to Mr Shane Young which i find him very professional guy, and here the link: PowerApps Cascading Dropdown, here you will find exactly what you want and more ! Good luck.


Chelsea_MSFT has the right answer, but just a couple other points: You mention "have to enter". Just pointing out that fields have a required property that can be set exactly the same way, so you can set fields to be conditionally required. PowerApps, for an inexplicable reason, runs these rules in design view while you're building your form. This means ...


In PowerApps managed metadata column shows up as a drop-down menu and There is no (out of the box) way to show the "tree structure" of terms. Source: PowerApps and managed metadata. Multi-valued managed metadata columns are fully supported in PowerApps. Source: Tips and Tricks for multiselect controls with advanced tagging options.


It is supported in PowerApps. I’ve tested in a simple list with 5 single line of text fields, named A~E. For example, when I check the Checkbox control, the field A and B will be invisible and be replaced by fields C~E. Please see the steps below: Select Data Card for field A and switch to “Visible” under properties. Type If(Checkbox2.Value=false,true,...


This is by design. The calculated fields will not be shown on New/Edit form of SharePoint list. It will visible on the display form of list or in list views only.


The special characters are nothing but pound symbol and ID of that user in that site. That's SharePoint exports the user field to excel. It's by design and we cannot change it. I understand that you want to remove the number and ;# in excel file. You can use formulas to achieve this. =SUBSTITUTE(H2, ";#", " ") Change H2 to the column which contains the ...


"Save as" function is disabled by default because SharePoint forms cannot be saved as new apps and used as template. This feature is currently not available. See the UserVoice post below: What we can do is create an app from a SharePoint ...

Top 50 recent answers are included