Yes, we definitely had this problem. I opened a ticket, tech support and I screen shared, they shot two movies of the problem and the errors, and then said they would escalate the ticket. A few days later, someone from tech support contacted me and said they cannot replicate the problem. In the end, because they couldn’t replicate the problem, we just closed the ticket. Here is what he said: 1) The report rendering engine looks up the custom attributes first; 2) If it takes too long to return the custom attributes, the rendering engine throws an error or leaves the column blank; 3) We were getting two things - either the rendering engine said the attribute did not exist or it rendered the report with a completely blank column; He said it was probably latency on our network, causing a delay in how long it takes to return information from their servers, driving the error. If the delay was really long, it said the attribute did not exist. If the delay was short, but long enough, it rendered a blank column. Nonetheless, I believe he revealed something there. If something is running slow, a normally perfect report (with custom attributes) will throw errors. Does this help at all? Eric
