Thank you for your suggestion.
This solved part of my solution.
I did it right on the custom connector itself tho, but much in the same way.
Search(
(Filter(
AddColumns(Office365Users.SearchUserV2({isSearchTermRequired:false, top: 1000}).value As temp,"employeeId",
Text(LookUp('MY-CONNECTION-NAME'.GetEmployees(),Upper(email)=Upper(temp.Mail)).employeeId)),
AccountEnabled = true,
!IsBlank(CompanyName),
!IsBlank(JobTitle)
)), TextInput1_1.Text, "DisplayName", "employeeId")
But I want to search both office365 AND employeeId at the same time with the same field.
Given the size of content in our Office365 connector this seems to give me a problem. As far as I can read on the Office365 connector documentation 1000 rows is the limit (with no searchTerm it seemingly justs snags the 1000 first rows in alphabetical order).
As of now, everything works for all persons going from A-C(somewhere), but thats it. And I can search for their employeeId. But the initial dataset is to small to cover my search.
If I on the other hand provide a searchTerm to make the initial dataset from Office365 connector smaller, I can't use employeeId as a term, since it doesn't exist in that connector.
Any suggestions would be much appreciated. 🙂
Regards,
Daniel