The challenges:
- If I was to create fields for all the possible different hours it would be too many fields, too much data on our account page layouts
- Stores are located in all of the different North American timezones
- Store hours are set by owners, so we can't just assume that all will be 9-5 because they are in X timezone
- The hours also fluctuate depending on seasons of the year.
Any suggestions on how we could track the hours without having too many fields for different seasons, one off occasions, ect.
Thanks.
2 answers
If many stores share common hours you could even create a Store Hour object and a junction object that way you could have a many to many. The let's say you have a store hour record created that is Central Time - Sunday - 9am - 5pm and 10 stores have those hours you could relate it to all 10 but then if the hours change on that record it will change them for all.
How many fields do you think it would take to capture all hours? Is it common for stores to have differnt seasons and several variations? I would try to keep it as fields on the account if it can be narrowed down.
