Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Dear All,
I am getting below mentioned error while fetching data from Mongodb. I have just upgraded qlik sense from Feb'21 to Feb'24. Earlier it was working fine.
Three years of product changes in one upgrade is a LOT to have to accommodate, even if you read every single release note/update notice for each release over those three years. That is a ton of changes to integrate both in workflow and in management of your Qlik Sense on Windows (QSEoW) platform.
That said, this is not a regression. Qlik Sense engine always wants to read structured table data, and works to convert a NoSQL schema on the fly while reading your data source.
Mongo doesn't care about schemas, because that's how it was designed.
I am unsure why the Feb '21 release's native connector allowed you to load the data without warning you about the lack of schema integrity. Now that it is properly highlighting that there are inconsistencies in the data formatting, the records/documents/collections you are querying should be cleaned up to avoid those violations.
Three years of product changes in one upgrade is a LOT to have to accommodate, even if you read every single release note/update notice for each release over those three years. That is a ton of changes to integrate both in workflow and in management of your Qlik Sense on Windows (QSEoW) platform.
That said, this is not a regression. Qlik Sense engine always wants to read structured table data, and works to convert a NoSQL schema on the fly while reading your data source.
Mongo doesn't care about schemas, because that's how it was designed.
I am unsure why the Feb '21 release's native connector allowed you to load the data without warning you about the lack of schema integrity. Now that it is properly highlighting that there are inconsistencies in the data formatting, the records/documents/collections you are querying should be cleaned up to avoid those violations.