[QUESTION] Can I combine people and list results via UI?

[bryllyg]

Version used
Ex: 1.3

Question
Hi, we've been using PnP V4 and are testing Aequos. In V4 I can combine people data from Graph and a SharePoint list by modifying the Search web part's template and Properties. In Aequos, the Data Visualizer web part does not provide access to Properties. Is it possible to combine Graph or People data and list data via the UI, or does this need to be tackled via advanced customization (using extensiblity libraries)?

Additional context
Add any other context about the problem here.

[FranckyC]

Hi @bryllyg, not sure to understand your use case. Can you show me the options you are refering to?

[bryllyg]

@FranckyC Of course. I'm kind of doing a workaround in V4 by making updates to the Edit Properties on the last tab of setup.

To combine my list (which includes tags I want associated with the users) I have my Results source pointing to the list, then I'm using a custom template based off of the People template to combine the user data and the list data. To do this, I have to edit the Properties to add back the "layoutProperties" that are cleared when I switch from People layout to a custom layout (I understand this de-linking is intentional). That allows me to display the user and hover card, as well ass tags associated to the user from my list. Like this:

Is there a way to accomplish this through the UI in the Aequos solution? The other place we've edited Properties is when we need to loop through an entire data set without using paging. In this case we're increasing the max number of items queried via the Edit Properties UI.

[bryllyg]

The real goal here is to have term set tags associated with users that we can use as filters, and display on the results cards, We have too much data to create user profile tags, and user profiles don't support nested terms ala term sets, so we're trying to combine the two.

[FranckyC]

Hi @bryllyg, I think I get it;). If your source already exposes the correct consolidated data then you can benefit from the custom layout extensibility feature to save additional properties that can be used in your template.

Otherwise, if your data need to be processed before rendering, then you can also use the custom source capability. More complicated option but you can do pretty much want you want here.

[bryllyg]

@FranckyC Thanks! I was thinking we'd need to dive into the custom source capabilities, but wanted to check and make sure I was going down the correct path.

[FranckyC]

You're welcome! Custom source is probably a good candidate for your use case. Let me know if you have questions regarding the implementation.

[bryllyg]

@FranckyC a related question (I can post this to a new thread if you want), can I increase the amount of items iterated through beyond 50 per page vie UI? Or is this also custom source?

[FranckyC]

Technically you can do more than 50 items per page if I remember correctly for SharePoint search. We limit to 50 for performances purpose and I suggest you to stick to it. You probably don't really need 500 items to displayed at one time :D

[bryllyg]

@FranckyC Sorry, I didn't explain that well, I'm only displaying from 9 -12 items on the page, but I need to be able to iterate through the entire list (over 15000 items) in order to collect the appropriate results. I'm gathering unique owners and providing a count of all of their items (displaying those with the highest count). It is a performance hit, but to get that data we need to iterate through the entire data set. What would be your recommendation for doing so?
Thanks!

[FranckyC]

In your custom data source, you have access to the paging information so you should be able to iterate (ex: itemsCountPerPage, pageNumber) if you are using SharePoint search, it is pretty easy to use that info to build your calls.

[ghost]

Technically you can do more than 50 items per page if I remember correctly for SharePoint search. We limit to 50 for performances purpose and I suggest you to stick to it. You probably don't really need 500 items to displayed at one time :D

@FranckyC what would be the easiest way to get all 500 rows returned from a SharePoint Search data source? We have a use case to group the returned data by a specific column and show a count (we would need all search results - typically 200 returned to do this, understanding that the grouping action will have a performance hit). Currently using handlebars to group the data and only displaying the groups/counts in the UI.

[Laul0]

Hi @randhawaryan,

As @FranckyC mentioned, you can use the SharePoint search pagination information to get more than 500 items.

Here, a link that explain the idea: https://docs.microsoft.com/en-us/sharepoint/dev/general-development/pagination-for-large-result-sets

Hoping this information will help you