Error in predefined filter or members have not been loaded yet: &[1]

Answered
Nil asked on November 24, 2021

Hi team,
We are getting this for flexmonster when connected to AAS.
Please find the below logs for your reference
 
core.js:27909 Angular is running in development mode. Call enableProdMode() to enable production mode.

flexmonster.full.js:442 Error in predefined filter or members have not been loaded yet: &[1]
wGa @ flexmonster.full.js:442
flexmonster.full.js:442 Error in predefined filter or members have not been loaded yet: &[11]
wGa @ flexmonster.full.js:442
flexmonster.full.js:442 Error in predefined filter or members have not been loaded yet: &[2]
wGa @ flexmonster.full.js:442
flexmonster.full.js:442 Error in predefined filter or members have not been loaded yet: &[12]
wGa @ flexmonster.full.js:442
flexmonster.full.js:442 Error in predefined filter or members have not been loaded yet: &[3]
wGa @ flexmonster.full.js:442
flexmonster.full.js:442 Error in predefined filter or members have not been loaded yet: &[31]
wGa @ flexmonster.full.js:442
dc.services.visualstudio.com/v2/track:1 Failed to load resource: the server responded with a status of 400 ()

flexmonster.full.js:442 Error in predefined filter or members have not been loaded yet: &[1]
wGa @ flexmonster.full.js:442
flexmonster.full.js:442 Error in predefined filter or members have not been loaded yet: &[12]
wGa @ flexmonster.full.js:442
flexmonster.full.js:442 Error in predefined filter or members have not been loaded yet: &[2020]
wGa @ flexmonster.full.js:442

5 answers

Public
Illia Yatsyshyn Illia Yatsyshyn Flexmonster November 25, 2021

Hello, Nil,
 
Thank you for reaching out to us.
 
If we understand correctly, the issue is warnings displayed in the console by Flexmonster. Does the component itself work as expected?
 
The possible reason is predefined member filters in your report that cause these warnings to appear.
Our team will investigate this issue and provide you with results ETA Dec 14.
 
Meanwhile, we suggest checking if all the members present in filters actually exist in your dataset. Trying to filter by non-existing members is considered a valid reason to display this warning.
 
Please let us know if other questions arise.
 
Kind regards,
Illia

Public
Vera Didenko Vera Didenko Flexmonster December 13, 2021

Hello, Nil,
 
We are happy to announce that the issue with the warning when setting predefined filters for OLAP data source was fixed.
 
This is available in the 2.9.14 (latest) minor release version of Flexmonster.
You are welcome to update the component. Here is our updating to the latest version guide for reference.
 
Please let us know if the fix works fine for you.
We are looking forward to your feedback.
 
Kind regards,
Vera

Public
Vera Didenko Vera Didenko Flexmonster December 28, 2021

Hello, Nil,
 
We are wondering if the fix worked for you.
 
Did updating to the latest version of Flexmonster fix the issue with the warning when setting predefined filters for OLAP data source?
 
We are looking forward to your answer.
 
Kind regards,
Vera

Public
Nil December 28, 2021

Hi team,
 
We have not updated the accelerator version to latest .Only angular library updated to latest 

Public
Vera Didenko Vera Didenko Flexmonster December 29, 2021

Hello, Nil, 
 
Thank you for your input.
 
Updating ng-flexmonster to the latest version should be enough for this fix to come into effect.
 
We hope the update works fine for you.
Should any questions arise, feel free to reach out.
 
Kind regards,
Vera

Please login or Register to Submit Answer