#dominoforever | Product Ideas Portal
Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
Another limitation is the proper display oaf a 24+ hour reservation within the RnR database. While it is shown correctly in a user's calendar when booking a resource 24+, a "resource owner" has no proper overview in the RnR database how the resource is actually allocated.
From a schedule perspective (busytime/clubusy) everything works fine though, but RnR database also lacks of capability in displaying (not just creating) 24+ reservations, which would also be required.
IMHO - That would have to considered as a bug
How can this be NOT a bug?
Agreed. I have a client who rents small aircraft that frequently will leave sometime during one day and not return till the next - or perhaps several days later.