Dropdown Items

(0) Share

Report

Posted on by RJF61

1,265

I have the following in the 'Items' portion of a Dropdown.

Sort(Distinct(Filter(EmployeeShort,Separation = false),'Job Title'),Value,SortOrder.Ascending)

My expectation was that it would select "distinct/unique" values from a column named 'Job Title' from my SP List named EmployeeShort. I am not receiving all values. Any suggestions regarding my error?

Categories:

Building Power Apps

All responses (3)

Answers (0)

Sort by

LaurensM 12,516 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!
Hi @RJF61,

Distinct will show only the unique values of a certain columns - in this case the job titles of rows where separation is false. However, the unique rows retrieved is dependent on the Data Row Limit. You might want to double check whether the Data Row Limit is set to e.g. 2000 instead of 500. (App Settings -> General tab -> scroll down)

Additionally, a dropdown can only display up to 500 items. Should the unique Job Titles surpass 500 records, you might want to use a ComboBox instead.

It might be obvious but adding it for completion's sake:

Make sure the Job Titles you are missing are actually in EmployeeShort (and Separation = false)

Should they be added recently, try to refresh the EmployeeShort data connection

If this solves your question, would you be so kind as to accept it as a solution.

Thanks!
RJF61 1,265 on at

Like
a
(0)

Report
Copy link

Link copied!

Hello @LaurensM Thanks for the response.

I believe your "obvious" suggestion is the key. As I reviewed EmployeeShort, there are (159) records where Separation is blank. These should have a value of "No". How do I ensure the SP List (EmployeeShort) is updated with a "Yes" or "No" and not have blanks? The data was entered in Power Apps.
LaurensM 12,516 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @RJF61,

A yesNo field normally has a default value that should take care of empty value patches. Is it possible that this field was added later on? In this case, all records before the column creation will remain empty.

To ensure a value, you could make the field required in your SharePoint list. Even in the very unlikely event (due to the default value) that the user manages to patch an empty Separation value, it will throw an error.

I hope this helps! 😊