web

You’re offline. This is a read only version of the page.

News and Announcements icon

Power Platform CommunityForums Power Apps Can not save because o...

Power Apps

Answered

Can not save because of a hidden required field

(0) Share

Report

Report

Posted on by Flensborg

20

Hello,

I am building a SharePoint list using Power Apps to help input correct data.

I have created a dropdown that is visible if Type Of Project = Execution Project

If it not an Execution Project, the selected dropdown will be hidden.

However the drop-down is mandatory, and I would like it to be mandatory only if visible.

Currently I am not able to save if I select something that isn't Execution, as the required field is now hidden.

How do I ensure that this drop-down is required ONLY if DataCardValue18.Selected.Value = "Execution Project"?

I've tried the following: If(DataCardValue18.Selected.Value = "Execution Project",true,false)

I have also tried making two statements

If(DataCardValue18.Selected.Value = "Execution Project",true) OR If(DataCardValue18.Selected.Value = "New Product Development",false)

However I do not seem to be able to crack this. Does anyone have any ideas?

Categories:

Building Power Apps

I have the same question (0)

All responses Img

All responses (2)

Answers Img

Answers (1)

Sort by

VeGETzX 367 on at

Like (1)

Report
Copy link

Link copied!
As I know, If your SharePoint column are required, So the data for that column can't be blank, regardless of any code you use on Power Apps because it's restricted by SharePoint.

I do recommend to set that column to be optional on that SharePoint list and use Required property for Datacard in PowerApps.

It's more flexible, then you can use this code on Required property of your Execution Project's datacard
DataCardValue18.Selected.Value = "Execution Project"

Was this reply helpful? Yes No
Verified answer

Flensborg 20 on at

Like (0)

Report
Copy link

Link copied!

Thanks for the answer. I had already changed the permissions in the SharePoint column, but apparently PowerApps had not registered it.
The solution for me was to re-create the exact same column, and then do as you mentioned with making it "required" in PowerApps and "Not Required" in the SharePoint list settings.

Thanks for your help 🙂

Was this reply helpful? Yes No

Join the conversation