If Statement isn't working properly

[ShondaT]

I have the following code assigned to a sharepoint column field that should be hidden if the content of another field doesn't match the value indicated. Below is screenshot. As you can see, the column should only appear when "Email" is selected in the Invoices and Statement Delivery, however, it remains visible regardless of selection.

Any help is greatly appreciated.

[Amik · Accepted solution]

@ShondaT - consider wrapping parenthesis around your OR statement, e.g:

(varshowfields = 3 || varshowfields = - 1) && DataCardValue15.SelectedText.Value = "Email"

In addition, there is no need to use an IF condition. The above expression will either return Boolean true or false.

------------------------------------------------------------------------------------------------------------------------------

If I have answered your question, please mark your post as Solved. Remember, you can accept more than one post as a solution.

If you like my response, please give it a Thumbs Up.

Imran-Ami Khan

[ShondaT]

@Amik it worked perfectly! Thank you so much!

[ShondaT]

@Amik would I have to apply a different syntax if visibility was based on a field that is a sharepoint choice field? The variable would remain the same. 

[Amik]

@ShondaT same syntax except you will use DataCardValue15.Selected.Value instead of of DataCardValue15.SelectedText.Value.

[ShondaT]

@Amik that worked to! You're awesome. I'm so sorry to have another question but please know that I appreciate your expertise! What would be the syntax if the visibility was the same for two options? I've tried DataCardValue14.SelectedText.Value="Entity" || "Individual"  but it is only visible when Entity is selected.

By the way, I decided to change all of my SharePoint Choice columns to text columns and set the options in the app. That seems to work so much better and is an approach I can use as a standard. I don't think there's any benefit it using SharePoint Choice fields in solutions unless I'm missing something.

[Amik]

@ShondaT :

ComboBox1.Selected.Value = "Entity" || ComboBox1.Selected.Value = "Individual"

Dropping complex field types is the correct approach. Complex fields like Lookups and Choices are very useful if you are interacting directly with SharePoint because Complex field types are designed for the SharePoint user interface in mind. If the ultimate goal is for users to interact directly with the App, there is little need to use Complex fields.

------------------------------------------------------------------------------------------------------------------------------

If I have answered your question, please mark your post as Solved. Remember, you can accept more than one post as a solution.

If you like my response, please give it a Thumbs Up.

Imran-Ami Khan

[ShondaT]

@Amik Prior to hearing back from you I tried doing this: 

(varshowfields=2||varshowfields=-1) && DataCardValue14.SelectedText.Value<>"Assurance"

and it worked. I only have 3 options in the dropdown and "Assurance" is the only one that needs to show different fields. 

I tried just tried your approach, but I couldn't get it to work. This is the column the visibility of the other columns are based on and is the text column I applied "Allowed Values" to. Could that be why your suggestion didn't work?

 

Also, thanks for the validation. Part of the responsibility within the firm I work for is to build these solutions. I've been able to feel my way around, but I have very surface level knowledge which I'm trying to transition to solid approaches. The only way I can do that is to have an understanding of the different ways to construct various syntax and how those syntax differ based on the column type. Your help with that is so appreciated. 🙂

[Amik]

Hi @ShondaT - I did not quite understand your description, but well done for figuring out a solution in your own way.

[ShondaT]

I just reread what I wrote and it was very poorly written. I revised it. No need to reread though. LOL Thank you for your response. I hope your day is going well. 🙂