Issue with ComboBox and multi-column collection - why the heck is this happening?

[simms7400]

Hello Folks -

I have a ComboBox within one of my DataCards that collects multiple columns from a SharePoint List. The logic is as follows:

	ClearCollect(
		TargetList,{TargetAlias:"Not Applicable",TargetID:"Not Appplicable"},
			ShowColumns(
				Filter(rdTarget, Or(Not(DataElement_Type.Value="Time Tracking"),Not(Portfolio_Status.Value="Terminated"))),
				"TargetAlias","TargetID","DDU_Portfolio","Modality_Detail","Target_Short_Name","Target_Long_Name","Business_Owner","Mechanism","IP_Owner"
			)
	)

As you can, the Collection has multiple columns.  Within my ComboBox I am using the ["TargetAlias"] as the field.  The issue I am having is that if I open the Form and go to submit it after making a change to OTHER fields, it won't submit.  However, if I edit the ComboBox and select a new value (or the same) it will submit successfully....

I did some trial and error and if I remove everything BUT "TargetAlias" and "TargetID" from the collection it works fine. why?

Collection that works:

	ClearCollect(
		TargetList,{TargetAlias:"Not Applicable",TargetID:"Not Appplicable"},
			ShowColumns(
				Filter(rdTarget, Or(Not(DataElement_Type.Value="Time Tracking"),Not(Portfolio_Status.Value="Terminated"))),
				"TargetAlias","TargetID"
			)
	)

Why the heck is this happening?  I need the other columns because I use them across other DataCards in lookups etc.

Thank you!

[RandyHayes]

@simms7400 

What is the Update property of the datacard for the combobox?  And what is the DefaultSelectedItems property of the Combobox?

Look over those as they are the controlling factors to what is displayed (the underlying data) and what is written (the chosen values in the combobox).

I hope this is helpful for you.

[simms7400]

@RandyHayes   Hi Randy, long time no talk, hope all is well!

My DefaultSelectedItems property is as follows:

LookUp(TargetList,TargetAlias=ThisItem.ResearchAlias)

And the Update property is as follows:

PFRAlias_CB.Selected.TargetAlias

PFRAlias_CB is my ComboBox Name. Do you notice anything out of the ordinary? Thank you!

[simms7400]

@RandyHayes 

So I did some more analysis and I think I narrowed down the issue.  So if I remove the fields that are "choice" fields from the collection, everything works as expected. However as soon as I add the choice fields back, I experience the behavior as explained above.

Is this a known issue? How do I solve for it?

[RandyHayes]

@simms7400 

Hello again. Hope you are well too, and sorry for delay...the forum is sending me message notifications about 3 hours late for some reason today.

So the thing about Combobox DefaultSelectedItems is that when you set them, they need to match the schema of the Items property.  Your items property is based on a collection that has 9 columns in it.  Yet, you are trying to then set it based on a LookUp that might return something other than that (based on the Not Applicable you are trying to add in).

SO, as you stated in your original post - your collection has multiple columns. And the bigger clue what when you mentioned "or the same" when selecting a value...your combobox should have already had the value from the underlying data record in it selected.

So, before jumping into a few avenues to take, let me know some more details:

1) I am assuming that the underlying column is a text column and not something else?

2) When you edit an existing record that has a value in that column, does it appear as a selected item in your combobox?

    a) When you edit an existing record with something beside "Not Applicable" in it, does that value appear selected?

    b) When you edit an existing record WITH "Not Applicable" in it, does that value appear selected?

3) Why are you using ShowColumns on this Filter?

I think I have a a couple more questions, but can't think of them at the moment.

[simms7400]

@RandyHayes  

1) I am assuming that the underlying column is a text column and not something else?

Yes you are correct, the ComboBox is sitting within a DataCard that is a text column

2) When you edit an existing record that has a value in that column, does it appear as a selected item in your combobox?

Yes it does

a) When you edit an existing record with something beside "Not Applicable" in it, does that value appear selected?

Yes it does

b) When you edit an existing record WITH "Not Applicable" in it, does that value appear selected?

Yes it does

3) Why are you using ShowColumns on this Filter?

I thought that was the proper way, I guess it's not? What is the best practice method?

So to recap, all values are appearing as expected in the combobox, whether it's a "Not Applicable" value or another value from the collection so that's why this is a head scratcher.  Per my earlier note, if the ComboBox is populated with "Not Applicable" when I edit the form and make changes to other fields and then I go to submit, it works fine, but when there is another value in the collection, I get a "Gateway" error and it won't submit.  Unless until I select a new value, or re-select the value that's displayed, will it submit.

Lastly as I mentioned, everything works fine when I remove the columns from my collection that are "Choice" fields from my SharePoint list. Which is odd.

Thank you for your help, Randy!!

[RandyHayes]

@simms7400 

Thanks for the answers...it helps...sort of 😂

So, based on what you said and what you described and what you have, things should be working.  I am wondering if there is another sinister actor involved in this.  

You don't have any other modifications to the Combobox except the DefaultSelectedItems and the Items property??  (i.e. no OnChange, OnSelect, or anything else?)

So, in your first test, you said that if you go into a record and change OTHER fields, it will not submit.  You need to then change the Combobox in order to get it to submit.

I am working from that analysis - so, let's shortcut the whole combobox.  In the Update property of the datacard, simply make it "Not Applicable".  Then try that same test again...change other fields and try to submit (don't worry about the combobox during this test as it is not connected).  Does it submit if we take the combo out of the picture?

[simms7400]

Hi @RandyHayes 

So that's the weird thing, when the form opens and "Not Applicable" is populated, you can submit the form as is and no error...

However, when its populated with another value, (other than "Not Applicable") that's when it doesn't submit. I then need to edit the ComboBox  by re-selecting the value that's currently displayed or a new value and it will submit fine.

But just to test, I made the update property "Not Applicable" and that works as expected.  And I believe I already mentioned this but the collection is populated within the "On Visible" property, but I don't think that would have any negative impact on things.

Instead of showcolumns, do we need to create the collection with "Add Columns" and give fields new names? As I mentioned, when I take out the choice fields from the collection everything works fine.  Very interesting.

[RandyHayes]

@simms7400 

Okay...so your other factor is that you said Not Applicable worked before.  So now, set the Update property to one of the other values that would normally be in that combobox.  Let's see what that does.

[simms7400]

Hi @RandyHayes  okay now I think we are getting somewhere!

When I added a value (i.e. FIN-111 Restoration of h.micro (4089-100) ) that is populated to the Update property, other than "Not Applicable" it does not submit and I get the "gateway" error.  This is odd, it almost doesn't recognize the value when it's populated when the form open, but recognizes when the value is re-selected within the ComboBox...hmmmmm.