Unexpected Behaviour When Using 'Hours' as a Custom Field

Content
1

Hello. A client with multiple departments at one location is looking to store each department’s hours within a single Location entity to eventually surface them on custom built location pages.

It seems that when adding an ‘Hours’ field as a subfield within a list of Struct within a CF (as can be seen for ‘Popular Services’ CF in attached screenshot), there is no option to add holiday hours. Whereas when using an Hours field as a standalone CF (as you can see for ‘Priority Shopping Hours’ CF in attached screenshot) you can!

Does anybody know if this is a purposeful limitation/restriction when using an Hours field as a subfield to not enable holiday hours? Or do the holiday hours fields actually exist in the backend but for some reason are not surfaced in the entity edit UI when added as a subfield?

These fields will be powered by an API, so a list format is the preferred solution.

Any help would be appreciated - thanks!

Screenshot 2021-03-02 at 14.37.32
Screenshot 2021-03-02 at 14.37.321282×817 35.9 KB
Screenshot 2021-03-02 at 14.38.59
Screenshot 2021-03-02 at 14.38.59771×547 29.5 KB

2

Hi Gabriel,

Currently, we do not surface the holiday hours & temporary closed flags within the UI when Hours-type fields are in a list, or within a struct-type field. However, this information is stored in our backend, so for your use case, if you are powering these fields via API, then you would indeed be able to store and manage holiday hours data in this way.

We definitely have plans in the near future to surface these subfields in the entity edit UI for cases like this. But for right now, in your specific case, this information can be managed via API as well as via bulk upload.

Best,
Fed

3

Thanks for the info Fed!