TeamDesk Knowledge Base & Support

basenine 8/1/2016 6:39:11 AM

I had a similar issue a while back...and I too thought that it was the fact that there were too many records (filtering on a date range of over 13 000 records)

Turns out that 1 record had imported incorrectly and was only a problem with this new view that I'd created with "Ask the User". The problem:
A date was written in as 12/11/0012....so the "Ask the User" had to populate all dates starting with year 0012.

Slava made a view for me to find where the problem was occurring. It was a #records with year date type of view...anyway --> it pointed me directly to the faulty record and the view has worked perfectly since.

This might help
😃

Philipp Matuschka (MMB) 8/18/2016 12:44:33 PM

Blake

I usually found that it was due to heavy processing of formula fields while creating the view, especially if these in turn referred to selections. I got around it by using non-formula fields with defaults where possible. Another solution where defaults don't work and absolute up to date is not critical, I populate fields for reports with time based triggers, so that when a report is run the data is at most 10 minutes old.

I am a bit of a purist about the normalisation of my database, but this gets around it and still allows me to be almost a purist.