Patch with drop down not working

[akbarmahfuzalam]

PowerHi Guys,

I am new to Powerapps and I am trying to build an app for mobile users with their Time in and Time out with Cascading drop-down list which is been taken from SharePoint List.  

I am able to Build an app with all the combination and permutation. But when it come to send the data from Powerapp form to SP . Its not happing.

I am able to send data the one which is in Text format but failing big time with drop-down and date. 

Sample Code:  Patch(ATM,Defaults(ATM),{Title:TextInput1_1.Text,Comment:Comments.Text,Category:Dropdown1.Selected.Value})

The type of argument 'Category does not match the expected Type' Record' Found type Text

The function Patch has some invalid arguments.

In Sharepoint too I have defined Category as Choice field.

[akbarmahfuzalam]

Distinct(CascadingList,Title)

[akbarmahfuzalam]

For Category dropdown List

Item

Distinct(Filter(CascadingList, Title = Dropdown1.Selected.Result),Category)

Sub Category

Distinct(Filter(CascadingList, Category = Dropdown2.Selected.Result),SubCategory)

InternetFeasibility

Distinct(CascadingList,InternetFeasibility)

Language

Distinct(CascadingList,Language)

Process

Distinct(CascadingList,Process)

[Anonymous]

@akbarmahfuzalam 

What is 'CascadingList'? Also, why are you using Distinct and Filtering on Choice columns? The easy way to get the values of a Choice column is

Choices(myList.myColumn)

So, for the Items of your Choice columns they could all be the above structure. For Category, you may need to look at something different if CascadingList is larger than 2000 items?

I see you have removed your previously posted items, this would be helpful now. As an aside, is that list of various items in Excel or is it held in SharePoint?

[Anonymous]

I will also add, that an easy way to see what your Items properties should be for different controls is to add a new screen, add an EditForm and point it at your SPList then simply look at the Items properties of the various controls that PowerApps creates. This is a great way to troubleshoot.

[akbarmahfuzalam]

The Data is stored in SP and the Cascading List is where I am Cascading the dropdown as a dependent dropdown.

Cascading List is also stored in SP as a list.

CascadingList is exact 2000 items set.

Do you want me to change it to 1000?

I need to correct this one Elman. Since Yesterday I am trying to fix and am unable to fix this issue.

[Anonymous]

@akbarmahfuzalam 

Did you try adding an EditForm to blank screen to view the Items properties it creates?

Also, what do you mean by:

CascadingList is exact 2000 items set.

Do you want me to change it to 1000?

I'm confused. Do you mean CascadingList is set to 2000 items in the Advanced Settings in PowerApps OR is CascadingList a 2000 item SharePoint list and now you are willing to reduce this down to 1000 items?

To further explain the issue you are having, Distinct() is creating a VALUE ie a single item then when you are trying to Patch this VALUE to the Choice column you are getting the error that it needs a RECORD. Choice columns require a TABLE to be Patched to them.

This is why you add a new screen, insert an EditForm and point it at your List. You will then see what is required to be Patched. You may even be able to copy the Items from this Form and use them inside your Patch! What could be easier?

[akbarmahfuzalam]

To Answer

I'm confused. Do you mean CascadingList is set to 2000 items in the Advanced Settings in PowerApps OR is CascadingList a 2000 item SharePoint list and now you are willing to reduce this down to 1000 items?

Yes, I did in the Advanced Settings in PowerApps.

Did you try adding an EditForm to the blank screen to view the Items properties it creates?

I don't know how to do this  " I am new to Powerapp whatever I did it's by watching the Youtube and reading the blog.

Can you do one favor for me? Guide me if you can ad I will do it as walk me through.

This is why you add a new screen, insert an EditForm and point it at your List. You will then see what is required to be Patched. You may even be able to copy the Items from this Form and use them inside your Patch! What could be easier?

If I Add the Editform then my dependent dropdown will go by.

My ask is I want to ask my 1000 People to do an entry from their mobile app their Time-in, Time-Out and Home not working with a certain dependent drop-down list which I have stored in the SP.

[akbarmahfuzalam]

And one more thing I want to bring to kind attention as I am able to capture the text column in the SP

Patch(ATM,Defaults(ATM),{Title:TextInput1_1.Text,Comment:Comments.Text})

The above Formula is not fetching any sorts of error.

So what i did so far is I have joined One List from SP as CascadingList for dependent dropdown and now i want to add to another SP list called ATM.

[Anonymous]

@akbarmahfuzalam 

I can try to help you but I don't generally use Dependent dropdowns, I find them difficult to get right. If you are new to PowerApps then you definitely taking on a tough challenge first up and one you could probably avoid if you structured your data better, maybe?

Could you please re-post that Items list you deleted. That can be our starting point.

[v-bofeng-msft · Accepted solution]

Hi @ akbarmahfuzalam:

Could you show me the data structure of CascadingList and ATM? Screenshots are better. For example:

Column (click to edit)	Type
Title	Single line of text
Signature	Hyperlink or Picture
dattt	Date and Time
Operador	Choice
lookup	Lookup
Modified	Date and Time
Created	Date and Time
Created By	Person or Group
Modified By	Person or Group

Firstly, let me explain why you encounter the problem of data type mismatch.

The key is to use the same type of data for calculations and updates.

Issue1: The function Patch has some invalid arguments.

Dropdown1.Selected.Value is a text type value, I am afraid it is not feasible to update the choice field with a string.

Issue2: Thanks, Elman for your quick response, But it seems to be again not working.

Usually, using "Dropdown1.Selected" is enough to solve this problem, but only if the items attribute of Dropdown1 is set to Choices([@ATM]. Category).

The key is that you need to update this field with the preset options in the Category field instead of using other data sources.

Secondly, I suggest you pay attention to the items property of the drop-down box, and the data type of the referenced value.

For example:

Step1:

set the Dropdown1’s items property to:

Choices([@ATM]. Category)

Or

Filter(Choices([@ATM]. Category),Value = XX)  /* Value = XX is my custom filter rule*/

Step2:

Try this code:

Patch(ATM,Defaults(ATM), {Title:TextInput1_1.Text, Comment:Comments.Text, Category:Dropdown1.Selected})

Best Regards,

Bof