$Busytime and $CSVersion

I have an issue that I think has a simple explanation / fix, but it’s not coming to me, so, I’m hoping someone will have some input.

I have a Rooms and Reservations database with two custom views. Certain reservation documents that show in the standard views do not appear for some reason in the custom views - this is the problem.

I’ve looked at the view selection criteria, and the custom views (developed by someone else) specify that either $Busytime be unavailable / not present OR $Busytime = “1” and $CSVersion be available / present. The reason the documents are not appearing in the custom views is that they do have $Busytime present, but $CSVersion is not.

Does anyone know how these two fields get set? They’re not explictly defined on the Reservation form, and I’m not able to find the mechanism that sets them. If I can find why the $CSVersion isn’t being set when $Busytime is, then I should have a solution for my user.

Does anyone have any ideas?

Thanks,

Catherine

Subject: $Busytime and $CSVersion

Most of the R&R code is processed in core routines that we can’t access. I discovered this when I customized our R&R process to add feature availability to each room (A/V, seating arrangements, webcast support, etc.). I wanted to add custom fields to the doc that gets sent to the R&R database, but couldn’t. I had to mail a duplicate calendar doc to my custom app, and process my custom fields there.