search

aequos-solutions / modern-data-visualizer

Documentation for the Modern Data Visualizer solution
https://aequos-solutions.github.io/modern-data-visualizer/
8 stars 7 forks source link

[QUESTION] Taxonomy not showing term sets #119

Closed MartinSpitz closed 8 months ago

MartinSpitz commented 1 year ago

Version used 1.5.4

Question When I configure a Taxonomy template, I am only able to see the term groups. I dont have the ability to expand those to pick my term sets to be used, How do I get it to work?

image

Laul0 commented 1 year ago

Hi @MartinSpitz,

Taxonomy pickers use several requests and Microsoft Graph endpoints to access information.

To access these endpoints, your SharePoint administrator(s) need to approve the accesses to our App from the SharePoint admin center as mentioned in our documentation: https://aequos-solutions.github.io/modern-data-visualizer/installation/

Can you check if all necessary requests were approved? If yes, do you have any error from the DevTool Console of your browser?

We hope this information will help you, let us know

MartinSpitz commented 1 year ago

Hi @Laul0 It's working now for the first six term groups. But the last of them won't load. Please see below. Do I need to do anything else than approving the API access as I did yesterday?

image

Laul0 commented 1 year ago

Hi @MartinSpitz,

The approbation of the Graph API should be sufficient to access your TermStore. Do you have more information from the DevTool of your browser? An error in relation to the TernStore request?

MartinSpitz commented 1 year ago

Hi @Laul0 , I get this in the console from the DevTool.

Laul0 commented 1 year ago

Hi @MartinSpitz,

We will check on our side if we can reproduce the issue and release a fix for it. Not sure that your error is in relation to the Taxonomy picker...

wtdavis42 commented 1 year ago

I am experiencing the same issue. API Access has "Termstore.Read.All" permissions.

This shows the Enterprise term group has term sets. image

This shows the Enterprise term group cannot be expanded in the Taxonomy picker in MDV Filter Settings: image

Laul0 commented 1 year ago

HI,

Thank you for your feedback. We will check and try to reproduce this issue on our side and keep you in touch.

TrannumS commented 1 year ago

Hi @MartinSpitz @wtdavis42 ,

Could we please have a Teams call to understand this issue better? Kindly send your email ids and available time slots at this address: mdv@sword-group.com

Thank you!

MartinSpitz commented 1 year ago

Hi @TrannumS I have sent an email as requested last week. But haven't gotten any feedback from you guys.

Laul0 commented 1 year ago

Hi @MartinSpitz,

You will receive a link during the morning to take a time that will the best for you.

MartinSpitz commented 1 year ago

hi @Laul0 and @TrannumS Haven't received the link yet as you mentioned.

TrannumS commented 1 year ago

Hi @MartinSpitz ,

You should have received it now, kindly schedule it as per your convenience.

Thanks

wtdavis42 commented 1 year ago

@Laul0 , checking the status on this? I received an email on Sep 1st that you can replicate the issue, opened a ticket with Microsoft, and are also trying to find a way around this.

Laul0 commented 1 year ago

Hi @wtdavis42,

Yes, we can reproduce the issue because the cause comes from the SharePoint Search API. As far as we know, Microsoft is still working on it. We are checking on our side to see if we can develop a workaround or find another API to do the same thing.

In addition, feel free to open an issue on your Microsoft environment about the API (not MDV because is not supported by Microsoft). If you consider opening a ticket to Microsoft on your side, let us know if you need information.

Thank you

wtdavis42 commented 1 year ago

@Laul0 , I would be happy to open a ticket, but they typically have a hands-off approach to troubleshooting issues related to third-party products. One way to handle this would be for us to build some code to reproduce the issue then open a Microsoft ticket to address it. If you can provide any specifics, to pinpoint what's failing, I'll work on this.

Laul0 commented 1 year ago

Hi @wtdavis42,

You are right, mentioning a third-party product will not help you open a ticket. In addition to this, we determined that the limitation comes from the $batch endpoint. Even if no limitation is indicated, it will be quite complicated to challenge Microsoft on it. This is why we are working and checking on a workaround to bypass the $batch request limitations.

Once done, we will release a new version. We will do our best to release this new version as fast as we can.

Thank you

MartinSpitz commented 9 months ago

@Laul0 how is this coming along? It has been a while since the last update on this ticket.

MartinSpitz commented 9 months ago

@Laul0 please, can you share some information about progress on this?

Laul0 commented 9 months ago

Hi @MartinSpitz,

Sorry for the delay, the next version includes some important fixes that have an impact including taxonomy. We are working hard to release a new version very soon. Based on our calendar, we should be able to release a new version at beginning of March

Laul0 commented 8 months ago

Hi @MartinSpitz,

We released an earlier beta version of MDV that includes the fix for your issue : https://github.com/aequos-solutions/modern-data-visualizer/releases/tag/1.6.0-beta.1.2064eb3?notification_referrer_id=NT_kwDOAOkkZbM5Nzc4NTA1OTk0OjE1Mjc5MjA1

Once the latest release is available, you can switch back from the beta to it.

Thank you for your patience and your feedback, it is appreciated 🙏🏻

MartinSpitz commented 5 months ago

@Laul0 when will the new release be available? We are not able to install beta versions in our production environment.

Laul0 commented 5 months ago

Hi @MartinSpitz,

I am curious to know why you are not able to install the beta version. Do you have any errors? That would be appreciated if you could try the beta version to ensure everything's ok on your side before creating a final release without good improvements.

Let us know if you can do something on your side. If not, we will create an earlier release for you.

MartinSpitz commented 5 months ago

Hi @Laul0 It's a change process thing. We can not install beta bits on our production environment. We need a fully released version. So when will you release the new version (non-beta) with the fix? Thanks for your help so far.

Laul0 commented 5 months ago

HI @MartinSpitz,

We understand. The only thing is, if the fix provided is not sufficient, we have to check again on our side and perform a refactoring of the useless code. This is why, if a beta version can be validated, it is better. You still can check the beta version on one site collection only.

Anyway, we will provide a new release soon that will include the current fix.

MartinSpitz commented 3 months ago

@Laul0 any news?

Laul0 commented 3 months ago

HI @MartinSpitz,

Thank you for your patience and your understanding. To be able to create a non-beta release, we had to review our roadmap and exclude a couple of features dedicated to 1.6.0.

We were just able to create a release 1.5.5.

Thank you again 🙏🏻

MartinSpitz commented 2 months ago

@Laul0 thanks you very much. It works like a charm!! :)