Patch -> Invalid argument type. Expecting a record value, but of a different schema

[Anonymous]

I am getting the below error in patch function

-The function 'Patch' has some invalid arguments
- Invalid argument type. Expecting a record value, but of a different schema

-Your formula is missing a column id

Below is the formula

Patch('Single Point Of Failure', Defaults('Single Point Of Failure'),
{'Process Name':{ '@odata.type' : "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",Value:ProcessName}});

Here

Single Point Of Failure -> SharePoint List

'Process Name' -> Lookup field

Value: Process Name  -> Data card Name

Thanks in Advance

[WarrenBelz · Accepted solution]

Hi @Anonymous ,

That is because a Lookup field is a Table and also expects the ID of the item looked up in the other list. You also do not need the odata line. NOTE - this is syntax only as I do not know the relationship between ProcessName and the other list field.

Patch(
   'Single Point Of Failure', 
   Defaults('Single Point Of Failure'),
   {
      'Process Name':
      {
         Value: ProcessName,
         Id:
         LookUp(
            YourOtherList,
            YourLookedUpField = ProcessName
         ).ID   
      }
   }
)

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Visit my blog Practical Power Apps

[Anonymous]

@WarrenBelz Thanks a lot.

I am new to the power app development. It worked.

[Lynn626]

Hi There,

I am new to PowerApps and am running into the same error message (Invalid argument type.  Expecting a Table value, but of a different schema).  I have the main SP list 1 (Trigger Test Data-FINAL) where I want to update the choice 'Product ID' field.  I pull the 'Product ID' field into the form, but use a combo box to pull in the list of products from a different SP list call 'Product List'.  I use the patch code below wanting to update the 'Product ID' field based on the multi-select combo box, but got the error message noted above.  Below is the patch I used with the error message.  Any idea why the code is not working?  Thank you in advance for your help!  Lynn

Patch(
'Trigger Test Data-FINAL',
Gallery2.Selected,
{'Product ID': ComboxProdList.SelectedItems,
'Value for This Period': DataCardValue14.Selected,
Status: DataCardValue11.Selected,
'Reported Date': Today()}
);
If(
IsEmpty(Errors('Trigger Test Data-FINAL')),
Notify(
"Successfully Submitted",
NotificationType.Success
);
Navigate(ScrTriggerMain),
Notify(
First(Errors('Trigger Test Data-FINAL')).Message,
NotificationType.Error
)
)

[WarrenBelz]

Hi @Lynn626 ,

If you really must use Lookup fields (I have never found the need), be prepared for some complexity and limitations in many areas. As noted in my earlier post, you need to find the ID of the record in the other list containing the field you have chosen. It gets a bit more complex with multi-choice fields.

Patch(
   'Trigger Test Data-FINAL',
   {ID: Gallery2.Selected.ID},
   {
      'Product ID':
      ForAll(
         ComboxProdList.SelectedItems,
         {
            Value: ComboxProdList.Selected.Value,
            Id:
            LookUp(
               YourLookedUpListName,
               YourLookedUpFieldName = ComboxProdList.Selected.Value
            ).ID
         }
      ),
      'Value for This Period': DataCardValue14.Selected,
      Status: DataCardValue11.Selected,
      'Reported Date': Today()
   }
);

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Visit my blog Practical Power Apps

[Lynn626]

Hi Warren,

Thank you so so much for your quick response to my question above.  I plug in the patch you provided above which make sense, but now I got the delegation warning.  Any idea how I can fix this?

I have two other clarification questions if you don't mind:  1)  Your response above indicated that a Lookup field is not needed.  How else would I be able to provide the list of products for users to select from without the separate 'Product_List' Sharepoint List?  2)  I'm confused when I use the 'Product_List' Shareppoint List data source for the combo box that the column name 'Product' is not on the field selection list, but instead it's under a column called 'Name' which I have no idea where that came from.  Thus, I don't know in the patch if I should use the original column name 'Product' (for the list of Products) or the assigned column called 'Name'.  I would like to use the results of the combo box selection to update the 'Product ID' field in the 'Trigger Test Date-FINAL' Sharepoint List.  Hope that make sense.  Thank you again for your help on this.  Truly appreciate it!  Lynn

[WarrenBelz]

HI @Lynn626 ,

Yes and there is no avoiding this. SharePoint is not a Relational Database and will not accept Delegation on Relational (to a second list) queries within an action. If you were simply using the Choices() of the Lookup field as the Items of the Combo Box, this would work as the Id would be part of the Table in the Combo Box, but once you start putting other things in there you then need to "get the Id back".

To answer your "not needed" question, simply link the second list as a data source in Power Apps and then use the column you would normally look up as the Items of the Combo Box, then write the output back to a Text field in the first list. To your second point, if you want a second field lookup, put the list (or use ShowColumns with the fields you need) as the Items, select the Combo Box and then choose Edit from the right panel - you can then choose to display whatever field you want in the list seen by the user.

You can then also refer to any other field in the second list in the record you have chosen, so if for example, the output of your Combo Box was Combo1.Selected.Product and you had the ProductID in the Items as well, this would be Combo1.Selected.ProductID. There may be a bit more to the second one depending on how you are using it.

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Visit my blog Practical Power Apps

[Lynn626]

Hi Warren,

Thanks again for your quick response.  I went with your first recommendation above (see print screen below).  However, not sure why the Product field from the secondary SharePoint list is not showing the actual value, but 'Choice 1, 2....'.  Therefore, I just made the 'Title' the same as the 'Product' field and use that instead.  The combobox using the 'Title' field works.  

However, I'm getting the following error message using the patch below:

Any idea what I'm doing wrong?

Thanks again,

Lynn

Patch(
'Trigger Test Data-FINAL',
Gallery2.Selected,
{'Product ID': ComboxProdList.Selected
'Value for This Period': DataCardValue14.Selected,
Status: DataCardValue11.Selected,
'Reported Date': Today()}
)

[WarrenBelz]

Hi @Lynn626 ,

If you want to get rid of Delegation warnings, consider getting rid of Lookup fields - SharePoint is not a Relational Database and this field type is historical and was designed primarily for the SharePoint native interface and InfoPath (sort of a "light" predecessor to Power Apps).

[Lynn626]

Hi Warren, appreciate your feedback on this.  I will continue to look at this to see if I can find a better solution.

Happy Holidays!