Email optional causing error

%3CLINGO-SUB%20id%3D%22lingo-sub-2668807%22%20slang%3D%22en-US%22%3EEmail%20optional%20causing%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2668807%22%20slang%3D%22en-US%22%3EWe%20are%20currently%20using%20Bookings%20to%20allow%20customers%20to%20book%20appointments%20with%20librarians.%20As%20many%20of%20our%20customers%20do%20not%20have%20email%20addresses%2C%20we%20have%20made%20that%20field%20optional.%20However%2C%20we%20are%20learning%20that%20despite%20being%20optional%2C%20the%20system%20will%20not%20allow%20an%20appointment%20to%20be%20created%20without%20it.%3CBR%20%2F%3E%3CBR%20%2F%3EHas%20anyone%20else%20encountered%20this%3F%20We%20can%20add%20email%20to%20the%20custom%20fields%20and%20remove%20it%20entirely%20from%20the%20standard%20fields%2C%20but%20wondering%20if%20there%20is%20something%20I%E2%80%99m%20missing.%3CBR%20%2F%3E%3CBR%20%2F%3EThanks!%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2668807%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EBookings%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Visitor
We are currently using Bookings to allow customers to book appointments with librarians. As many of our customers do not have email addresses, we have made that field optional. However, we are learning that despite being optional, the system will not allow an appointment to be created without it.

Has anyone else encountered this? We can add email to the custom fields and remove it entirely from the standard fields, but wondering if there is something I’m missing.

Thanks!
0 Replies