When querying data with the Microsoft Dynamics CRM V2 connector using FetchXML, Qlik internally retrieves the first page of data. It then checks if those attributes contain data, and only those attributes containing at least one value are being made available for subsequent use within the Qlik script.
Now, in certain cases - depending on the order of the retrieved records and on how the data is populated across the records and among the attributes - not all attributes contain values in the first page. The problem: In these cases, these attributes are discarded and not made available within the Qlik script.
Thus, I would suggest to implement a feature enabling it to bypass the above-mentioned check and get every single attribute defined in the FetchXML query - regardless whether in contains data in the first page of records or not.