Report definition with unoptimized property returns a different property value
I have written a report definition that returns employee data. The columns are properties on 2 embedded pages in work objects. For a particular date property (Birthdate), the report returns the value of a different property (First name) if the value is blank or null. Otherwise, it returns the correct value. The property is unoptimized. This is the only property in the report that this happens with. All other properties return the correct values at all times. I have looked at the clipboard data of the cases and the birthdate is indeed not there. I have also run the report definition's SQL statement in query runner and it doesn't return the birthdate. Does anyone have experience with this happening to them or ideas of what could be happening here? If so, how can I resolve this?
Thanks for the confirmation.It is always a good practice to optimize property present in report definition.The reason behind that is DB stores these values as blob,It would not create any issue if data size is less but when volume of data is high then it plays a vital role.Expose/optimization of property creates a separate column in table respectively as a result data retrieval becomes faster.
Hope I clarified your query.Please let me know If you need more detail.