Portal2 Map portlet data limitation

Flow Classic
1

Hi there, this is maybe a bit of rant, but i am hiding it within a question and sharing information to save others the same hassle; I have just spent the entire day working on getting a map portlet to work, and no matter what I did I could not get my data to show up in the map, even though my debugger told me it was fetching the data properly…

After a lot of trial and error i discovered that the issue was the number of records I was fetching that was the issue, limiting the dataset using TOP(50) for instance returned datapoints in the map. Trial and error showed me that the cutoff was at 603 records. Is there some reasoning behind this seemingly arbitrary number, and is this a limit that can be set up somehow in the settings on the server side? I can definitely understand the logic behind limiting the data shown, but would like to control it myself and know the logic behind it (whether it’s based on number of records, amount of data or what?)

Thank you in advance :slight_smile:

2

Hi @JoakimLeren Thanks for raising this concern, let me ask around about this internally and get back to you.

-Amri-

3

Hi @JoakimLeren ,
Development of the map portlet for Connect is planned for the middle of next year and we will keep it mind having a better interactive setting for that but as per the no. of cutoff records and the logic behind it , it’s more or less how it was designed.
Thanks

4

Hi Amri,

I can understand that, however since it is not specified anywhere it becomes very difficult for us to work with the Map portlet in Portal2 in any capacity as we do not understand the limitations and logic.

For example, I have a dataset that contains approx. 10000 records and a filter to filter on departments which would lead to the map portlet displaying something between 200-600 records for a selected department. If I pick a department that is an early part of the dataset, everything works perfectly, but if i pick a department that is a late part of the dataset, no data is shown in the map portlet.

This leaves me with the following questions:

  • What is the cut-off value?
  • Why is it fetching a limited dataset before filtering? If the filter is applied as part of the data query instead this would not be an issue.