Update Sharepoint list item powerapps

Hi Chris,

The methodology Mohammed uses is correct. There is however another way of doing this using the same methodology [which I use when the target field is a lookup].
Instead of Patching, simply try the formula below in the update properties of the card [I have used new lines only to show the logic].

[
{
'@odata.type': "Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
Id:LocationvDepartment.Selected.ID,
Value: LocationvDepartment.Selected.Title
}
]

NOTE - all of this is case-sensitive [ID does not equal Id] - you seem to have this one.

To explain [from my humble level of understanding at least]: -

Firstly, the purpose of the "odata.type" reference is a bit of a mystery to me [and others when you Google it] except I know you need it for multi-value field references to work on anything other than a straight [non-custom] cards generated by PowerApps [it takes care of this in the background].

On fields in SharePoint based on Lookup fields from another table [not simply multi-value Choice lists in the SharePoint target field], the field actually contains two pieces of information - the actual value you are after and the ID from the other list you are looking up and both have to be passed back to the target list.

I hope this helps.

Hi Chris,

The methodology Mohammed uses is correct. There is however another way of doing this using the same methodology [which I use when the target field is a lookup].
Instead of Patching, simply try the formula below in the update properties of the card [I have used new lines only to show the logic].

[
{
'@odata.type': "Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
Id:LocationvDepartment.Selected.ID,
Value: LocationvDepartment.Selected.Title
}
]

NOTE - all of this is case-sensitive [ID does not equal Id] - you seem to have this one.

To explain [from my humble level of understanding at least]: -

Firstly, the purpose of the "odata.type" reference is a bit of a mystery to me [and others when you Google it] except I know you need it for multi-value field references to work on anything other than a straight [non-custom] cards generated by PowerApps [it takes care of this in the background].

On fields in SharePoint based on Lookup fields from another table [not simply multi-value Choice lists in the SharePoint target field], the field actually contains two pieces of information - the actual value you are after and the ID from the other list you are looking up and both have to be passed back to the target list.

I hope this helps.

Hi Chris,

The methodology Mohammed uses is correct. There is however another way of doing this using the same methodology [which I use when the target field is a lookup].
Instead of Patching, simply try the formula below in the update properties of the card [I have used new lines only to show the logic].

[
{
'@odata.type': "Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
Id:LocationvDepartment.Selected.ID,
Value: LocationvDepartment.Selected.Title
}
]

NOTE - all of this is case-sensitive [ID does not equal Id] - you seem to have this one.

To explain [from my humble level of understanding at least]: -

Firstly, the purpose of the "odata.type" reference is a bit of a mystery to me [and others when you Google it] except I know you need it for multi-value field references to work on anything other than a straight [non-custom] cards generated by PowerApps [it takes care of this in the background].

On fields in SharePoint based on Lookup fields from another table [not simply multi-value Choice lists in the SharePoint target field], the field actually contains two pieces of information - the actual value you are after and the ID from the other list you are looking up and both have to be passed back to the target list.

I hope this helps.

Hi Chris,

The methodology Mohammed uses is correct. There is however another way of doing this using the same methodology [which I use when the target field is a lookup].
Instead of Patching, simply try the formula below in the update properties of the card [I have used new lines only to show the logic].

[
{
'@odata.type': "Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
Id:LocationvDepartment.Selected.ID,
Value: LocationvDepartment.Selected.Title
}
]

NOTE - all of this is case-sensitive [ID does not equal Id] - you seem to have this one.

To explain [from my humble level of understanding at least]: -

Firstly, the purpose of the "odata.type" reference is a bit of a mystery to me [and others when you Google it] except I know you need it for multi-value field references to work on anything other than a straight [non-custom] cards generated by PowerApps [it takes care of this in the background].

On fields in SharePoint based on Lookup fields from another table [not simply multi-value Choice lists in the SharePoint target field], the field actually contains two pieces of information - the actual value you are after and the ID from the other list you are looking up and both have to be passed back to the target list.

I hope this helps.

Hi Chris,

The methodology Mohammed uses is correct. There is however another way of doing this using the same methodology [which I use when the target field is a lookup].
Instead of Patching, simply try the formula below in the update properties of the card [I have used new lines only to show the logic].

[
{
'@odata.type': "Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
Id:LocationvDepartment.Selected.ID,
Value: LocationvDepartment.Selected.Title
}
]

NOTE - all of this is case-sensitive [ID does not equal Id] - you seem to have this one.

To explain [from my humble level of understanding at least]: -

Firstly, the purpose of the "odata.type" reference is a bit of a mystery to me [and others when you Google it] except I know you need it for multi-value field references to work on anything other than a straight [non-custom] cards generated by PowerApps [it takes care of this in the background].

On fields in SharePoint based on Lookup fields from another table [not simply multi-value Choice lists in the SharePoint target field], the field actually contains two pieces of information - the actual value you are after and the ID from the other list you are looking up and both have to be passed back to the target list.

I hope this helps.

Hi Warren,,

Yes the Items Properties for the two fields are sourcing data from a separate SP list to the one I need updating.

Formulas are; -

Location Field - ItemsSort[Distinct[LocationVDepartment,Title],Result]
Department Field - Items -Distinct[Filter[LocationVDepartment,Title=LocationID.Selected.Result],Department]

[These are the same formulas being used in the initial screen for entering data for a new visitor]

The columns in my SP list for Location & Department were Choices. I changed them both the Single Line of Text and refreshed. Errors appeared for both fields - Expected Record Value.

The error seems to relate to Default and DefaultSelectedItems properties. They are currently display the formulas, ThisItem.Location and ThisItem.Department respectively in both property fields.

Hi Chris,

The methodology Mohammed uses is correct. There is however another way of doing this using the same methodology [which I use when the target field is a lookup].
Instead of Patching, simply try the formula below in the update properties of the card [I have used new lines only to show the logic].

[
{
'@odata.type': "Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
Id:LocationvDepartment.Selected.ID,
Value: LocationvDepartment.Selected.Title
}
]

NOTE - all of this is case-sensitive [ID does not equal Id] - you seem to have this one.

To explain [from my humble level of understanding at least]: -

Firstly, the purpose of the "odata.type" reference is a bit of a mystery to me [and others when you Google it] except I know you need it for multi-value field references to work on anything other than a straight [non-custom] cards generated by PowerApps [it takes care of this in the background].

On fields in SharePoint based on Lookup fields from another table [not simply multi-value Choice lists in the SharePoint target field], the field actually contains two pieces of information - the actual value you are after and the ID from the other list you are looking up and both have to be passed back to the target list.

I hope this helps.

• You have two target fields to be updated, which are expecting a simple text value. Your cards have these fields as the source data.
• The default of the drop-down should be Parent.Default [it needs to display the item from the main list if present] however ThisItem.Location should work.
• I have not seen a DefaultSelectedItems property in a drop-down - it seems to relate to Combo Boxes [which I do not use presently], however some Googling suggests Parent.Default may work [don't take my advice on this - check it].
• All of this aside, the actual field name from the other list you are displaying for selection is the one to be used for updating the target. This in both cases below appears to be "Title" [please confirm if I am correct], so: -
  
  • The Update properties of card Location_DataCard8 should be LocationID.Selected.Title.
  • Likewise Department_DataCard8 should be DepartmentID.Selected.Title

Hi Warren,,

Yes the Items Properties for the two fields are sourcing data from a separate SP list to the one I need updating.

Formulas are; -

Location Field - ItemsSort[Distinct[LocationVDepartment,Title],Result]
Department Field - Items -Distinct[Filter[LocationVDepartment,Title=LocationID.Selected.Result],Department]

[These are the same formulas being used in the initial screen for entering data for a new visitor]

The columns in my SP list for Location & Department were Choices. I changed them both the Single Line of Text and refreshed. Errors appeared for both fields - Expected Record Value.

The error seems to relate to Default and DefaultSelectedItems properties. They are currently display the formulas, ThisItem.Location and ThisItem.Department respectively in both property fields.

Hi Chris,

The methodology Mohammed uses is correct. There is however another way of doing this using the same methodology [which I use when the target field is a lookup].
Instead of Patching, simply try the formula below in the update properties of the card [I have used new lines only to show the logic].

[
{
'@odata.type': "Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
Id:LocationvDepartment.Selected.ID,
Value: LocationvDepartment.Selected.Title
}
]

NOTE - all of this is case-sensitive [ID does not equal Id] - you seem to have this one.

To explain [from my humble level of understanding at least]: -

Firstly, the purpose of the "odata.type" reference is a bit of a mystery to me [and others when you Google it] except I know you need it for multi-value field references to work on anything other than a straight [non-custom] cards generated by PowerApps [it takes care of this in the background].

On fields in SharePoint based on Lookup fields from another table [not simply multi-value Choice lists in the SharePoint target field], the field actually contains two pieces of information - the actual value you are after and the ID from the other list you are looking up and both have to be passed back to the target list.

I hope this helps.

• You have two target fields to be updated, which are expecting a simple text value. Your cards have these fields as the source data.
• The default of the drop-down should be Parent.Default [it needs to display the item from the main list if present] however ThisItem.Location should work.
• I have not seen a DefaultSelectedItems property in a drop-down - it seems to relate to Combo Boxes [which I do not use presently], however some Googling suggests Parent.Default may work [don't take my advice on this - check it].
• All of this aside, the actual field name from the other list you are displaying for selection is the one to be used for updating the target. This in both cases below appears to be "Title" [please confirm if I am correct], so: -
  
  • The Update properties of card Location_DataCard8 should be LocationID.Selected.Title.
  • Likewise Department_DataCard8 should be DepartmentID.Selected.Title

Hi Warren,,

Yes the Items Properties for the two fields are sourcing data from a separate SP list to the one I need updating.

Formulas are; -

Location Field - ItemsSort[Distinct[LocationVDepartment,Title],Result]
Department Field - Items -Distinct[Filter[LocationVDepartment,Title=LocationID.Selected.Result],Department]

[These are the same formulas being used in the initial screen for entering data for a new visitor]

The columns in my SP list for Location & Department were Choices. I changed them both the Single Line of Text and refreshed. Errors appeared for both fields - Expected Record Value.

The error seems to relate to Default and DefaultSelectedItems properties. They are currently display the formulas, ThisItem.Location and ThisItem.Department respectively in both property fields.

Hi Chris,

The methodology Mohammed uses is correct. There is however another way of doing this using the same methodology [which I use when the target field is a lookup].
Instead of Patching, simply try the formula below in the update properties of the card [I have used new lines only to show the logic].

[
{
'@odata.type': "Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
Id:LocationvDepartment.Selected.ID,
Value: LocationvDepartment.Selected.Title
}
]

NOTE - all of this is case-sensitive [ID does not equal Id] - you seem to have this one.

To explain [from my humble level of understanding at least]: -

Firstly, the purpose of the "odata.type" reference is a bit of a mystery to me [and others when you Google it] except I know you need it for multi-value field references to work on anything other than a straight [non-custom] cards generated by PowerApps [it takes care of this in the background].

On fields in SharePoint based on Lookup fields from another table [not simply multi-value Choice lists in the SharePoint target field], the field actually contains two pieces of information - the actual value you are after and the ID from the other list you are looking up and both have to be passed back to the target list.

I hope this helps.

• The collection I called CrewList [collected from a list called Crew, but this is not relevant].
• The field CrewItem is the list item used in the drop-down.
• The form is based on a list called Roster.
• The target field is [Roster.]CrewName.

• The Form's DataSource is Roster.
• The Card's DataField is CrewName.
• The drop-down's Default is Parent.Default [simply taking Roster.CrewName as the source].
• The drop-down's Name is CrewDD.
• The Items property of the drop-down is CrewList.CrewItem.
• The Update property of the card is CrewDD.Selected.CrewItem

• The collection I called CrewList [collected from a list called Crew, but this is not relevant].
• The field CrewItem is the list item used in the drop-down.
• The form is based on a list called Roster.
• The target field is [Roster.]CrewName.

• The Form's DataSource is Roster.
• The Card's DataField is CrewName.
• The drop-down's Default is Parent.Default [simply taking Roster.CrewName as the source].
• The drop-down's Name is CrewDD.
• The Items property of the drop-down is CrewList.CrewItem.
• The Update property of the card is CrewDD.Selected.CrewItem