Elements exceeds the maximum allowed as defined in the Properties

Nate Wert1 · ‎12-21-2015

I have a user table that has 110K plus records. I am trying to get a breakdown of a team by user. When I create a breakdown source off the sys_user table I get the following error: "This breakdown source was automatically disabled because the number of elements exceeds the maximum allowed as defined in the Properties". What is even more perplexing is the fact that with the filters set, this breakdown source is really only using 7 records.

I have tried to adjust the properties setting to exceed the number of records that are in this breakdown. The property that I adjusted was "Maximum number of breakdown elements for a breakdown to be included in data collection." However still get the same message.

Has anyone seen this before? Thoughts?

Atul Kumar2 · ‎12-21-2015

Hi Nate,

Could you please try after doing the caching on the instance. Just put above your instance url and check if it works ?

/cache.do

Note: Please do it on the lower environment and off pick hour because it impacts the performance.

Regards,

Atul kumar

Nate Wert1 · ‎12-22-2015

Hi Atul:

Thank you for your response. We execute a cache.do regularly in regards to another issue. Just to be clear, you are suggesting doing this after adjusting the properties?

Thanks again.

Atul Kumar2 · ‎12-22-2015

Hi Nate,

Yeah, You need to edit the property and then do the caching so that it can sync up with server in case if it has not.

Regards,

Atul Kumar

Vincent Loffel1 · ‎12-21-2015

Hi Nate,

Adjusting the properties should be handled with care. Best is to leave them as they are, because they can seriously impact the performance of your instance.

There are limitations to the number of breakdown elements, yes, but the question is why do you want to divide a table that contains 110K+ records over 7 users? What information do you get out of that? And more importantly what are you gonna do when you know this number? There are several suggestions I could do, but the most important question is, what do you want to measure and why? If we know that, we most likely can build an indicator that suits your needs.

Cheers,

Vincent