aequos-solutions/modern-data-visualizer

Using ElasticSearch as search schema for data visualizer

Closed this issue · 10 comments

mayabank commented

Hello,

My requirement is to rely on ElasticSearch as the search schema for content that is stored in SharePoint. There are separate microservices for making entries into ElasticSearch index when a new record is created in SP.

ElasticSearch would expose simple json based rest apis for searching through the indexes.

The question I have is -

  1. Can I solve this via Anonymous API? If so, would the response from ES MicroService need to be oData compliant?
  2. Can I solve it by creating a custom data source? Is there a working example that I can refer and create my customization?
  3. Can I word wrap the search result column headers?

Thanks and regards,
Mayank

Laul0 commented

Hello @mayabank,

Thank you to reaching us; your questions are interesting:

  1. Yes. With OData anonymous Data Source you can request any API.
    Note: if you enabled the authentication, please refer to the Elastic documentation to set the appropriate headers ("Authorization": "Basic xxxx")
  2. You can create a custom Data Source too. This method allows you to have more options, flexibility on the request, and results.
    All information about custom data sources is available in our documentation: https://aequos-solutions.github.io/modern-data-visualizer/extensibility/custom_data_source/
  3. I think the answer is YES. You can manage the "slots" from the Data Visualizer to match your results

BTW: we saw your mail - you had created your issue before we can answer it. Additionally, we prefer communication via GitHub issues like this as much as possible rather than mail

Hope that information will help you.

Best regards

mayabank commented

Hello Laul,

Thank you for the response.

I havent been able to complete the POC and my trial expired. Is there any way that my trial is reinstated to be able to complete the POC?

Would be looking forward for acquiring license if the solution matches our requirement. Would it be possible to get in a call to demonstrate our our requirements and seek your help as to what you can do for us v/s not.

Thanks again for addressing queries.

With regards,
Mayank

Laul0 commented

Hi @mayabank,

Sure, we can see for exceptionally extend your trial version to let you enough time to test your use case.

Of course, we can schedule a point for some minutes to check your requirements and give you an ETA.

I will reach you by email for the meeting and for additional information to extend your trial version.

Best regards,

mayabank commented

Sure. Thank you. Looking forward to meet you.

With regards,
Mayank

mayabank commented

Hello,

Thank you. looks like license extended. But getting following error while adding search web part to page.

[SPLoaderError.loadComponentError]:
Failed to load component "544c1372-7e5a-49ec-8db6-812f76c375f2" (aequosSearchBoxWebPart). Original error: Failed to load URL 'https://publiccdn.sharepointonline.com/keysighttech.sharepoint.com/sites/filenetdev/ClientSideAssets/59903278-dd5d-4e9e-bef6-562aae716b8b/SearchBoxWebPartStrings_en-us_611ac8196d5e60e0be53b7c2c37fef24.js' for resource 'SearchBoxWebPartStrings' in component '544c1372-7e5a-49ec-8db6-812f76c375f2' (aequosSearchBoxWebPart). The file was not found in the server.

image

Laul0 commented

Hi @mayabank,

Did you upgrade the version of MDV?

mayabank commented

Hello Laurent,

Thank you for your time yesterday.

I tried registering an extension. Post that web parts started failing. I tried deleting and reinstalling the sppkg completely afresh but the problem continues to persist. Can you please suggest how can I fix it?

image

Thanks and regards,
Mayank

mayabank commented

Hi Laurent,

I solved this by changing the menifest id in the sppkg and redeployed with a dummy id. It worked. Thank you.

I got a question around slots wherein my datasource is SharePoint. There are a few pre-defined properties only to choose from when it comes to create a slot. How can I add my own property here? There are a few tenant level properties (for ex- ContentType) of which I manually entered the name in the slot but that didnt work.

If the property works in slot, does it mean that it will be available as a filter as well?

Thanks and regards,
Mayank

  • 👀1
mayabank commented

HI Laurent,

Looks like the properties to fetch from datasource is hardcoded in chunk.sharepoint-search-datasource_1ff4c0b860f47cc81dd5.js. How the new properties/dynamically added here?

image

Thanks and regads,
Mayanks

Laul0 commented

Hi @mayabank,

Glad to read that you fixed your issue about upgrading the package, even if it is quite weird such as behavior.

About the slots, it is a recommendation to use them - they help you to edit mapping without it your Template, but you can define item properties directly in your Template if you don't want to use the Slots.
Everything about the slots is explained in our documentation: https://aequos-solutions.github.io/modern-data-visualizer/usage/data-visualizer/slots/

Please note your issue has several subjects at the same time. It makes tracking more difficult and another purpose of split issues per subject is to help other people that can meet the same kind of problem/question.

I will close this issue because:

  • We saw your main issue about ElasticSearch together during a meeting
  • You successfully upgrade your package
  • I provided you the information about the slots

But feel free to open a new issue if necessary for one of these subjects or for a new one.

Best regards