Today I received the information from HCL Support that the current version of the Room and Resource calendar does not have the feature to span meetings with 24+ hours.
There´s a request for this option in the Domino Ideas Portal ( please vote !! )
There´s also a SPR # ASAEBQELLY created for this issue. So if you want this issue solved quick, open a case and reference to the case number CS0125933 and SPR # ASAEBQELLY.
Last week I could see an issue with the resource reservation database regarding meetings 24+ hours.
Beginning with V11 you´re able to schedule meetings for 24+ hours and this is working very well ( thanks to HCL !! ). But if you also reserve a meeting room you’ll find out that the meeting scheduled e.g. from Wednesday, July 1st, 07:00 to Friday, July 3rd, 18:00, will only show up as a 1-day-entry in the resource reservation database.
Here are the screenshots:
The meeting entry in the calendar
The meeting entry in the calendar overview
The calendar entry in the resource reservation database
The calendar entry detail ( correct EndDate )
After opening a case I received the information that this issue could be reproduced. So it seems that there´s a problem with the template of the resource reservation database.
If you want to refer to my existing case the case number is CS0125933.
After a great hint from Oliver Busse I checked if the free time search is working – and yes, it´s displaying the reserved time correctly:
Starting with 10.0.1 you receive an error message “Operation failed” when trying to create reservations directly in the resource database with the German template.
This is caused by a forgotten bracket in the code. To get rid of this error you have to do the following:
- Open the template of the resource reservation ( resrc10.ntf, resrc11.ntf ) in the Designer
- Open the Script Library “SharedFunctions_de-DE”
- Switch to the function “GetResourceInfo”
In the second to the last “If versionNumber < 377” you have the following code where a bracket is missing in the marked “Else” statement:
To correct this issue you have to replace the code with the following:
IsSpecList_Error = Evaluate(|@IsError(@ExpandNameList( @Subset(@DbName;1) ; “| + tmplist +|”;[IGNORE_FWD_ADDRESS]))|)
After this modification replace the design of your resource database(s).