Trying to filter by Office Location

(1) Share

Report

Posted on by blanghorst

206

Hello,

I am having an issue with a flow and hope someone can see what I'm doing wrong. Please see the flow below. Using the office location as a filter in the "Send an HTTP Request" activity will not work (that parameter doesn't seem to be supported as a filter), so what I'm trying to do is pull back a list of users and then filter the results based on an office location value, which I'll return to Power Apps:

The flow runs successfully but the Filter Array activity always returns null results - in the example below, you can see at least one of the inputs has the Office Location value set to 1234

What could I be doing wrong? I've attached the json sample used in the parse activity.

(Also, SearchUserV2 won't work in this instance because initially, there will be more than 1000 users returned. Post filter, I anticipate returning no more than 100 user names back to the Power App.)

JSONSample.txt

Categories:

Building flows

I have the same question (0)

All responses (5)

Answers (0)

Sort by

AnthonyAmador 2,557 Moderator on at

Like (1)

Report
Copy link

Link copied!
Hi,

This is likely a problem with the schema, but it’s hard to identify where. Can you try with this schema I processed using your sample?

{ "type": "object", "properties": { "type": { "type": "string" }, "properties": { "type": "object", "properties": { "value": { "type": "object", "properties": { "type": { "type": "string" }, "items": { "type": "object", "properties": { "type": { "type": "string" }, "properties": { "type": "object", "properties": { "businessPhones": { "type": "array", "items": { "type": "string" } }, "displayName": { "type": "string" }, "givenName": { "type": "string" }, "jobTitle": { "type": "string" }, "mail": { "type": "string" }, "mobilePhone": { "type": "string" }, "officeLocation": { "type": "string" }, "preferredLanguage": { "type": "string" }, "surname": { "type": "string" }, "userPrincipalName": { "type": "string" }, "id": { "type": "string" } }, "required": ["businessPhones", "displayName", "givenName", "jobTitle", "mail", "mobilePhone", "officeLocation", "preferredLanguage", "surname", "userPrincipalName", "id"] } } } } }, "@@odata.context": { "type": "string" } } } } }

Let me know if that works.

Anthony.

If my reply answers your question, please like and mark it as verified. This helps me stay motivated to assist others and makes it easier for users with similar questions to find the answer. Thanks!
Feel free to connect with me on LinkedIn!

Was this reply helpful? Yes No
Suggested answer

David_MA 14,499 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

In your array, the officeLocation is a string. However, the filter is treating it as an integer. You should convert the dynamic value in the filter to an int and I think it should work.

Was this reply helpful? Yes No
blanghorst 206 on at

Like (1)

Report
Copy link

Link copied!

Thanks for the help guys.

@AnthonyAmador - this did not fix the issue. I am pretty sure it is something with the JSON though like you said.

@David_MA - officeLocation should be a string - I just put 1234 in the filter field because I have a profile with that office number and wanted to test if it would work. I've also tried using other parameters such as givenName and it isn't working either.

Was this reply helpful? Yes No
AnthonyAmador 2,557 Moderator on at

Like (1)

Report
Copy link

Link copied!

Can you declare the following expression with the 1234 or dynamic value you are using? What @David_Ma mentioned makes sense, and it seems like the filter is interpreting the number as an integer.

For example

Hope this helps.
Anthony.

Was this reply helpful? Yes No
blanghorst 206 on at

Like (2)

Report
Copy link

Link copied!

Thanks! Yeah, I went back and ran some tests. Here's why I was a bit confused. If I used ABC123 as the office location, it did not work either. But I did go in this morning with a string function and it did work. Interesting.

Was this reply helpful? Yes No