V5.1 problem with calendar view and timestamp fields on form

rocketman

just upgraded from 4.95 to 5.1 build 1427.

1) My main calendar is not showing any of the appointments - even though the next 6 weeks are booked up - busy busy

2) Some timestamp fields on my forms are reduced to 1 character in width and I can't input anything. I can select a date from the picker field but the time goes in as 00:00 and I can't get at the field to change this.

These seem to be fields that default to empty (null) when creating a new record. Anything that is seeded with CURRENT_TIMESTAMP shows as the correct size (like voucher sold time)but there are some fields that I need to be empty (start and end time of flight) which we don't know until the voucher holder phones up to book an appointment slot

HELP!!!!!

rocketman

Update, the zero length timestamp fields only occurs when the form is called by clicking in a time slot on the calendar. When called from the standard menu item, the fields are the correct length.

I can live with that until a solution is found but my main problem is that all the flight bookings and week long courses which were there earlier this evening are no longer showing in build 1427. fortunately they are still in the database and come up in standard lists. They may return if I switch to the old style calendar - I'm going to try that after a few hours sleep

but any ideas at this stage would be greatly appreciated

rocketman

... and his from the AwareIM viewer

Unable to find TLSale.ID in aggregate operation COUNT

rocketman

Update.

The report from Chrome's Javascript viewer.

GET http://www.dlgc.org.uk:8080/AwareIM/scheduler/css/sch.lockingschedulerview.css 404 (/AwareIM/scheduler/css/sch.lockingschedulerview.css)
Uncaught SyntaxError: Unexpected token <

rocketman

Note to AwareIM Support.

With regard to the zero length fields in my form. the offending fields (starttime and endtime) were in a separator area which was set as collapsible and collapsed initially. I have unchecked the collapsible box and the fields now show as correct size and editable.

Possible Bug?

Still haven't figured out why the calendar is empty. any ideas?

rocketman

Further note to AwareIM support

Have reverted to "use old style calendar" and all my appointments are visible again but - of course I don't now have the ability to run processes from the right click menu.

The only difference as far as I can see between the calender that works in the new style and the calenders that don't is the calenders that don't, use a modified appointment BO that contains reference attributes and shortcuts

aware_support

If you want urgent help please do not bombard the forum with cries for help. Send us an email and purchase a support ticket or consider purchasing a yearly support plan.

rocketman

THAT'S OUTRAGEOUS!!! and has just lost you a lot of brownie points in my eyes.
I was trying to be helpful and provide you with as much information from my own testing as I could.

The point was at 8:45 on Wednesday night all was fine and at 9:15 after the upgrade it no longer was. Upgrading to newer versions is supposed to be painless and seamless. This is Aware's problem not mine!!

rocketman

Having calmed down a bit over a coffee and a fag..

Seriously guys, I don't want to denegrade a fine product which I love, so if you want to remove this post and PM me on this matter - that's fine, but when the same set of data can be viewed in one calendar style with absolutely no problem but not in another, when the same set of data appears in the new style calendar in one version but not in another - then something is seriously wrong somewhere. And it's not something you should be expecting your customers to pay for to get fixed.

Further info. Since I have established that with a clean empty test site, I can enter and see entries in the new style calendar, there may be certain characters that are not being handled correctly. I have exported the entire table to a csv (1202 records) and on first run through, the only possible candidates are ' as in O'Connell, + as in Gavin + Stacey, - as in Evening-Group, and : as in Evening:Junior group. These are all in the Subject attribute

aware_support

New versions may be stricter in certain aspects and if something does not work in the new version it doesn't always mean that there is a bug. We didn't have complaints about this functionality from anyone else.

Most probably the problem is in your data somewhere and there is a character that the new version doesn't like.

Like I said, if you need urgent help you need to pay for support. This is normal practise for any company.

tonyjamero

I had this same problem with build 5.0, all of a sudden my appointments will not show in monthly view but the records are there when you query the records on standard report view. We thought it is cause by some corrupted data in one of the linked attributes. But after all the testing and experiments, we found out that its does not like the "&" character. So I just told my users never to use "&" when making appointments.

rocketman

FOUND THE PROBLEM

We use a BO to record the sale of Trial Lesson Vouchers. These are often purchased as gifts for a 3rd party. At the time of sale we often don't know when the voucher will be redeemed so we leave the start time blank.

After much testing, it would seem that if the new calendar system encounters a record with no start time then any records after that point in the BO will not show on the calendar.

I have been using a simple FIND ALL TLSales so I think I can do a workaround by modifying the search to find tlsale where starttime is defined.

Will post later if it works.

Support - you might want to look at this or at least document it somewhere

rocketman

The post as promised. The workaround worked. So to recap with a slight change,

If the new calendar encounters a record with a null "StartTime" attribute within the CONTEXT, the BO records immediately BEFORE the offending record will show in the calendar but any records AFTER the offending record will not show. Moreover if you try to add a calendar item - even though it might pre-date the offending record - it won't show in the calendar. I'm guessing that's because it will be placed at the end of the list in context.

This is different behaviour to the calendar in V4.95 which would simply ignore any records with Null StartTime and show everything else