Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi All,
Does anyone know if there's a max number of fields that can be displayed in Source Documents -> Task -> Reduce -> Reduce by Field Value?
I select open document and can see it being loaded into RAM. The Processing swirl appears while it's loading, and then vanishes as expected. However, no field list appears. The document has 1828 fields. (Large I know, but I can't find anything that states there's a limit.outside of what the RAM can handle.)
If I do the same with Reduce by Bookmark, I get a bookmark list.
Same has been tried on a qvw with 60 fields, and that displays without issue.
So, back to the question, is there a limit to the number of fields that QlikView can handle in the reduce by field display?
Many thanks in advance,
Simon
In case this comes up for anyone else..
This from Qlik support which resolved the issue.
"The issue is due to the maximum message bytes. Since there are lot of fields , the maximum message size has exceeded. If you go to logs under C:\ProgramData\QlikTech\ManagementService\Log you will see an error message
"Error QDS did not respond to request.
Last exception (for http://qlikserver1:4720/QDS/Service😞 The maximum message size quota for incoming messages (262144) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element."
I am attaching an article for you to resolve the issue. Follow the below steps;
In case this comes up for anyone else..
This from Qlik support which resolved the issue.
"The issue is due to the maximum message bytes. Since there are lot of fields , the maximum message size has exceeded. If you go to logs under C:\ProgramData\QlikTech\ManagementService\Log you will see an error message
"Error QDS did not respond to request.
Last exception (for http://qlikserver1:4720/QDS/Service😞 The maximum message size quota for incoming messages (262144) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element."
I am attaching an article for you to resolve the issue. Follow the below steps;
Great post...helped me as well with the same issue.