aware_support wrote. .
@[deleted]
I have an Appointments Group containing 5 Appointment objects with a large amount of records. 40 fields in common. Works fine for 3+ years.
I want to create a new unrelated BO Group (So I can use the calendar).
When I make a new Appointment Object (default name is Appointment) it puts it in the existing Appointments Group and of course it adds the Required fields for Appointments.
This table has no fields in common with the previous 5 tables.
Do i add these same 40 fields even tho they will always be empty. If not, then my queries that use Appointments will not be able to access the fields because the new 6th BO doesn't have these 'common' fields.
Of course, then I have to add these new 10 fields to the other, logically-unrelated fields.
Am I missing something?
If I make a new BO Group, I can add the new table to it. But its still forced to be in the original Appointments group.
If I now remove it from that group, it removes the Scheduler fields and is no longer an Appointment object.
Any ideas?