Bizarre glitch when patching dropdowns

(0) Share

Report

Posted on by CU05122009-0

I think this is really odd, does anyone have an explanation or even better, a solution?

I'm patching multiple drop downs to a SharePoint list using:

Patch(Table1,varRecord,{Field1: dropdown1.Selected.field1ID, Field2: dropdown2.Selected.field2ID, Field3: dropdown3.Selected.field3ID})

This will work fine maybe once however after the app is published the patch throws up an error. It stops recognising field2ID and field3ID and if I edit those values it wants me to use fieldID1 values for each.

Each of the dropdown is populated from their own SharePoint lists and if I remove and readd the SharePoint lists it will again recognise and accept field2ID and field3ID but then the error soon returns.

Since it will recognise it the after the lists are reattached this suggests I'm not doing anything wrong but am I?

Categories:

General Questions

I have the same question (0)

All responses (4)

Answers (0)

ronaldwalcott 3,827 Super User 2025 Season 2 on at

Like (0)

Report

Bizarre glitch when patching dropdowns

Are Field1, Field2 and Field3 text columns as the selected value from the dropdown is a text value? What error is the Patch showing?

Was this reply helpful? Yes No
CU05122009-0 4 on at

Like (0)

Report

Bizarre glitch when patching dropdowns

Both Field1 in the SP list being patched and Field1ID from the dropdown SharePoint list are number columns. They are acting as foreign key and primary key respectively.

The error is "The type of this argument 'field_9' does not match with the expected type 'Number'. Found type 'Error'. Which makes sense as dropdown2 and dropdown3 seem to think their corresponded selected value is field1ID, they aren't recognising the existing of field2ID and field3ID respectively.

Was this reply helpful? Yes No
ronaldwalcott 3,827 Super User 2025 Season 2 on at

Like (0)

Report

Bizarre glitch when patching dropdowns

Why would this make sense? Is this the field you configured for the dropdown?

"Which makes sense as dropdown2 and dropdown3 seem to think their corresponded selected value is field1ID"

How is the dropdown configured and what is field_9?

Was this reply helpful? Yes No
CU05122009-0 4 on at

Like (0)

Report

Bizarre glitch when patching dropdowns

It makes sense in so far as, if dropdown2 thinks it's dropdown1 then corresponding values from dropdown2 would produce an error, so the error message is correct. What doesn't make sense is dropdown2 thinking it's dropdown1! I.e., the error message is of no help.

Each drop down has its Items set from its own SharePoint list. Each list only has two relevant columns, the values the user see (text) and the corresponding ID.

You can ignore 'field 9' that could be any value, I have several drop downs on the screen and its patching to a large transactional SharePoint list.

Was this reply helpful? Yes No